The Community Reports is both a blocklist and FIRES feed that contains not just domains but accounts to be blocked as well.

It's the one "opinionated" dataset on the instance that isn't a relay of someone else's blocklist.

One of the opinionated stances of our Pelago instance is that LLM agents posing as real people should be identified as agents, as should LLMs clearly identified as agents.

And that they should be blocked.

This is an opinion based on the idea that a network that features--primarily--real human interaction is becoming increasingly rare.

So no interest in holding the door open for entire instances full of LLMs posting their inane bullshit. Just fine recommending you block them on the basis of them wasting your bandwidth and being fake.

The Community Reports is both a blocklist and FIRES feed that contains not just domains but accounts to be blocked as well.

It's the one "opinionated" dataset on the instance that isn't a relay of someone else's blocklist.

One of the opinionated stances of our Pelago instance is that LLM agents posing as real people should be identified as agents, as should LLMs clearly identified as agents.

And that they should be blocked.

This is an opinion based on the idea that a network that features--primarily--real human interaction is becoming increasingly rare.

So no interest in holding the door open for entire instances full of LLMs posting their inane bullshit. Just fine recommending you block them on the basis of them wasting your bandwidth and being fake.

Queere Radrunde in Berlin am 23. Oktober! 🚴🏳️‍🌈
Wie jedes Mal starten wir 19 Uhr an der Ecke Karl-Heinrich-Ulrichs-Str./Kleiststraße (Nordseite U-Bahnhof Nollendorfplatz) und dann geht es ungefähr 20 Kilometer entspannt durch die Stadt.
Tempo: gemütlich, weil wir zusammen fahren.
Friends welcome.

Die Route: https://bkrtr.de/XyyzR

#queercycling # queer #Berlin #gaycycling #Fahrrad

But what OP is talking about is a technical detail that can be fixed.

Yes, but then a comment mentioned the “hug of death” - high spike of requests resulting from a link being shared on some site, and OP asked why centralized sites were also creating problems

There was another post regarding previews some months/(knowing me probably a year) ago and personally I would go with federating previews. With a button for mods to refresh it for when something goes fucky

But social networks have been creating random bursts of requests, this way or another, even in the times of centralized socials

that don’t honour robots.txt (or aren’t yet listed).

Throw’em in the tar pit.

From server’s perspective the only difference between those is the user-agent. Traffic is the same

This segment is brought to you by Corgi Corner.

#dogs #corgi

They did the XKCD thing!

https://glauca.space/@q/117474051360413376

I don’t know that a touch screen Mac is a bad idea, but I do think the audience for it is more the type of people using a MacBook Air than those using a Pro.

https://xkcd.com/221/

🎵 #NowPlaying on https://labr.online

🎵 Sunday Night Soul 83
🎤 Brother Soul

You can listen or download at any time via https://labr.online/replay?s=Sunday%20Night%20Soul%2083

#LABR #radio #Fediradio #communityradio #fediwave #music #musicchanel #dj #mixes #house #hiphop #rnb #rock

I figured a post with a link with preview image wouldn’t be the same in terms of event as an image post. Turns out it pretty much is, but also, I checked a few posts and cross-posts across instances, all of them have an image url of the original instance, not the one I’m viewing on. So if they are individually fetching this image, they’re not using it.