Today, (just this morning in AEST) I accidentally nuke my pod (twtxt.net). I keep backups, but unfortunately the recovery point objective (RTP) is at worst a month! đ¤Śââď¸ đą (the recovery time objective is around ~30m or so, restoring can take a while due to the size of the archive and index) â For those that are unfamiliar with these terms, they essentially relate to âhow much data loss can occurâ (RPO) and âhow quickly you can restore the systemâ (RTO).
This pod (twtxt.net) is back up and online. However weâve last the last ~5 days worth of posts yâall may have made on your feeds (for those that use this pod).
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.
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.
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.
So I am really curious, now that I am building upon @sorenpeter@darch.dkâs Timeline app, how other users write/add their twtxt, and how you follow conversations. Comment svp!
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.
(#i233nxq) Nice. Will this be the place to slowly build a better documentation and explaining some of the considerations for people who use and/or start using twtxt?
(#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.
(#frjxwvq) 𤣠Indeed. Itâs like using disallow is only pointing them to look for more stuff to index. Those few kBâs for a twtxt file, meh.. shouldnt even be a discussion.
(#frjxwvq) I agree. The idea of twtxt is to be an âopenâ format or standard. Regarding how often, the TTL could (should?) be honored, but open means open.
I swear, poking at Suckless tools have become such a great way for me to slowly learn coding in C. Just getting things working in st and surf has helped me better understand how things fuction better than most of the books Iâve been reading.
(#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.
There. Re-enabled the old subdomain url (twtxt.prismdragon.net), and just pointed it to the file in my twtxt fileâs url field. Either should work, so links wonât be broken.
(#mowsvgq) @prologic@twtxt.net Ah! Looks like the quickstart script I was working on got screwed up. Thanks for pointing it out. Should be fixed now. Also, I used to point the feed to the twtxt.prismdragon.net subdomain, but stopped because of a misbehaving nginx, so it may be something cached somewhere. Not sure where, though.
Rebuilding my twtxt file after deciding to return, and trying to get back into working on my fork of txtnix as a reason to continue learning Perl again.
(#z6ameqa) There is a reason P2P was invented. The streaming model will never work, but.. if they want to act like digital kings, then own the pain that comes with it.
(#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:
Agreed, but at the moment date+txt creates the unique timestamp
Preferably newest twt as the last line, will make for more structure.
