‍fuchsiaaaaaaaaaaaaaaaaa @f0x@pixie.town

Also React 18's Suspense and serverside rendered response streaming is super cool, it allows out-of-order sending of the rendered page, where some things take longer to load than others (because they have to do various requests to the Mastodon backend)

Finally worked some more on #FediFoxShield, my project to write a protective layer of sorts around Mastodon 4.x' newly way too exposed API

Code is a sprawling mess, but i'm also using this as a playground for some new tech, like streamed server-side React rendering with Suspense

https://git.pixie.town/f0x/fedifox-shield

I can understand if new admins don't know that Soapbox is bigotware and they'll be defederated nearly instantly for running it...

but Soapbox is bigotware and you'll be defederated almost instantly for running it

the cloak looks like this btw

I think that what bothers me about the "there's a power imbalance between who can host an instance and who can't and that's why fedi is unsustainable" argument, is that it doesn't acknowledge that *this is true for every alternative too*.

This isn't a problem of Mastodon or fedi specifically. It is a problem of technology in general, a problem that even predates computers. It holds true for any infrastructure that involves technical complexity. Once it becomes a specialization, there's a power imbalance.

Even if you just look at social media sites - how is this any different for Twitter, Cohost, and so on? There's still the same admin vs. user power imbalance, just now you don't even get to choose who is the admin, and there's no real accountability because the cost of leaving is social exclusion.

I'm not convinced that this problem (of power imbalance in technical complexity) is actually solvable, and I also don't think that it's a useful *goal* to try and solve it - it feels to me like the same old 'rugged individualism' in a new coat of progressive-sounding paint.

The more useful goal here would be to *acknowledge* that those power imbalances exist, and try to erase or at least minimize their impact through building healthy communities and trust relationships. Not by replacing it with a centralized silo that has the same problems but worse.

(And no, P2P isn't a solution either. There's still a power imbalance between developer and user there.)

ak.kyaruc.moe is a single-user instance whose admin is a fascist (has an ableist slur in their bio, posts and shares racist and transphobic memes, hates the idea of defederation and shares posts from other freeze peach instances). they also have an account on starnix.networks

#FediBlock

Let's do a #NixOS Q&A thread! Ask me anything conceptual about Nix, NixOS, or related tools, and I'll answer honestly and to the best of my ability (including if the answer is that it's not a suitable tool yet!) ​

Please don't ask specific "how do I fix ____" questions, though - those require too much energy and back-and-forth for me to answer right now, and are probably best asked in the support room on Matrix instead.

Anything about the concept, the governance, whether certain problems are already solved, etc. is fine though! Particularly the kind of questions that are difficult to find a coherent answer to by yourself.

My perspective is that of someone who has been using NixOS for a long time, and is somewhat adjacent to governance, but who holds no formal position in any of it. I'm enthusiastic about where NixOS can go, but also critical of where it is today.

(And if your question is about what utility function to use, it's probably in this chart that I made: https://nix-cheatsheet.pixie.homes/)

Substack feels like medium.com in 2013. I wonder if it will end up the same in a few years.

If you want to blog: use a static site generator. Don't tie your publishing to a domain you don't own.