The week before last I had the opportunity to deliver a "flash talk" at a work meetup. I opted to present a summary of what I've learned while adding support for Finger and Gopher protocols to the WordPress installation that powers DanQ.me (I also hinted at the fact that I already added Gemini and Spring '83 support, and I'm looking at other protocols).
The presentation is a shortened, Automattic-centric version of a talk I'll be delivering at Oxford Geek Nights tomorrow. If you're in or around Jericho, Oxford tomorrow, come say hi!
Read more or watch at: https://danq.me/yesterdays-internet-today-vienna
#finger #Gopher #Gemini #Spring83 #WordPress #Automattic #Oxford
#finger #Gopher #gemini #Spring83 #wordpress #automattic #oxford
I'm hoping to be speaking at Oxford Geek Nights 53 (22 Feb 2023, https://oxford.geeknights.net/)!
My working title: "Yesterday's Internet: Today!" I'm hoping to drum up some local interest in retro tech like Gopher and Finger as well as modern homages like Gemini and Spring '83!
#Oxford #OGN53 #internet #tech #gopher #finger #gemini #spring83
#oxford #ogn53 #internet #tech #Gopher #finger #gemini #Spring83
As the sun begins to set on Spring '83, I finally finish implementing my server for the protocol, way too late for anybody to pay attention or notice.
Read more: https://danq.me/2022/11/20/sts-6/
#article #gemini #indieweb #programming #publishedOnGemini #spring83 #technology #web #webDevelopment
#article #gemini #IndieWeb #programming #publishedongemini #Spring83 #technology #web #webdevelopment
Finally got around to implementing a super-lightweight (~20 lines of code, 1 dependency) Spring '83 key generator. There are plenty of others; nobody needs this one, but it's free if you want it:
https://github.com/Dan-Q/spring83-keygen
Read more: https://danq.me/2022/11/18/spring83-keygen/
#note #cryptography #javascript #openSource #spring83 #technology
#note #cryptography #javascript #opensource #Spring83 #technology
I've spent the summer playing with Robin Sloan's #Spring83 protocol but it's only now, as its nights get longer, that I've finally finished the key functionality of the server I wanted to implement - STS-6:
“On this front, I am an evangelist: arbitrary HTML and CSS should have a place in our social networks. They are so expressive, and they are available everywhere, on every device, essentially “for free”
Found on Robin Sloan comments on #spring83 aftermath https://www.robinsloan.com/lab/specifying-spring-83/#summer
I dream of a mastodon instance with posts made of HTML / CSS boxes only. No JS, no media, limited to a bunch of bytes, just like #spring83, alt text obviously, extra <3 for avatars made of a single HTML tag to style.
By the way I am still updating my #spring83 board https://0l0.lol/a1b78c1493c0393c629569742183906483ef0405a11c9e71afa7d3df583e0323
My board archive is online: https://raphaelbastide.com/spring83/boards/
The source code as a snippet https://gitlab.com/-/snippets/2384941 #spring83
#spring83 cousins:
◾ The Whole Earth Catalogue
◾ Surf clubs https://sites.rhizome.org/surfclubs/
Quick and dirty python script to generate an HTML archive of my #spring83 boards. Not public yet.
This is my #spring83 board URL, add it to your springfile and share me yours!
:cannabis_leaf: https://0l0.lol/a1b78c1493c0393c629569742183906483ef0405a11c9e71afa7d3df583e0323
@liaizon @johnjohnston @dajbelshaw @despens It reminds me of this fun experiment I made once: Twab, a prototype for a minimalist microblogging engine based on browser tabs. A self-refreshed page shows the last update in the <title>. To follow someone, just open their page in a tab!
https://lab.raphaelbastide.com/twab/whythisiscool.html
#spring83
To all #spring83 and web garden fans: in 2011 Olia Lialina and I created "Once Upon," fully working implementations of social networks for Netscape 4: http://1x-upon.com/
In that version of "facebook," every user can edit a message that is loaded in a frameset.
First thoughts about Robin Sloan's Spring '83 protocol.
This has much of the energy and community that was missing from Gemini.
Why, because the conversation is happening in the protocol, not the mailing list.
Also color, and fonts!