Maiyannah BishopIt was the dawn of the third age of federation, ten years after the Diaspora war. The ostatus project was a dream given form - it's goal: to give a place where people could work out their differences peacefully. It's a port of call, a home away from home, for shitposters, furries, developers, activists, and wanders. All wrapped together in over five hundred thirty-eight machines of silicon and steel, all alone in the internet. It can be a dangerous place, but it is our last, best hope for peace. This is the story of the last of the ostatus networks. The year is 2017. The name of the place is GNU social.
Diana
- 36 Followers
- 45 Following
- 193 Posts
queer, programmer, etc
Zaki@argumatronic I'm imagining a universe where computers are still women but Haskell exists and it's the only way to talk to women.
Does anyone have experience with the MongooseIM fork of ejabberd? I'm thinking about standing up my xmpp server again, and I really don't feel like going back to prosody.
NolanDistantly you recall something called a "web browser" with "tabs" that you could switch between. Your left hand involuntarily twitches towards the Ctrl and Tab keys, driven by a deep longing for a past joy which you can no longer name
Oracle(tm) e-Business Social 🎃tfw you want to yell at the cloud and be a curmudgeon, but you're not nearly old enough to be convincing. you just like the classics.
Nolan LawsonActually I take back my take-back. Trying to string together Rollup and Browserify and Babel with about 20 different plugins to handle JSX correctly and I'm starting to get a taste of why backend folks smack-talk modern JS practices so much. Some of these things are configured in 3 different places and it's hard to tell which config is actually winning. I get an error message and it's impossible to tell which plugin/transform/package caused it. We've ruined JavaScript, folks. #MastodonPerf
@nolan This is the kind of stuff that backend devs like me cry into our C++ textbooks about.
ShiPoCluGod will punish you for running a follow bot.
DJ SundogOkay, off the cuff and possibly wrongheaded in places depending on how it comes out:
A federated network of real-ish-time streaming data servers should have very minimal data payloads at their most basic level. The barest minimum of object properties for any object in a stream.
Implementations should add additional object properties to support their needs. There should be a well-defined format for sharing these additional properties and implementing elsewhere.
Truly, a master of project management and diplomacy