wbknl @twtxt.net
 (1y ago)

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
wbknl @twtxt.net
 (1y ago)

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
 (1y ago)

@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
gallowsgryph @prismdragon.net
 (1y ago)

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
Codebuzz @www.codebuzz.nl
 (1y ago)

(#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
Codebuzz @www.codebuzz.nl
 (1y ago)

(#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
Codebuzz @www.codebuzz.nl
 (1y ago)

(#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
movq @www.uninformativ.de
 (1y ago)

(#4w3ilsa) More interesting aspects about Antenna:

At first, I thought that Antenna acted like a “traditional” blog aggregator, but that’s not really the case. You know, with a blog aggregator, you would normally contact the owner and ask them to include your feed. That step is not needed with Antenna.

So, when someone publishes a blog/gemlog post and you would like to “reply” to it, you can just do that: Write your post and then publish the link on Antenna. This means your Gemini capsule doesn’t need to be well known in order to participate. If I read something interesting and would like to reply, I could do that right now – instead of having to wait for the webmaster of the aggregator to include/unlock my feed.

Also, it’s just arbitrary Gemini links in Antenna – unlike a blog aggregator, where everything is a blog post. So I just saw someone publishing a link titled “A wild twtxt appears” and that’s just a link to their twtxt file.

In many ways, this thing is a bit more like a forum than a blog aggregator. Or maybe you could also call it a “bus”.

#w72qu5a
movq @www.uninformativ.de
 (1y ago)

(#zloep2q) @lyse@lyse.isobeef.org Ahh, I see. So it’s not really a drama. 😅

(When the spec says “content is UTF-8”, then it kind of follows for me that I should set Content-Type: text/plain; charset=utf-8. Lots of feeds don’t do that, though, which is why jenny ignores the header altogether and always decodes as UTF-8.)

#cf2y3za