Steven Deobald
3rd wave open source, vipassana, chai, fixies, other stuff.
while prototypes and research are cool, the @modal@mastodon.design work on reflection feels like some of the first production-grade local-first software delivered in earnest, and built to last. this article is a great summary of their work so far:
https://www.prototypefund.de/en/blog/the-road-to-a-local-first-app-ecosystem
spent all day ripping apart the rotten ramp behind our new house. found an even more rotten deck joist hidden behind it.
whether a real-world construction project or a software project, it's always yaks all the way down. 🐂
maybe i'll get to build stairs next week.
ctos and senior staff engineers in my alumni networks going "please star my github project, bro" but it's just a bash script with a loop and a markdown file named SKILL.md which contains the words "ok, try even harder this time, robot"
what is even happening
i think a big part of why i love immutable data is because i'm afraid of computers
please, please apply for this.
not sure? doubtful? not confident your work is worth it? apply! you have absolutely nothing to lose.
this program was built for *you.*
मेरा शरीर टूट रहा है।
अभी नहीं, अभी नहीं।
यह टूटगा। लेकिन अभी नहीं।
तो मुझे काम करने दो।
spent the entire day thinking and writing about community infrastructure and solutions to the "repeatability problem" (albeit in a very different context).
this is a great example of designing for repeatability, and one of the organizational choices that makes gnome such a delight to use today. ❤️🙏
@nekohayo savebutton already does archiving but the archival code is shit because i wrote it. 😂
the modern web is broken and snapshots really demand a headless browser. will do eventually but it’s a pain. i’m very tempted by https://gwern.net/gwtar but i’m cognizant that might just be nerd fetishization of a neat hack, on my part.
currently the archives can be bounced. maybe i should also make those timestamped/immutable, but they’re heavy to sync (compared to a .url file) and not a primary focus yet.
i’m also aware i need to add tombstones for erasure of saves. but i want to get the ux right first before i worry about compliance-type things. i’m also sure the tombstones can’t contain the original filename in case someone wants to erase super-embarrassing-sexy-image.gif because super-embarrassing-sexy-image.gif.tombstone is probably still incriminating if their spouse finds out. but i kinda hate the idea of obfuscating tombstone names so i haven’t built them yet.
@matk@mastodon.social @razze@osna.social oh no now i need to move all my git repos out of ~/work
oh man, this is too good. company whose entire brand is "calendly, but open source sort of" gets rid of the second half. now just:
"calendly, but slightly crappier."
excellent.
(this is why saas apps need to be #upstreamfirst ... but that's always been true.)


