[–] 13 points 2 days ago (1 child)

It’s because an instance ban is a major action usually reserved for bots or pedophiles spreading bad things. If every single admin had to remove that user and their posts it would allow bots to spread things like wildfire and for CSAM to stay up for an indefinite amount of time.

It’s much better and safer for the entire fediverse that instance bans propagate deletions.

  • source
  • parent
  • context
  • [–] 8 points 1 month ago (1 child)

    I’ll give my reasoning. Or at least one story from a compendium of many.

    There is an OSS library called ktlint for Kotlin. It is a “no bikeshedding linter” that was supposed to be based on the default rules from JetBrains. That is, if a rule existed already from JB then ktlint would enforce it and if the rule wasn’t specified it would make and enforce a new one that the community agreed on.

    That was all fine and dandy until I and some others pointed out that one of the rules was the exact opposite of what JB had specified. When called out the owner of the repository didn’t care, until too many people were against his choices that he couldn’t ignore it anymore. He made it configurable.

    So the rule was fixed. Until he sold the repository to Pinterest. Pinterest just wanted to own ktlint so they could control the rules. They immediately changed it back and made it non-configurable. When pressed on it, they just refused saying it wasn’t going to be that way anymore. They didn’t care what the community wanted they just wanted to control the rules for themselves.

    The repository is open source, but they took the most widely used Kotlin linter and essentially stole it from the community. Getting enough people to switch because of one rule will never happen.

  • source
  • parent
  • context
  • [–] 33 points 1 month ago (1 child)

    They declared they have no AI features. The features in Firefox are still AI features. They aren’t needed. They’re a waste of development time and are useless.

    I literally say this as someone that has contributed to Firefox.

  • source
  • parent
  • context
  • [–] 9 points 4 months ago (4 children)

    Lemmy world uses cloudflare. Cloudflare blocks problematic IPs. Someone on that vpn IP has been doing naughty things and so the IP was flagged. Just switch your location in the vpn and try again.

  • source
  • [–] 28 points 4 months ago (5 children)

    Good opportunity for him to say he doesn’t have the money right now, can she buy him the plane tickets and get himself a nice little free trip to LA. She’ll obviously say no, and boom he’s out of it.

  • source
  • [–] 22 points 5 months ago (2 children)

    Am I the only one that has noticed the massive increase in buggy software across almost every domain? Like, EVERYTHING has so many more bugs now. Things just break constantly. AI isn’t one shotting fixing bugs, it’s one shotting making hundreds of new ones.

  • source
  • [–] 9 points 5 months ago

    the amount of people that do not understand how big of an improvement passkeys are is really saddening. They think that somehow these tech companies are utilizing this in some nefarious way, rather than the very very simple explanation that ... tech companies don't want to be responsible for more breaches.

    Passkeys are so simple and such a huge improvement that it's literally all upsides and no downsides. Either you use their passkey managers like you would their password managers and it's safer for them, or you use your own password manager with passkeys in it and it's still safer for them.

  • source
  • parent
  • context
  • [–] 11 points 5 months ago

    You have a vast misunderstanding of why passkeys aren't transferrable or usable outside of those providers. It had nothing to do with lock-in, but because every implementation was different. And no, you do not 'depend on the site' to let you use that option instead of a major provider. There's a standard now and everyone is following it. If you can use a passkey you can use your password manager to manage that passkey.

  • source
  • parent
  • context
  •  

    Hi all,

    First off, I want to apologize for all the server instability. We long ago outgrew our instance size, but I was unable to afford a larger node on our provider, Vultr. We were maxing out every part of the server whenever any even slightly significant number of users were on the fediverse.

    I've finally found the time to migrate us to a new provider, which allows us to step up to a much more powerful configuration. That migration has now been completed. I actually intended to post about the downtime on this community this morning before beginning, but when I went to do so, the server was already down and struggling to come back up. So I went ahead with the migration.

    Server before 4cpu/16GB/400GB NVMe Server after 8cpu/64GB/1Tb NVMe

    Please update this thread if you are seeing any issues around any part of the site. This means duplicate threads, things that aren't federating, inability to load profiles, etc.

    There is still database tuning that needs to occur, so you should expect some downtime here and there, but otherwise the instance should be much more stable from now on.

    During this process I also improved several other aspects of operating the server, so any 'actual' downtime should be accompanied by proper maintenance pages (that hopefully don't get wiped by ansible anymore), so that will also be a good indicator of legitimate maintenance.

    Once again, I really apologize for all of the downtime. It's very frustrating to use a server that operates like this, I understand.

    snowe

    view more: next ›