This is only first draft quality, but I made some notes on the #twtxt v2 proposal. http://a.9srv.net/b/2024-09-25

@prologic@twtxt.net Thanks for writing that up!

I hope it can remain a living document (or sequence of draft revisions) for a good long time while we figure out how this stuff works in practice.

I am not sure how I feel about all this being done at once, vs. letting conventions arise.

For example, even today I could reply to twt abc1234 with “(#abc1234) Edit: …” and I think all you humans would understand it as an edit to (#abc1234). Maybe eventually it would become a common enough convention that clients would start to support it explicitly.

Similarly we could just start using 11-digit hashes. We should iron out whether it’s sha256 or whatever but there’s no need get all the other stuff right at the same time.

I have similar thoughts about how some users could try out location-based replies in a backward-compatible way (append the replyto: stuff after the legacy (#hash) style).

However I recognize that I’m not the one implementing this stuff, and it’s less work to just have everything determined up front.

Misc comments (I haven’t read the whole thing):

• Did you mean to make hashes hexadecimal? You lose 11 bits that way compared to base32. I’d suggest gaining 11 bits with base64 instead.

• “Clients MUST preserve the original hash” — do you mean they MUST preserve the original twt?

• Thanks for phrasing the bit about deletions so neutrally.

• I don’t like the MUST in “Clients MUST follow the chain of reply-to references…”. If someone writes a client as a 40-line shell script that requires the user to piece together the threading themselves, IMO we shouldn’t declare the client non-conforming just because they didn’t get to all the bells and whistles.

• Similarly I don’t like the MUST for user agents. For one thing, you might want to fetch a feed without revealing your identty. Also, it raises the bar for a minimal implementation (I’m again thinking again of the 40-line shell script).

• For “who follows” lists: why must the long, random tokens be only valid for a limited time? Do you have a scenario in mind where they could leak?

• Why can’t feeds be served over HTTP/1.0? Again, thinking about simple software. I recently tried implementing HTTP/1.1 and it wasn’t too bad, but 1.0 would have been slightly simpler.

• Why get into the nitty-gritty about caching headers? This seems like generic advice for HTTP servers and clients.

• I’m a little sad about other protocols being not recommended.

• I don’t know how I feel about including markdown. I don’t mind too much that yarn users emit twts full of markdown, but I’m more of a plain text kind of person. Also it adds to the length. I wonder if putting a separate document would make more sense; that would also help with the length.

OAuth for Browser-Based Apps Working Group Last Call!
The draft specification OAuth for Browser-Based Applications has just entered Working Group Last Call! ⌘ Read more

I just “published” a #draft on my blog about “How I’ve implemented #webmentions for twtxt” (http://darch.dk/mentions-twtxt), so I wanted to know from you guys if you see yourself doing a similar thing with yarnd @prologic@twtxt.net or others with custom setups?

OAuth for Browser-Based Apps Draft 15
After a lot of discussion on the mailing list over the last few months, and after some excellent discussions at the OAuth Security Workshop, we’ve been working on revising the draft to provide clearer guidance and clearer discussion of the threats and consequences of the various architectural patterns in the draft. ⌘ Read more

New Draft of OAuth for Browser-Based Apps (Draft -11)
With the help of a few kind folks, we’ve made some updates to the OAuth 2.0 for Browser-Based Apps draft as discussed during the last IETF meeting in Philadelphia. ⌘ Read more

Maxime Buquet: Versioning
I finally took time to setup a forge and some old drafts turned up. I am
publishing one of them today as is even though it’s 4 years old
(2018-08-07T13:27:43+01:00). I’m not as grumpy as I was at the time but I
still think this applies.

Today I am grumpy at people’s expectation of a free software project, about
versioning and releases. I am mostly concerned about applications rather than
libraries in this article but I am sure some of this would apply to libraries
as well.

Today we were discussing ab … ⌘ Read more

I was just about to write a long response to a discussion I saw online. But while writing it, I realized that I have an opinion, but I can’t express it properly and somehow I don’t have anything to contribute. So I deleted my draft. I don’t have to give my two cents on everything. 😅 ⌘ Read more

China to tighten grip on social media comments, requiring sites to employ sufficient content moderators
The draft regulation demands platforms to employ a content moderation team commensurate with the scale of the services. ⌘ Read more

if your eag profile doesn’t say ‘neartermism’, you’ll automatically be drafted into the deepmind potential hires mailing list

It’ll track a bunch of finger(1) endpoints and let you see what’s new. Very early draft. Not actually a social network, more an anti-social network for ‘80s CompSci transplants. :-)

My website is very Piling. look at the todo list: https://niplav.github.io/todo.html! i can’t tell you much about how it will look like in a year, but i can tell you that it won’t shrink. it’s piling. everything is piling up, forgotten drafts, half-finished experiments, buggy code—fixed over time, sure, but much more slowly than the errors come rolling in. it’s an eternal struggle.

I didn’t get around to blogging about the fact that Miniflux recently got a new version. With it, if an entry doesn’t have a title, it finally shows a snippet of the content instead of just the URL as the title. A great new feature if you follow a lot of micro blogs. Regarding micro-blogs, I’m also in the process of reading Manton Reece’s book draft. ⌘ Read more

phew. took me long enough, but I finally got an initial draft for using the monome grid in C directly via libmonome: !grid_tutorial

Isode: Draft, Review & Release ⌘ Read more…

⌘ Read more…

Antivax, How are they funded? Investigating ad trackers with Gephi and the DMI Tracker Tracker tool - First Draft ⌘ Read more…

@prologic@twtxt.net looking through the drafts it looks like it actually used SRV records as recently as 2018 😵

@xuu@txt.sour.is Not too happy with WKD’s use of CNAME over SRV for discovery of openpgpkey.. That breaks using SNI pretty quick. I suppose it was setup as a temporary workaround anyhow in the RFC..

Working Draft 435 ?~L~X https://notiz.blog/a/5cg

First Draft of OAuth 2.1 ⌘ https://aaronparecki.com/2020/03/11/14/oauth-2-1

Implicit flow in the Security BCP draft -14 ⌘ https://aaronparecki.com/2020/02/12/49/implicit

@lucidiot@tilde.town haha why not :P But for now it’s all in personnal notes or drafts ^^

rebooting-the-web-of-trust-spring2018/making-dids-invisible-with-petnames.md at petnames · cwebber/rebooting-the-web-of-trust-spring2018 · GitHub https://github.com/cwebber/rebooting-the-web-of-trust-spring2018/blob/petnames/draft-documents/making-dids-invisible-with-petnames.md

post-N235 Prolog prologue (Working draft) https://www.complang.tuwien.ac.at/ulrich/iso-prolog/prologue

Parrigues Tarot (draft) | Emily Short’s Interactive Storytelling https://emshort.blog/2018/06/26/parrigues-tarot-draft/

Band name of the day: vomit draft

How I Turned My Discarded Novel Drafts Into an AI | Literary Hub http://lithub.com/how-i-turned-my-discarded-novel-drafts-into-an-ai/

Second OpenID Connect Implementer’s Drafts Approved ?~L~X https://notiz.blog/t/1Xw

DisNix paper accepted at HotSWUp
The paper “Atomic Upgrading of Distributed Systems” (by Sander
van der Burg, Eelco Dolstra and Merijn de Jonge) has been
accepted for presentation at the First ACM Workshop on Hot\
Topics in Software Upgrades (HotSWUp). A draft\
of the paper is available. It describes Sander’s master’s
thesis research on DisNix, an extension … ⌘ Read more