@bmallred@staystrong.run Oh, I hear you! It’s always after carefully proofreading and publishing that a typo suddenly pops up. :-) Not sure if amending your edit implementation is really worth it, but happy hacking in case you do.

@movq@www.uninformativ.de Luckily, they’re not made of steel as I would not have made it home with such heavy weights. :-D

@movq@www.uninformativ.de Fuck! So there aren’t any non-criminal printer vendors out there anymore. Very sad. I really don’t understand why this is not highly illegal in the entire world.

@prologic@twtxt.net Got you bro.

@prologic@twtxt.net What the heck. 🫠

@lyse@lyse.isobeef.org Lyse, the man with feet of steel. 🦾

@lyse@lyse.isobeef.org i appreciate you updating this with that info. been in the weeds at work so haven’t been tracking the conversation here much. let me sit on this for a bit because often times the edits are within seconds of first post so maybe maybe i just allow them within a certain time frame or do away with them all together. i really only do it because it bugs me once i notice the typo :)

@prologic@twtxt.net sure thing!
What about discussing it in https://git.mills.io/yarnsocial/twtxt.dev ?
The only con I see is that everyone would need to create an account there to participate.

hi there!! @arne@uplegger.eu \0/

@lyse@lyse.isobeef.org I meant “detect” lol 😂

@eapl.me@eapl.me There are several points that I like, but I want to highlight number 7. https://text.eapl.mx/a-few-ideas-for-a-next-twtxt-version #twtxt

@prologic@twtxt.net No edits anymore! \o/

I show you the website of Baldo, my little black cat (the pocket panther).
Website: https://baldo.cat/
Twtxt: https://baldo.cat/twtxt.txt
#catsoftwtxt

interesting.. my pod was looking for him as https://eapl.me/twtxt.txt but the correct path is https://eapl.me/tw.txt

I think @movq@www.uninformativ.de removed support for it in jenny. 🫠

@prologic@twtxt.net eapl.me comes up not found for me.

2025-03-02T13:20:00-07:00 (#<fmgas3a https://twtxt.net/user/prologic/twtxt.txt?t=2025-03-02T10:12:13Z>) @<prologic https://twtxt.net/user/prologic/twtxt.txt> its hard to change by consensus. Some things are won in implementation.

@prologic@twtxt.net its hard to change by consensus. Some things are won in implementation.

@lyse@lyse.isobeef.org Clients could detest edits 🤞

@movq@www.uninformativ.de Yeah, the ground was wet here, too. Some sections of esp. smaller paths had turned into mud holes. There are a few notorious spots. Oh well, you just have to press on. :-)

Forest animals also have to do the laundry, they even have a proper clotheshorse! See: https://lyse.isobeef.org/wanderung-zu-den-schurrenhoffuechsen-2021-05-15/07.jpg :-D

@movq@www.uninformativ.de Hahaha, stimmt! :-D

@bmallred@staystrong.run I forgot one more effect of edits. If clients remember the read status of massages by hash, an edit will mark the updated message as unread again. To some degree that is even the right behavior, because the message was updated, so the user might want to have a look at the updated version. On the other hand, if it’s just a small typo fix, it’s maybe not worth to tell the user about. But the client doesn’t know, at least not with additional logic.

Having said that, it appears that this only affects me personally, noone else. I don’t know of any other client that saves read statuses. But don’t worry about me, all good. Just keep doing what you’ve done so far. I wanted to mention that only for the sake of completeness. :-)

@andros@twtxt.andros.dev I’ve commented on the ticket: https://git.mills.io/yarnsocial/twtxt.dev/issues/14#issuecomment-19142

In all reality, though, I don’t see that our community will come to an agreement. Some folks just don’t want to give up on the content-based addressing scheme.

@prologic@twtxt.net I formed my opinion about this before reading/watching any additional media coverage. And yes, this is extremely bad. These two have no place on the “world stage”. They are deciding on our future. (And I am well aware that my country is heading into a similar direction – unless we stop it.)

I like this syntax, you have my vote, although I’d change it a bit like
#<Alice https://example.com/twtxt.com#2024-12-18T14:18:26+01:00>

Hashes are not a problem on PHP, I dont know why it’s slow to calculate them from your side, but I agree with your points.

BTW, did you have the chance to read my proposal on twtxt 2.0? I shared a few ideas about possible improvements to discuss:
https://text.eapl.mx/a-few-ideas-for-a-next-twtxt-version
https://text.eapl.mx/reply-to-lyse-about-twtxt

@lyse@lyse.isobeef.org Gotcha. That makes sense. Doesn’t hurt the systems but definitely can break the thread.

@andros@twtxt.andros.dev Oh, this system has an edit button so I can just update the twt as needed. It’s a custom implementation so just kind of through it in when I was building it out.

@lyse@lyse.isobeef.org Haha so true

@prologic@twtxt.net I wonder if we watched the same video.

@lyse@lyse.isobeef.org Lalala, ich höre nix. 🙉

Aber total unrealistisch. Die „Fokuszeit“ hätte überbucht sein müssen durch ein anderes, wichtiges Meeting. Sonst war ja kein Platz mehr dafür.

@lyse@lyse.isobeef.org Looks like a nice day. 😊 I tried to go on a quick walk, but it was really cold. And everything’s wet at the moment. Bah.

Clothespins in the woods, who would have thunk? 🥴

@lyse@lyse.isobeef.org What do you think about this? https://git.mills.io/yarnsocial/twtxt.dev/issues/14

@bmallred@staystrong.run Not an issue if you’re the doctor working there. :-)

@bmallred@staystrong.run Any edit automatically changes the twt hash, because the hash is built over the hash URL, message timestamp and message text. https://twtxt.dev/exts/twt-hash.html So, it is only a problem, if somebody replied to your original message with the old hash. The original message suddenly doesn’t exist anymore and the reply becomes detached, orphaned, whatever you wanna call it. Threading doesn’t break, though, if nobody replied to your message.

@andros@twtxt.andros.dev Do edits cause problems? I sometimes make them and didn’t realize it may be an issue

@osnews@feeds.twtxt.net Its been so long and never really thought about it.

• Arch was great but always had issues.
  
• Gentoo was great but not enough patience to compile when I need something quick for work.
  

I haven’t really looked back since I installed Void. Sometimes it is a pain when things don’t play well with MUSL but nothing that would make me change course.

@thecanine@twtxt.net I don’t mind the FUTO keyboard either but it is pretty basic. Going to have to try out helio

@thecanine@twtxt.net I like the clipboard function of HeliBoard very much.

@prologic@twtxt.net @david@collantes.us Good question, was this on live TV? I think it was? 🤔

@movq@www.uninformativ.de I utterly despise them. They are slime balls. These should not have been broadcasted like this. This is wrong, and rubbish, and shameful. I truly have no words.

@lyse@lyse.isobeef.org Schon. 😭

@arne@uplegger.eu That’s nice, but … where do they get the money for this? Must be expensive as heck. 😅

@andros@twtxt.andros.dev I don’t see a burst of new twtxt clients popping up. Yeah, the most recent ones are TwtxtReader and twtxt-el. Did I miss one? I agree with @david@collantes.us, looks normal to me. :-)

I’m also working on my rewrite at the moment, but that started… *looking at the git history*… oh wow! O_o Over two years ago! I just implemented jumping to the next/previous unread message.

I was on the hunt for new twts and found what I was looking for. Welcome to my timeline:
@javivf@adn.org.es @lafe@tilde.club @melyanna@tilde.club @nff@www.noizhardware.com @shreyan@twtxt.net

@movq@www.uninformativ.de I could show you some places here, in MeckPomm.
You may also want to renovate an old abandoned manor!?

@andros@twtxt.andros.dev

• System Design Interview Vol. 1 and 2, Alex Xu and Sahn Lam
  
• Designing Data-Intensive Applications, Martin Kleppmann

also @Andros, I see that if I open that URL on my browser, I see weird characters in the .txt file:
description = 🏗
Perhaps your nginx server is missing a Content-Type: text/html; charset=utf-8 header?
https://serverfault.com/a/975289

In timeline it looks OK however, I think it’s relying on

The file must be encoded with UTF-8
of the original spec:
https://twtxt.readthedocs.io/en/latest/user/twtxtfile.html

@andros@twtxt.andros.dev, I am getting:

Feed was redirected: https://twtxt.andros.dev -> https://twtxt.andros.dev/

Each time my client fetches your feed. It just doesn’t make any sense to me. Wouldn’t be both, pretty much, be the same (I noticed the /, yes)?

@movq@www.uninformativ.de woah! MV, for what I read on Wikipedia, is a fantastic, almost fantasy like state. Very low density on population. Matter of fact, they seem to be having issues with population growth, and will certainly welcome a bass player addicted, esoteric programmer, that would otherwise be a pretty quiet person. A win-win! :-D

@lyse@lyse.isobeef.org Yeah, well, what they want is for us to become hopeless and give up. We should just try. Not wait and … wait.