‍fuchsiaaaaaaaaaaaaaaaaa @f0x@pixie.town

twitter turned on authorized fetch? nice, glad to hear they're taking safety seriously *finger to earpiece* oh

so I just found my favourite new app on Android: Google Reading Mode https://play.google.com/store/apps/details?id=com.google.android.accessibility.reader

it's like Talk Back, but more suited for long-form content. so you initiate it in the same manner and it will parse the text, generate an easily customizable / scrollable text view for it and allow you to play it using some surprisingly great machine voices. I'm currently using it to listen to an article by The Verge and it really isn't far off the experience of listening to a podcast

this is legitimately amazing. I'm really hoping the usage flow for it is just as great for visually impaired users too

girlcock.club doesn't appear to have issues with hosting disqordia people who have alts on various parts of fash fedi or are just abusive channers elsewhere. I've not seen anything done about a concerning report I forwarded to them a few months ago about this. I am probably not taking new follows anyways, but I would be extra scrutinizing of profiles on that instance if I were you.

#ProjectToot: I've finally completed an initial version of dlayer, my graph query library; it's kind of like GraphQL, but without the Facebook, without the weird DSL, and without the weird monolithic "design your whole API at once" design.

Instead, it's an extensible, modular design; an API is composed at runtime of one or more modules, which may or may not be aware of each other's existence, and extend each other's types with extra attributes as well!

This makes it much more useful for collaborative projects where different people might design different extensions for a (semi-)standardized API structure, as well as organic development, rather than GraphQL's assumption that you have one "team" that "designs the API" - which I'm sure works great in a startup, but *sucks* for community projects.

It shares the same useful property as GraphQL does, however; it lets you very easily assemble a coherent API out of many different, inconsistent data sources, regardless of whether any HTTP is involved. (There's currently not even any HTTP anything!)

The current implementation is in JS, but the design (and extensibility method) are simple enough that I see no reason it couldn't be ported to other languages!

Here's a rough example of how it works, with some dummy "modules" and data: https://gist.github.com/joepie91/a01a59485cd399324e37e3c6f00ebf78?ts=4

I need to sleep now, but I'll post a link to the code and some initial documentation tomorrow, probably. Let me know if you're interested in testing this out though :)

All the "why we shouldn't federate with Facebook" articles are like, deep analysis of historical behaviour track record, potential consequences for the community, group dynamics, etc.

And then there's the pro-Facebook articles and they're all just "but the growth! won't you think of the growth!"