(#2uui3hq) @klaxzy@klaxzy.net Yes, if Germany actually opposes this. But so far, there’s only one guy that said something on a press conference. He does speak for the ā€œCDUā€ party, which is ā€œin commandā€ at the moment, but that’s about it. I don’t trust these people – not until I’ve actually seen them voting against Chat Control. 🄓


#ge7d62q

(#2uui3hq) @prologic@twtxt.net Where do I stand on ā€œChat Controlā€? How long of a response/rant do you want? šŸ˜… It’s a disaster. As I understand it, they want to spy on me directly on my devices before encryption even happens – jfc, no, fuck off. And since there are so many devices, they want to automate the scanning, which is the worst idea you could possibly have.


#2by6oua

(#2uui3hq) @klaxzy@klaxzy.net Why, because Germany is now listed as ā€œopposedā€ on fightchatcontrol.eu? I’m not so sure. This is just one guy (Jens Spahn) saying ā€œno we don’t want itā€. That’s not an ā€œofficialā€ stance, it’s very fragile and could change any minute. https://netzpolitik.org/2025/eu-ueberwachungsplaene-unionsfraktion-jetzt-gegen-chatkontrolle-innenministerium-will-sich-nicht-aeussern/


#acqh4la

I went on a short stroll in the woods and came across two great spotted woodpeckers. They were busy with their courtship display, I reckon, so it took them a while to notice me and escape into thicker parts out of sight. That was really awesome. There are a lot of apples and sloes now, looking really good. The cam issues still persist, though, I wish the photos were sharper. Also, I got the error that the function wheel was not adjusted correctly and alledgedly pointed between two options numerous times. And no, it was bang on a setting. https://lyse.isobeef.org/waldspaziergang-2025-10-07/


#yxqalkq

While working on the Discoverability for my twtxt client (it runs client-side) I found out that Chrome doesn’t allow to set a custom user agent. šŸ™ƒ

I thought it was a general thing for browsers, but it that was actually allowed in a newer specification, yet it’s still not implemented in Chrome, it does work in Firefox though.


#36qa76q

(#dvw775q) @zvava@twtxt.net @lyse@lyse.isobeef.org I also think a location based reference might be better.

A thread is a single post of a single feed as a root, but the hash has the drawback of not referencing the source, in a distributed network like twtxt it might leave some people out of the whole conversation.

I suggest a simpler format, something like: (#<TIMESTAMP URL>)

This solves three issues:

  • Easier referencing: no need to generate a hash, just copy the timestamp and url, it’s also simpler to implement in a client without the rish of collisions when putting things together
  • Fetchable source: you can find the source within the reference and construct the thread from there
  • Allow editing: If a post is modified the hash becomes invalid since it depends on [ timestamp, url, content ]

#altkl2a

Hello everyone! šŸ‘‹

After a long while away, I’m back on twtxt with this new feed.

Some of you might remember me as justamoment@twtxt.net, that was a test account I made for trying things out, but I ended up keeping it more than planned.

I also tried other social platforms in search of a place that felt right for me.

In the end twtxt was the one that ticked all of my boxes:

  • Slow social: it act more like a feed reader and I really appreciate that there’s no flood of content that I can’t keep up with.
  • No server needed: I absolutely love to have total control over my content, I tend to avoid having moving parts that might break, plus you can put your feed under version control and it’s all backed up.
  • Ownership: I can put my feed anywhere I want and nobody can decide if I can access it or not.
  • For hackers: a single .txt file allows me to join a community, how cool is that!

This is why I decided to build my own twtxt client, one that allows you to decide how the feed is presented on your ā€œinstanceā€.

It’s still in the making but I’ll try to share a bit of it once I defined how things should work.

Coincidentally, I discovered that @itsericwoodward@itsericwoodward.com and @zvava@twtxt.net were also building a twtxt client, seems like twtxt is set to grow!


#hyp22lq

So, in addition to HTTPS and Gemini, my twtxt should now also be available over Gopher (gopher://hashnix.club:70/0/~dce/twtxt.txt). Not sure who, if anyone, would need this; but since my tilde provides Gopher hosting, I’d may as well mirror my twtxt there as well.


#d4pnopq

You know, I think I do actually like it here better than my other social media. It’s slower and quieter, but it feels more organic and nobody’s trying to sell me anything, promote their podcast, or change the way I think. It’s just… nice!


#iy53q2q