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

(#5vbi2ea) @falsifian@www.falsifian.org Yeah, delete requests feel very odd.

(#y2t2tnq) @prologic@twtxt.net I wish that was true! But I reckon there is still heaps of old stuff out there, that was created on a Windows machine. :-D And I wouldn’t be surprised if even today in that environment a new file does not make use of UTF-8.

(#bz7aevq) @quark@ferengi.one I’m not convinced. :-D

(#xvlyzfa) @quark@ferengi.one @movq@www.uninformativ.de Yep, they’re all RFC3339. Obviously, +02:00 and +01:00 are best, because I use them! :-P In all seriousness, Z might be the best timezone, as it is shortest. And regarding privacy, it leaks the least information about the user’s rough location. But of course, one can just look at the activity and narrow down plausible regions, so that’s a weak argument.

(#y2t2tnq) @falsifian@www.falsifian.org I can confirm, it’s fixed. Thank you! Indeed, this is some wild quoting.

I still do not understand why the encoding suddenly broke, though. :-? Anyway. I concentrate on my rewrite and do things the right™ way. ;-) Still long ways to go.

(#hwv7iya) @bender@twtxt.net I know, I know… A relative time in a static HTML document is questionable at best. ;-)

(#xzgj32a) Now WTF!? Suddenly, @falsifian@www.falsifian.org’s feed renders broken in my tt Python implementation. Exactly what I had with my Go rewrite. I haven’t touched the Python stuff in ages, though. Also, tt and tt2 do not share any data at all.

By any chance, did you remove the ; charset=utf-8 from your Content-Type: text/plain header, falsifian?

(#qlgshhq) @movq@www.uninformativ.de Non-ASCII characters were broken. Like U+2028, degrees (°), etc.

Turns out I used a silly library to detect the encoding and transform to UTF-8 if needed. When there is no Content-Type header, like for local files, it looks at the first 1024 bytes. Since it only saw ASCII in that region, the damn thing assumed the data to be in Windows-1252 (which for web pages kinda makes sense):

// TODO: change default depending on user's locale?
return charmap.Windows1252, "windows-1252", false

https://cs.opensource.google/go/x/net/+/master:html/charset/charset.go;l=102

This default is hardcoded and cannot be changed.

Trying to be smart and adding automatic support for other encodings turned out to be a bad move on my end. At least I can reduce my dependency list again. :-)

I now just reject everything that explicitly specifies something different than text/plain and an optional charset other than utf-8 (ignoring casing). Otherwise I assume it’s in UTF-8 (just like the twtxt file format specification mandates) and hope for the best.

Hmmmm, I somehow run into an encoding problem where my inserted data end up mangled in the database. But, both SQLite and Go use UTF-8. What’s happening here? :-?

(#kshd6sq) @prologic@twtxt.net Correct. :-D

(#r4msqlq) @prologic@twtxt.net I’m basically with @movq@www.uninformativ.de, but in contrast to him, I’m not looking forward to implement something like that. :-)

A feed URL is plenty good enough for me. Since I only fetch feeds that I explicity follow, there is some basic trust in those feeds already. Spoofing, impersonation and what not are no issues for me. If I were to find out otherwise, I just unsubscribe from the evil feed. Done.

To retrieve public feeds, I just rely on TLS. Most are served via HTTPS. If a feed is down, I’m not trying to fetch it from some other source, I just wait and try again later. So signed messages/feeds are not a use case I’m particularly benefitting from.

To me, it’s just not worth at all adding this crypto complexity on top.

(#t2kaoma) Found it: https://github.com/buckket/twtxt/issues/157

(#kshd6sq) @prologic@twtxt.net Yeah, but I reckon we can kill both birds with one stone. If we change it to support edits, it should be fairly easy to also tweak it to support feed URL changes. Like outlined in my first reply: https://twtxt.net/twt/n4omfvq The URL part sounds way easier to me. :-)

(#q5p74va) @sorenpeter@darch.dk There was or maybe still is a competing proposal for multiline twts that combines all twts with the same timestamp to one logical multiline twt. Not sure what happened to that, if it is used in the wild and whether anyone “here” follows a feed with that convention. “Our” solution for multiline twts is to use U+2028 Unicode LINE SEPARATOR as a newline: https://dev.twtxt.net/doc/multilineextension.html.

(#wnq5qva) @movq@www.uninformativ.de What’s you definition of “complete thread”? ;-) There might be feeds participating in the conversation that you have no idea of.

But yes, this has a nice discoverability bonus. And even simpler than a hash, that’s right.

(#otqhota) @movq@www.uninformativ.de Yeah, I think so.

(#pvju5cq) Keys for identity are too much for me. This steps up the complexity by a lot. Simplicity is what made me join twtxt with its extensions. A feed URL is all I need.

Eventually, twt hashes have to change (lengthen at least), no doubt about that. But I’d like to keep it equally simple.

(#yudn25q) @prologic@twtxt.net When the next hype train departs. :-)

(#r3mkxya) @stigatle@yarn.stigatle.no Yeah, the sudden drop makes it feel worse than it is. It made me wear a beanie and gloves on my bike ride on Friday evening. In a few weeks I consider the same temperatures not an issue anymore, maybe even nicely warm. ;-) The body is fairly quick to adopt, but not that fast.

I just saw that we’re supposed to hit 19°C mid next week again. Let’s see.

(#54t2ohq) @off_grid_living@twtxt.net Oh dear, what an epic adventure! Terrible at the time, but hilarious to tell later on. :-D

I do like this photo a lot. It brings up memories of cool scouting trips.

(#q5gm3da) @off_grid_living@twtxt.net Hahaha, this is really great, I love it! :-D

(#esfevsa) @off_grid_living@twtxt.net Still a bit different, but this reminds me of the rusk boy on the Brandt boxes which is kinda iconic over here: https://cdn.idealo.com/folder/Product/2151/8/2151814/s1_produktbild_max/brandt-der-markenzwieback-225-g.jpg They should switch to this photo. :-)

(#nhi4iya) @off_grid_living@twtxt.net It’s kinda cool to see how small cars were back in the days. Especially the left one looks really tiny.

(#zbkf3oq) Happy birthday @prologic@twtxt.net! :-)

(#kmopgpq) Ta, @bender@twtxt.net! Correct, apart from resizing, no further processing on my end. That’s just the Japanese sunset photo engineer’s magic. :-) In all it’s original glory (3.2 MiB): https://lyse.isobeef.org/abendhimmel-2024-09-13/02.JPG

(#nfuyjyq) @off_grid_living@twtxt.net Looks like you’re describing a captcha. They do not really work. Bots seem to solve them, too.

(#r3mkxya) @movq@www.uninformativ.de Thanks! Yeah, one week for autumn and spring must be enough. Or so the weather thinks. Looks like there is only on or off.

(#bhnihfq) @prologic@twtxt.net Oh, that’s a lovely campfire! Seeing them always makes me smile. Enjoy your time in nature with your loved ones.

Cool sunset when I went to the scouts: https://lyse.isobeef.org/abendhimmel-2024-09-13/

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.

(#agpuufq) ve tambien https://hispagatos.space/@argumento/113086543221571421

(#agpuufq) Cold war mentality is thinking one side is the absolute good and the other the absolute evil. Cold war mentality froze thousands of people’s from fighting for themselves for fear of being accused of communism or, on the other side of the iron wall, of falling for the American imperialist agenda. Cold war mentality is a prison our rulers create to make us hate their enemies, creating a division between fellow proles and unity with our masters.

When we say “no war but class war”, we mean that we’ll never raise a rifle against “the evil hordes” of the other side, since we know those “hordes” are made of people just like us, proles. When we say “no war but class war” we understand that our rulers are as evil as the tyrant on the other side. That the crimes of one mirror the crimes of the other, that the elites, in their need to rule the world, know no boundaries to their cruelty. And that makes them equal.