Corruptress of protocols; trust & safety tech; open-source contributor; Independent Contractor; Chronic Illness
You've probably used tech I've contributed to. 🏳️⚧️ 🏳️🌈 🇩🇪
I'm on the Fediverse: https://hachyderm.io/@thisismissem (this account is bridged too!)
Emelia
Loading...
Oh shit, this is still ongoing too
Are you in the Portland area and interested in #ATProto? Let us know in the comments to get added to the starter pack and so we know to reach out to you for upcoming ATProto #PDX meetups!
go.bsky.app/F8mKKn2
I totally nerdsniped myself with that little waitlist feature for @questionable.fyi — vite plugin for cimd-service, a lexicon for the records, and lots of other stuff!
There's no email notifications or anything like that, just a "eventually you'll be able to login to the alpha"
Also, with that, there's now a way to tell me you're interested in questionable.fyi – there's a really simple waiting list setup:
Submit a request, it gets written to your PDS (fyi.questionable.waitlist.reqest)
At some point in the future, I'll look for all that have that record, and add them.
Updated, built one: github.com/ThisIsMissEm...
It's not _super_ efficient, but it works. Would need to probably publish it as a package for others to use, but I'm not sure I really want to maintain that..
Let's get straight to the point:
Renting servers for hosting all 75k+ SkyFeed feeds for millions of users daily costs me ~1094 EUR/month
SkyFeed is 100% free, so the only income is my GitHub Sponsors (github.com/redsolver) with ~191 EUR/month
The math does not quite work out here.
Oooh a random PDS idea: what if there was a way to "soft ban" someone as an operator?
So: stop serving their data, but still allow them to migrate away. Could be useful for PDS terms of service breaches that aren't awful - e.g. if you end up on a PDS you shouldn't be on by mistake