The path here is to move everything to #htmx & #hyperscript running on #fzx (this will incorporate/depreciate my work on #ApresWeb)
I have a lot to say about why, but its way too much to write in this little box.
Got to spend a couple hours hacking on #apreposterus this morning and it was bliss. It’s been a great project to polish my #golang skills because at its heart it’s just basic operations so I can focus on the details.
@vertigo @krux I’m not sure if I’ve mentioned this here but I’m porting my old email-driven blog (https://code.jasongullickson.com/jjg/preposter.us) to #golang and making it generate #ApresWeb
Spent more time on #apreposterus today and it’s beginning to generate almost usable output!
https://code.jasongullickson.com/jjg/apreposterous
A few more hours and I think I’ll be ready to stand-up an alpha server.
I’m not sure how important it is to know if anyone else is using the #apresweb subset. Existing browsers will render it with no changes and new browsers designed for it will simply reject sites that are not compliant.
My biggest problem with Gemini is the TLS requirement, which rules-out using it on small machines. When I came to the conclusion that Gemini won’t work for me, I started designing something new and realized that if I could get what I need using a subset of HTML, I could re-use a lot of existing work and focus on building new stuff where it’s the most fun for me, the small machines.
Got to spend a couple hours working on the successor to #preposterus: #apreposterus.
It’s basically Preposterus rewritten in #golang to output an #ApresWeb blog.
https://code.jasongullickson.com/jjg/preposter.us
https://code.jasongullickson.com/jjg/apreposterous
Jason
requiem 🦫