Show newer

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)

Show thread

Finally worked some more on , 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

git.pixie.town/f0x/fedifox-shi

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

@thufie It's still kind of a tech demo atm, but I think it can progress fast from here. Especially as I'm hoping to share a bunch of components with the FediFox client (profile, toot, thread rendering etc).

Security-wise, the worst that could happen is exposing something that local non-admin account has access too, but as it won't follow anyone there's no simply no way to accidentally expose someone's follower-only posts etc

@goat@hellsite.site don't goats always have horns on main

also also now i'm going to do that thing where i'm not working on stuff so much after dinner, and just play some video games

(also it just uses the Mastodon api, so you can run it in front of a GoToSocial instance too if you wanted)

Show thread

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)

Show thread

Central to the design is that it authenticates as a local account on the instance, so you can run it with `DISALLOW_UNAUTHENTICATED_API_ACCESS`
(which would totally break the entire new frontend), and still have functional public profile and thread pages.
This also allows introducing more configurability and more consent, like letting users choose if they want to include unlisted statuses, or even show their profile publicly at all

Show thread

thought i was going crazy staring at my code, turns out there was a tiny fruitfly walking across the screen in circles

meta, power imbalance 

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.)

Finally worked some more on , 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

git.pixie.town/f0x/fedifox-shi

i should know so much better than to argue package managers with techbros

@zens@merveilles.town right, I guess i'm more interested in component libraries, which would be TailwindUI, but that stuff seems to be paid only

:boosts_ok_gay:​ considering using TailwindCSS for a project, thoughts?

Show older
Pixietown

Small server part of the pixie.town infrastructure. Registration is closed.