

The British are no longer genocidal slavers, either.
But back in the early 1800’s they were. So was pretty much everyone!
Web developer. Lead developer of PieFed


The British are no longer genocidal slavers, either.
But back in the early 1800’s they were. So was pretty much everyone!


Lemmy has a wikipedia page…
As well as API endpoints for feeds, these are on my mind:
Cross posting non-link posts
When sorting posts by new and then viewing a post should default to sorting comments by new
Browser hang (JavaScript loop) when typing community name in certain situations


The inaccuracy is a feature - if you want to really terrorise a population, add a bit of randomness to your violence.


!piefed_css@piefed.social has examples of how to make small tweaks by pasting CSS into a field in your profile. Nothing y2k themed but it shows a route someone could take to create one.
When I do a curl request to the feddit.online API endpoint I can log in fine. If I use an invalid password I get the expected error message.
rimu@rimu-mate2 ~ $ curl --request POST \
--url https://feddit.online/api/alpha/user/login \
--header 'Content-Type: application/json' \
--data '{
"username": "rimu",
"password": "valid password"
}'
{"jwt":"some gibberish"}
rimu@rimu-mate2 ~ $ curl --request POST --url https://feddit.online/api/alpha/user/login --header 'Content-Type: application/json' --data '{
"username": "rimu",
"password": "invalid password"
}'
{"code":400,"message":"incorrect_login","status":"Bad Request"}
Do you have any nginx rules which block scrapers by inspecting the user agent string? Perhaps that’s catching Voyager.
Yes, it was changed to ‘None’ in v1.6.0. A change too minor to mention in the release notes.


You can tell that’s not a real border patrol agent because he’s showing his face.


No advantage, in fact a massive disadvantage.
Fascists lie.


A handful of people - https://mastodon.social/tags/noltosocial


Check out this one I came across earlier - https://github.com/Jtensetti/fediverse-career-nexus/blob/main/README.md
It’s a federated LinkedIn. ofc it’s vibe coded.
Your first post was fine. You can leave it to the moderators to delete anything that doesn’t belong.


Laptop CPUs are crippled garbage compared to desktop CPUs of the same generation. So there’s that.
I haven’t tried to make something like that. I think it’d be hard to do that without also exhausting our resources too.
There are a lot of strategies. afaik a tar pit tries to waste the attacker’s resources by delaying our responses to their traffic? A honey pot tries to funnel bot traffic towards a place which only bots would go to. Once they go there you know they’re a bot and they can be banned.


That is a lot like AT Protocol.
There’s pros and cons to every architecture. Which pros seem important and which cons you can put up with depend on your values and priorities.
A never-ending maze would mean the scrapers just hammer our servers forever. Better to lead them into a honeypot and automatically ban their IP. Like PieFed does.
Yes PieFed has a setting for that. It makes scrapers give up pretty fast but ruins the experience for people without an account so I only use it on really bad days.
There is a FEP for this - https://codeberg.org/fediverse/fep/src/branch/main/fep/3b86/fep-3b86.md it’s not something dansup came up with originally. We’ll see how close Pixelfed adheres to it.
PieFed has implemented basic support for that FEP since August 2025 and I just added more today.