Mauve 👁💜 @mauve@mastodon.mauve.moe

And in order to make it easier for people to interact with data, there should be ways to have at least a default or some sets to choose from.

From there people could write their own views and share them with their pals or within moderated communities of view tied to data types.

Like, right now I have no clue what apps forlks are using, but it'd be cool if someone I'm mutuals with got added to my trust graph and I could discover the stuff they think is cool.

This gives space for creativity

For User Configurability, I think that's one thing that makes me the saddest about the state of the web (and apps!). While some hacker types can inject stylesheets and edit the layout at our whim, the average person is basically stuck with all the banner ads and useless shit and inconsistent accessibility.

For me personally, a lot of sites just don't work for my needs and are a constant pain to try to read through. What if instead they used standard ways of presenting their data.

Here's some things that I think would be important to have:
- User configurable views of the data (with color schemes!)
- Registries for data types and community curated lists of views
- Find ways to pull most common data on the web (e.g. reader view parsed html as legacy web page viewer, fediverse data)

Instead of a bunch of adware and megabytes of JavaScript / developers implementing totally random ways of doing things sites can serve "data" directly. Your browser should then take that data and give you some nice way of viewing it or letting you look up ways of viewing it (or buying or whatever for people that want that).

We could already start seeing things like that now with the ActivityPub data being published out there. What if the data itself also had suggestions for "default views".

One thing that we have now semantic-web-wise is a lot of data that random folks care a lot more about (it's their community or special interest!). And this is also coming from folks that were likely using alternative APIs already so they could get the best view of the data for their use case.

Usually this means new apps for specific purposes. But what if we could simplify making those apps and being able to recombine elements between them. In some sort of "user agent" for example.

However! This is also where the SemanticWeb and ActivityPub fit in.
One grossly underuse feature of activitypub is the client-server model and having the option to have access to data using a proper JSON-LD interface.

In other words. What if "fediverse" clients were just "Semantic Data" clients. Instead of relying on a specific app, we could have views over the raw data within a particular community through common (and swappable) interfaces.

Here's how we can get there and why it makes sense

One pain point though is exploring the domain specific way of formatting data while still being able to do all the social stuff. E.g. right now if I want to see a lemmy thread, I need to either see it boosted or navigate a lemmy instance and copy paste a link.

This means having lots of apps and identities, or also jumping between a bunch of websites.

This is where we are with the web and the current state of apps. A bunch of silos and we let them take full control.

One thing that we're seeing with stuff like kbin and lemmy is that there's room for other formats of the fediverse that can be appealing to lots of communities. And with AP at the core we can at least get some basic interactions server to server regardless of the specific format.

Here's my thoughts on how we can replace the web browser web with a data web and how this Reddit Migration thing is a great start. (thread)

In my experience the best docs for the average codebase I encounter are their unit tests. At least there you can see how the devs expect their library to be used even if they don't provide actual examples or actual docs for how to use it.

My hot take is that auto-generated docs from static types usually suck. Getting a randomly sorted list of function signatures is about as useful as just reading the source code.

Docs should get to the point and show people how to use the thing and fall back to type signatures for the nitty gritty bits when the examples don't suffice.

Golang/Java/Etc projects often just dump their types into an HTML page and call it a day without any context given to how to use it.

No confirmation yet, but the head librarian or whatever seemed interested in talking more about the workshops I wanna run to teach folks some skills to have more control over their computers.

I think devtools and bookmarklets might actually be more useful in the near term than full blown apps or whatever since it can give people the most broad range.

Honestly, following some Ottawa folks is already paying off. Now I can learn stuff without having to search for it. (an impossible task for me)

Low key thinking of running my own DNS server. I wonder how much it'd cost to give my home fiber connection a static IP. 🤔