Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)RA
Posts
0
Comments
74
Joined
2 yr. ago

  • Atleast the second point on your 'missed' list is generally instance related (atleast in my experience).

    The only issues with buttons not working I had was when I didn't realise my instance was down to update to 0.8.1

  • I mean you're highlighting some points that support how open and decentralized that this place is?

    It seems there is a healthy sentiment among users and understanding the tolerance paradox. Beyond that the ability to discuss around what we (an instance) wants vs what we (Lemmy) wants vs what we (individual users) want is great. The option the federate and defederate is also great, as if there is an instance adding 0 value to any of those prior groups (like lemmy.online), you as a community can decide to not federate. You as a user don't like that choice? You can go to another instance or make your own! The level of openess and control is really in your hands.

  • That's a new one... 15+ years on the internet, wtf does ICYMI stand for

    I felt the need for a quick edit, I appreciate the knowledge drop. Wine drops my pleasantries and so I just dove in on my curiosity!

  • Option 2 is cool in regards to letting users decide... Option 3 is my second choice that said.

    That said I ultimately agree with option 1. An instance dedicated to just regurgitating content from another user-generated site is just not a good thing. There is 0 value to those posts on Lemmy, instance wide imo.

    There is 0 way to interact with the posts in a meaningful way and they just fill up 'new' with crap from somewhere else.

    I don't like the nuclear option of defederation, but I really just see that instance as a hindrence to the existence and natural growth on Lemmy.

  • It's in git. In our current but on its last legs env we had a inhouse built tool that would compare a release branch with master and build a series files we'd throw at the DBA to run updating procs, tables, views, etc. Had procs built to preserve data when ddl changed and what not. Very painful. This was on Netezza.-

    Now we are moving to Azure Synapse... And we are using Azure DevOps instead of Bitbucket and it works but its jank. Our git repo is now actually tied to the DB through the use of release pipelines. PRs on master will get released automatically... That said most recent update from msft and now it takes 7hrs just for the deployment plan to build.

    Its not great.... My company is addicted to stored procs. I hear there is some projects looking into databricks, azure data factory, sparks, etc... For now my life is pain and complaints, just trying to get people to learn to love git. BI here before I joined unfortunately not IT minded.

    Edit: didn't even touch on testing.... And frankly half the devs seem like they don't/don't know how to even do impact analysis... If you change a column, at minimum search the code base for impacts... Don't just deploy and blow up our prod cause you're mismatching sizes