To clarify - we’ve had that setting for a long time and it won’t be automatically changed on existing instances unless an admin chooses to. I’ve just changed the default of it for new instances (of which there are much less, lately).

It’s the easiest way to stop scrapers, way easier than getting Anubis or fail2ban working properly. Unfortunately it comes at the cost of walling off an instance but most instances are for individual / small group use so it’s an ok default to have.

Scrapers are not federating.

Activitypub could be used to harvest content on a ongoing basis but to get all the historical data, which is the stuff they want, they can’t use activitypub. Lemmy only has the last 50 posts in each community’s outbox.

In the latest version, PieFed defaults to a mode which requires a login to browse. An admin needs to tick a box to expose themselves to scrapers.

If Lemmy automatically generated a list of related communities then mods wouldn’t need to manually maintain a list.

Very nice!

Yuu might want to move Pixelfed down into the Photos clump.

Have a Quake 3 Arena tournament.

If Bluesky’s throttling you can stop your entire app from running, it’s not decentralized.

I’ve been thinking about auto-unfollow, too. For example if an account hasn’t logged in for 6 months they unfollow everyone and leave all communities (but preserve the records of their subscriptions so they can be automatically re-follow/joined if they log in again).

Then that one guy who subscribed to all those anime communities a year ago won’t cause your instance to receive anime forever.

That’s a secret. But the selfhost community has lots of advice, e.g. https://piefed.social/c/selfhosted@lemmy.world/p/2146191/safely-exposing-services-to-the-internet

Yeah it’s not great. I could have a PSU blow out any time and it’ll take me days to sort it out, probably. I have a spare server (these things are < $100 so why not) but getting it ready for prime time wouldn’t be quick either.

Anyway the resiliency of the fediverse is in the network - people can just use another instance for their fix of shitposts until their main comes back.

A long-time mastodon contributor is shutting down their instance - https://vmst.io/@vmstan/116757564108266599

Small instances close down all the time but in this case it’s not just anyone’s instance.

This new environment will provide developers with an incentive to find ways to rein in their platform’s storage and CPU usage.

The next shoe to drop will be when S3 object storage prices double or triple. That’ll really thin the herd.

I left Hetzner after the price increase a couple of months ago, expecting that hike not to be the last.

Now I run my own hardware. It feels good to ‘own the means of federation’ and not rent it!

Not in the same way, no.

Most of the fediverse is open to all by default and the control admins have is to create a block list of instances they’d rather not federate with. With Peertube it doesn’t federate with anyone until admins on both sides add each other to an allowlist.

One thing that took me a looong time to realize is that Peertube federates weirdly - it’s all under control of the instance admin, not it’s users. Admins decide which instances federate with each other and then all the videos are copied between instances that have agreed to federate with each other.

But there’s no way to see this in the UI, as an ordinary user!

So it’s all super fragmented. Discoverability is atrocious, even by fediverse standards.

If you look at https://instances.joinpeertube.org/instances?sort=-totalInstanceFollowers then that’ll help you find a well-connected instance. Then post onto that one.

If I were blind I’d prefer it if the app just hid all image posts from me. The alt text, when it exists, is going to be trash most of the time anyway.

“Impressions” is the amount of time a piece of content was viewed. This is a key metric in advertising-based situations because you want to know the ratio of clicks on the thing vs how many impressions it has to judge how effective a bait it is.

Yep. This is a setting I put in for my instance only, not hard-coded.

Various domains have warnings for different things.

Log into your account and change your display name in the settings.

Ah that is interesting, I missed that the first time.

So the author instance would be responsible for federating activities, not the instance hosting the community? That could be very beneficial for spreading load across the network! But maybe it would complicate moderation because the author could ignore moderator’s commands to delete the post and stop federating it.