One of my quirks—don’t ask me why—is collecting backpacks, bags, patches, and watches, especially those related to aviation and the military. Just yesterday, I added a Direct Action Messenger bag and a 5.11 backpack to my collection.


#7owfudq

I feel exhausted, burned out. The workload just keeps piling up, and there’s less and less time to rest. What keeps me going are these little escapes to the smolweb.


#rnrnbsq

@wbknl@twtxt.net i’m currently working on my cyberpunk novella: W3bK3rN3l’s Radio Outpost

In the neon haze of a crumbling world, where the sky pulsed with the electric glow of a million flickering screens, Dmitri (aka dMHz) stood sentinel over the void. The echoes of the Russian military compound he once called home lingered like ghosts in his mind—flashes of chaos, the roar of an explosion that shattered the air and his life, propelling him into the cold embrace of space aboard a battered Gemini capsule.


#exjgoha

Another thing off my TODO list after an otherwise busy and tiring day. Now I have a new accessible email and XMPP account with Disroot, so I don’t have to deal with iCloud’s growing walled garden, or xmpp.jp’s reputation of being overrun by spammers.


#mw33trq

(#cs3mjwa) We cannot bulletproof it, no matter which solution we use. If somethings changes, most likely something breaks. However a Nick+Timestamp is fairly unique hash, even if someone for whatever reason had the same nick. For display nick@url would make that unique and recognizable again.


#gmctx4q

(#pqhbula) Well, as for a new UUID it’s a thought to combine the timestamp+username or timestamp+url to create a unique id. In this scenario I think the first would probably be favourable. This way if someone decides to use a different url (most likely they will stick to their nickname) UUID’s will still hold up.

Adding to that, we could implement a version variable in the meta, adapt code to either read the old or new format UUID, so older threads won’t break.


#zxzz7ta

(#lnlbnsq) Well I have been working on an update of Timeline, mainly improving speed. Getting a multiple of feeds can really become a big fetch. So I would advocate for ideas to maintain performance.

Regardings your points:

  1. Agreed, but at the moment date+txt creates the unique timestamp
  2. Preferably newest twt as the last line, will make for more structure.

#eween7q

Aujourd’hui, petits changements de formatage de mes documents sur le style RFC. Le titre apparaît désormais au centre et en haut de page. On a aussi la date de rédaction suivie de la date de dernière mise à jour. Que c’est beau :)


#inevwwq

(#tukxcsq) @prologic@twtxt.net YES James, it should be up to the client to deal with changes like edits and deletions. And putting this load on the clients, location-addressing with make this a lot easier since what is says it: Look in this file at this timestamp, did anything change or went missing? (And then threading will not break;)


#d4wfgda

(#j63urka) (#<2024-09-24T12:45:54Z https://twtxt.net/user/prologic/twtxt.txt>) @prologic@twtxt.net I’m not really buying this one about readability. It’s easy to recognize that this is a URL and a date, so you skim over it like you would we mentions and markdown links and images. If you are not suppose to read the raw file, then we might a well jam everything into JSON like mastodon


#gg7ykkq

(#a73p7ma) (#<2024-09-24T12:44:35Z https://twtxt.net/user/prologic/twtxt.txt>) There is a increase in space/memory for sure. But calculating the hashes also takes up CPU. I’m not good with that kind of math, but it’s a tradeoff either way.


#ipfcooq

(#rksyfja) (#<2024-09-24T12:39:32Z https://twtxt.net/user/prologic/twtxt.txt>) @prologic@twtxt.net It might be simple for you to run echo -e "\t\t" | sha256sum | base64, but for people who are not comfortable in a terminal and got their dev env set up, then that is magic, compared to the simplicity of just copy/pasting what you see in a textfile into another textfile – Basically what @movq@www.uninformativ.de also said. I’m also on team extreme minimalism, otherwise we could just use mastodon etc. Replacing line-breaks with a tab would also make it easier to handwrite your twtxt. You don’t have to hardwrite it, but at least you should have the option to. Just as i do with all my HTML and CSS.


#lpc2tia

(#bz2mpca) (#<2024-09-24T12:34:31Z https://twtxt.net/user/prologic/twtxt.txt>) WebMentions does would work if we agreed to implement it correctly. I never figured out how yarnd’s WebMentions work, so I decide to make my own, which I’m the only one using…

I had a look at WebSub, witch looks way more complex than WebMentions, and seem to need a lot more overhead. We don’t need near realtime. We just need a way to notify someone that someone they don’t know about mentioned or replied to their post.


#nmi6qwq