This is a #lisp machine for network protocols. Initially in pursuit of a social forum focused on link sharing.
as #startups and free projects alike rush to implement some #IETF RFC adding only 'but on the web'. I aim to define a modular protocol server which can support an arbitrary number of network protocols as a network daemon. Our POC in this endeavour will be to build an #NNTP -like protocol daemon which gateways to #IPFS storage. The content held in this system can be consumed by arbitrary clients; a web application presenting #reddit -like services would be just one of many potential clients, although it is likely that Gnus for Emacs will be the first one. https://codeberg.org/fade/callisto
Reminder: travel grant applications due by May 10, 2024
We're pleased to offer a number of Diversity Travel Grants to support early-career academics and PhD students from under-represented groups to attend the Applied Networking Research Workshop (ANRW'24) and IRTF meetings co-located with the #IETF 120 Meeting in Vancouver, Canada, in July 2024. https://www.irtf.org/travelgrants/
@smallcircles I saw the reply button, but that just opens a regular mailto window that would result in a top-level thread reply, instead of the reply to a specific message that I would want. 😦
Maybe it's kind of a generational divide, but joining a mailing list just to quickly chime in on an ongoing conversation seems like a lot... but I'll consider it.
I do appreciate how, when writing #IETF drafts using the markdown template and GitHub, every writing session starts with spending 30 minutes debugging Python and Ruby build issues – this always make me feel more productive
More straws on the #DNS camel: another #IETF draft to amend RFC 1035. :)
"4. Updates to RFC 1035
A DNS message with OPCODE = 0 (QUERY) MUST NOT include a QDCOUNT parameter whose value is greater than 1. It follows that the Question Section of a DNS message with OPCODE = 0 MUST NOT contain more than one question.
A DNS message with OPCODE = 0 (QUERY) and QDCOUNT > 1 MUST be treated as an incorrectly-formatted message. The value of the RCODE parameter in the response message MUST be set to 1 (FORMERR)."
domain names cost too much, literally the fakest economy in existence. Yhey just need to cover the funding of ICANN and the IETF which should be no more than 50 furrys (network engineers) and 10 old guys on a board (they work for free they like it).
Hot on the heels of a post I wrote 4 years ago, wouldn't it be useful to have a well-known URl for user avatar images? When I sign up to a web service, I don't want to faff around uploading an image to use as my avatar. I want that service to look at my […]
Going through some of my old photos. I found the photo where we discussed on May 18, 2004 in New-York (20 years ago), where should be developed the Atom feed format: #W3C or #IETF.