Mauve 👁💜 @mauve@mastodon.mauve.moe
- Pronouns
- they/them/it
- mauve+fedi@mauve.moe
- Matrix
- @mauve:mauve.moe
- Github/Gitlab/Discord
- @RangerMauve
Mod
Occult Enby that's making local-first software with peer to peer protocols, mesh networks, and the web.
Exploring what a local-first cyberspace might look like in my spare time.
Joined Apr 2022
LMAOO I had a typo in my test url.
Good news! The replies index in the social inbox seems to be working. https://social.dp.chanterelle.xyz/v1/@mauve@staticpub.mauve.moe/inbox/replies/https%3A%2F%2Fstaticpub.mauve.moe%2Fnewpost.jsonld
With this static websites can easily link to the replies collection of their posts without needing to recompile for every reply. AP clients or instances can then pull those replies into their thread view. Next up we'll be rolling this out to sutty sites and pulling them in https://reader.distributed.press
@mauve@staticpub.mauve.moe Any day now 😭
@mauve@staticpub.mauve.moe Another one, thank you 💅
@mauve@staticpub.mauve.moe Testing again lmao
Mauve 👁💜
boosted
Operating systems like iOS and Android are designed as media consumption devices (e.g.: for watching TikTok or Instagram). They are barely usable as a general purpose computer.
Several libre mobile operating systems aspire to imitate iOS and Android. With good intent: so that user familiar with these are familiar with the new libre OS.
The downside is that these new libre platforms are not well-designed mobile computer operating systems; they're mostly imitations of media consumption devices.
Honestly I wish I had more use for my knowledge of the #chromium source code.
Anyone wanna pay me to get web extensions working on mobile chromium?
@xgebi The format used in the extensions system specifically checks against the hostname.
The source code is here: https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/renderer/core/url_pattern/url_pattern.h;l=26?q=URLPattern&sq=&ss=chromium%2Fchromium%2Fsrc
@homestucklinebyline This is me checking emails in the morning
@pry Merkle Search Trees are way more complicated to deal with and implement in my experience. I wrote up a spec for the prolly tree impl I use here: https://github.com/ipld/ipld/blob/776b537e0d16dc0341f1bec13ee79bd05a0dfb9e/specs/advanced-data-layouts/prollytree/spec.md
It talks about how merging works.
The tl;dr is you traverse the merkle tree and where you see a diff, you add in keys from there, you can quickly skip places where the data is the same. You could treat it like an eventually consistent system in that way. Also could merge just subsets of the tree according to the keyspace
@pry The other cool part is that compared to other DBs like hyperbee from https://holepunch.to Prolly Tree based databases can be determenistically merged without much hassle so you can have communities merging datasets into larger and larger indexes without having to fully replicate all the data, just the parts at boundries.
@pry Right now most p2p data things use some variation on an "oplog". As your data grows it gets slower and slower for a peer to get the state of the data and it makes it hard to do "sparse replication" of just the data you want.
Using an indexed database as a building block means you can replicate just the data you need for a particular db query. This means you applications get more speedy and you use less data overall. You can still do full replication in the background.
Mauve 👁💜
boosted
Google PR sure is taking its sweet time getting back to me about the finding that Chrome has a hidden extension that allows all *.google.com domains to monitor your CPU usage and other private system info. I'm sure they're working just as fast as they can.
https://simonwillison.net/2024/Jul/9/hangout_servicesthunkjs/
High on my todo list is HTTP over #veilid app messages with a local daemon that can act as a proxy.
- Register veilid service
- Run local daemon as a proxy (optionally tell it to make a safety route)
- Curl to a unix socket the daemon is listening on
- `Host` header set to the public key for the service
- Encode request as app message to the service
- Response gets sent as an HTTP response down the socket
Bad for large files, good for locally run services / automation.
Might fuck around and place more local services under unix domain sockets for a laugh. 🤪
https://github.com/node-fetch/node-fetch/issues/336#issuecomment-1260253215
@KatS Oh good, I think back when it first came out there was a max size limitation. Glad my knowledge is out of date on that!
@pry Oh! Have you seen my blog post on peer to peer databases by any chance? https://blog.mauve.moe/posts/peer-to-peer-databases
I'm less into realtime document sync and more into optimizing for sparse replication of views. CRDTs are cool but they often share the same issues as oplogs. I think the latest version of automerge is pretty speedy though.
@pry @yala @quinn IIRC the datamodel and execution is similar to datalog? I'm mostly interested in "local-first" daabases so you can merge data from multiple sources as you network connectivity grows with local data being available.
Datalog over #EarthStar might also be cool to do some day.
@KatS Nice. Yeah I was considering just using Neo4j but I wasn't sure if the max node limit would be something I'd run into. I think my matrix server data alone leads me to at least a few million records.
- Pronouns
- they/them/it
- mauve+fedi@mauve.moe
- Matrix
- @mauve:mauve.moe
- Github/Gitlab/Discord
- @RangerMauve
Mod
Occult Enby that's making local-first software with peer to peer protocols, mesh networks, and the web.
Exploring what a local-first cyberspace might look like in my spare time.
Joined Apr 2022
