(#p2jw2xq) @sorenpeter@darch.dk I have znc running in a VM on my home theater/gaming PC for IRC.

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 🤞

(#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.

(#vqodnya) @prologic@twtxt.net Edited and published.

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.

(#zo4hvla) Thanks as well @prologic@twtxt.net 😃

(#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.

(#zo4hvla) Thank you, thank you @sorenpeter@darch.dk 😃

(#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.

Signature PDF | https://signature-pdf.framalab.org/signature

~bt | https://btxx.org/

https://unixdigest.com/

lxappearance pour configurer le darkmode sur dwm ?

ParaCyberBellum Security Review | https://library.paracyberbellum.io/review

Shrinkpdf : Shrink PDF files with Ghostscript | https://github.com/aklomp/shrinkpdf

Des favoris Nextcloud à twtxt et dmenu | https://galusik.fr/log/2021-12-12-dtwtbmk.html

twtxt via dmenu | https://git.sr.ht/~fredg/mybin/tree/master/item/twt

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 :)

(#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;)

https://renecoignard.com/

(#rksyfja) why can we both have a format that you can write by hand and better clients?

(#gg7ykkq) No, json is overhead. I love twtxt for simplicity where blog is just text file and not several json files where fields are repeated…

(#r7ee4ya) yes that works

(#2bsh7vq) (#<2024-09-24T12:53:35Z https://twtxt.net/user/prologic/twtxt.txt>) What does this screenshot show? The resolution it too low for reading the text…

(#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

(#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.

(#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.

(#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.

(#r6z66ta) lol, this flags looks like russian name

(#cu5bdda) Sorry but i dont undestand b. New feed author? But why?

(#j63urka) Aggred. But reading twtxt in raw form sounds… I can’t do this

Some more arguments for a local-based treading model over a content-based one:

1. The format: (#<DATE URL>) or (@<DATE URL>) both makes sense: # as prefix is for a hashtag like we allredy got with the (#twthash) and @ as prefix denotes that this is mention of a specific post in a feed, and not just the feed in general. Using either can make implementation easier, since most clients already got this kind of filtering.

2. Having something like (#<DATE URL>) will also make mentions via webmetions for twtxt easier to implement, since there is no need for looking up the #twthash. This will also make it possible to make 3th part twt-mentions services.

3. Supporting twt/webmentions will also increase discoverability as a way to know about both replies and feed mentions from feeds that you don’t follow.

Finally pubnix is alive! That’s im missing? Im only reading twtxt.net timeline because twtxt-v2.sh works slowly for displaying timeline…

Hello!

(#s2dhlvq) @movq@www.uninformativ.de I cases of these kind of “abuse” of social trust. Then I think people should just delete their replies, unfollow the troll and leave them to shouting in the void. This is a inter-social issue, not a technical issue. Anything can be spoofed. We are not building a banking app, we are just having conversation and if trust are broken then communication breaks down. These edge-cases are all very hypothetical and not something I think we need to solve with technology.

(#crmwgxq) Been thinking about it for the last couple of days and I would say we can make do with the shorter (#<DATETIME URL>)since it mirrors the twt-mention syntax and simply points to the OP as the topic identified by the time of posting it. Do we really need and (edit:...)and (delete:...) also?

(#zoktkgq) @prologic@twtxt.net what time in UTC?

(#kdtce4q) @falsifian@www.falsifian.org hiya from the Sunshine State (also known as a never-ending hell, LOL)!

(#xwvocwa) @falsifian@www.falsifian.org this one hits hard, as jenny was just updated today. :‘-(

(#l5452vq) @lyse@lyse.isobeef.org indeed! There is no “central authority” acting as witness, and notary. The more I think of it… LOL.

(#2p5ulxq) @movq@www.uninformativ.de I recognise him, but yes, he has aged quite a bit. I mean, I look at myself in the mirror and can’t, often, recognise myself. Ageing is a bitch! 😅

(#pgi2jkq) I mean, really, it couldn’t get any better. I love it!