@jerry this is exactly why I included some default blocklists in the fedi impl we're working on at distributed press. Having even the bare minimum like garden fence means not having to deal with a large amount of garbage for new and vulnerable users.
While some folks are trying to move towards "Lets put everything into WASM and WebGPU" I wish more folks would move towards "Lets put everything into standard data formats and let users bring their UI to the data more easily".
Are there any #lisp flavors that aim to transpile to other programming languages? Seems like it'd be handy to have a way to make libraries than can be reused in other langs. Lisp just seems like a simple enough set of syntax for transpiling.
@shauna What OS? Notepad++ on Windows worked great. On Linux I have gotten decent mileage from `nano` (along with making the keybindings closer to what graphical editors use).
I am not aware of web based ones that don't start stuttering as the file size gets huge.
The DNSLink stuff is a bit iffy for hypercore, but I'll be fixing that up tomorrow.
Now stuff can be published via Distributed Press, and viewed via @agregore
What's cool is that in addition to keeping your content online, you can easily configure it to set up DNS keys for you by delegating with an NS DNS entry for the `_dnslink` subdomain on your domain.
Looks like #ActivityStreams over #IPLD is very likely to be a thing some time this year!
Currently drafting up the grant milestones and figuring out budget.
Likely #rust or #golang to start along with some general #RDF goodies.
My hypothesis is that baking database indexes within the data itself will make it efficient to load people's posts over #p2p without needing to rely as much on indexing servers.
Occult Enby that's making local-first software with peer to peer protocols, mesh networks, and the web.Also exploring what a local-first cyberspace might look like in my spare time.