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!

(#pgi2jkq) @movq@www.uninformativ.de perfect in every way. Configurable too! Thank you!

(#pgi2jkq) @movq@www.uninformativ.de yes, that’s perfect! <3

(#vq422aa) @eldersnake@we.loveprivacy.club I wanted to ask you, are you running Headscale and WireGuard on the same VPS? I want to test Headscale, but currently run a small container with WireGuard, and I wonder if I need to stop (and eventually get rid of) the container to get Headscale going. Did you use the provided .deb to install Headscale, or some other method?

(#xghlsva) @prologic@twtxt.net I read it. I understand it. Hopefully a solution can be agreed upon that solves the editing issue, whilst maintaining the cryptographic hash.

(#xghlsva) @prologic@twtxt.net I know the role of the current hash is to allow referencing (replies and, thus, threads), and it also represents a “unique” way to verify a twtxt hasn’t been tampered with. Is that second so important, if we are trying to allow edits? I know if feels good to be able to verify, but in reality, how often one does it?

@movq@www.uninformativ.de could it be possible to have compressed_subject(msg_singlelined) be configurable, so only a certain number of characters get displayed, ending on ellipses? Right now the entire twtxt is crammed into the Subject:. This request aims to make twtxts display on mutt/neomutt, etc. more like emails do.

(#3f36byq) @prologic@twtxt.net I don’t trust Google with anything, sorry, pass. Oh, and you need to sign in on your Google Account (or whatever they call it these days).

(#xghlsva) @prologic@twtxt.net how about hashing a combination of nick/timestamp, or url/timestamp only, and not the twtxt content? On edit those will not change, so no breaking of threads. I know, I know, just adding noise here. :-P

(#qgv3waq) @eldersnake@we.loveprivacy.club there has to be less reliance on a single point of failure. It is not so much about creating jobs in the US (which come with it, anyway), but about the ability to produce what’s needed at home too. What’s the trade off? Is it going to be a little bit more expensive to manufacture, perhaps?

(#xghlsva) @quark@ferengi.one It does not. That is why I’m advocating for not using hashes for treads, but a simpler link-back scheme.

(#kdtce4q) @prologic@twtxt.net :-D Thanks! Things can come in cycles, right? This is simply another one. Another cycle, more personal than the other “alter egos”.

(#kdtce4q) @aelaraji@aelaraji.com hey, hey! You are my very first reply! 👋🏻 Cheers!

Incredibly upset—more than you could imagine—because I already made the first mistake, and corrected it (but twtxt.net got it on it’s cache, ugh!) :‘-( . Can’t wait for editing to become a reality!

Alright. My first mentions—which were picked not so randomly, LOL—are @prologic@twtxt.net, @lyse@lyse.isobeef.org, and @movq@www.uninformativ.de. I am also posting my first image too, which you see below. That’s my neighbourhood, in a “winter” day. Hopefully @prologic@twtxt.net will add my domain to his allowed list, so that the image (and any other further) renders.

(#kikq2xa) Alright, announce_me set to true. Now, who do I pick to be my first mention? Decisions, decisions. Next twtxt will have my first mention(s). :-)

I have configured my twtxt.txt as simple as possible. I have setup a publish_command on jenny. Hopefully all works fine, and I am good to go. Next will be setting the announce_me to true. Here we go!

Everything starts at a “hello world”. At least around these parts; the nerdy parts.

RT https://hispagatos.space/@argumento/113092655322062316

The only thing we need to say to any liberal that calls for “unity” to “stop the rise of fascism” is “France 2024”.

(#qawz75q) i have an old laptop that should work OK as a coordination node and a couple of bitscope quattros that will work nice as a little compute array once I figure out how to manage them using netboot.

(#qawz75q) may as well accept that the big machine will be offline often during the new heatwave season. we’re already planning to move the environmental controls to a home assistant yellow so the zigbee integration and control system can live in the same device.

rm -fr, remove french-style: merciless colonizer. thief and destroyer of worlds.

maybe i’m overly restrained when it comes to making changes in a codebase, but i do a lot of the work in my head before committing to code.

running grey until after dark, it’ll be around 40C until tuesday in the daytime so I can’t really run the main server while I’m sat in my office. i’ll have some pine quartz blades or my quattro arrays up some day to handle the lower power stuff so running grey doesn’t mean the whole system is offline.

Releasing names of 900 alleged nazi war criminals who fled to #Canada could embarrass federal government, bureaucrats told. https://ottawacitizen.com/news/national/defence-watch/releasing-names-alleged-nazi-war-criminals-canada-could-embarrass-federal-government-bureaucrats

Some of the individuals and organizations consulted by LAC argued against releasing any of the information, warning it could be embarrassing or lead to prosecutions of the alleged war criminals.

the limitless babying of literal fucking nazis is getting really fucking old.