I still canāt believe we elected Trump twice⦠I didnāt vote for him. Maybe it WAS rigged.
@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. š„“
@movq@www.uninformativ.de@www.uninformativ.de if I understand chat-control voting correctly at least 14 member states needs to oppose, or, the supporting bloc must fall short of the 65% population threshold. by opposing, germany tossed the supporters below 65%⦠I also believe this is a great win agains folks like Ashton Kutcher and his lobbying Thorn co.
@prologic@twtxt.net Germany was listed as āopposingā on https://fightchatcontrol.eu/ for a while, now itās back to āundecidedā. According to netzpolitik.org, itās still debated. Also according to that page, there could be an important vote on the EU level on October 13/14.
The green party and the (far) left are opposing this (at least in Germany). Sadly, Germany is leaning more right with every year ⦠As for young people: The (far) left is the strongest party among young people, with the (far) right being the second strongest one. (https://www.tagesschau.de/wahl/archiv/2025-02-23-BT-DE/umfrage-alter.shtml) Is there cause for hope? I donāt know.
went to vote. got told i canāt vote because iām not registered. handed a form to fill out that i later learn is not in english.
go home and find out the problem is widespread among young voters like me.
fuck this country.
The Bad Joke of NYC Ranked Choice Voting ?~L~X https://thenewleafjournal.com/b/7tq
7 to 12 and use the first 12 characters of the base32 encoded blake2b hash. This will solve two problems, the fact that all hashes today either end in q or a (oops) š
And increasing the Twt Hash size will ensure that we never run into the chance of collision for ions to come. Chances of a 50% collision with 64 bits / 12 characters is roughly ~12.44B Twts. That ought to be enough! -- I also propose that we modify all our clients and make this change from the 1st July 2025, which will be Yarn.social's 5th birthday and 5 years since I started this whole project and endeavour! š± #Twtxt #Update
@eapl.me@eapl.me I honestly believe you are overreacting here a little bit 𤣠I completely emphasize with you, it can be pretty tough to feel part of a community at times and run a project with a kind of ādemocracyā or āvote by committeeā. But one thing that life has taught me about open source projects and especially decentralised ecosystems is that this doesnāt really work.
It isnāt that Iāve not considered all the other options on the table (which can still be), itās just that Iāve made a decision as the project lead that largely helped trigger a rebirth of the use of Twtxt back in July 1 2020. There are good reasons not to change the threading model right now, as the changes being proposed are quite disruptive and donāt consider all the possible things that could go wrong.
now() or the message's creation timestamp? I reckon the latter is the case, but it's undefined right now. Then we can discuss and potentially tweak the proposal.
@bender@twtxt.net Hehehe! :-D
@movq@www.uninformativ.de I have to admit, I didnāt follow the topic very closely, but I was under the impression that there were more votes on location-based addressing. But maybe Iām completely wrong. Anyway. I donāt have the energy to be part of a fundamental debate.
yarnd UI/UX experience (for those that use it) and as "client" features (not spec changes). The two ideas are quite simple:
This expands the usefulness of Twtxt / Yarn.social to:
- Sharing small posts
- Sharing links
- Sharing media
- Having long conversations
- Voting on topics, opinions or decisions
- RSVPing to virtual or physical events
š” I had this crazy idea (or is it?) last night while thinking about Twtxt and Yarn.social š
There are two things I think that could be really useful additions to the yarnd UI/UX experience (for those that use it) and as āclientā features (not spec changes). The two ideas are quite simple:
- Voting ā a way to cast, collect a vote on a decision, topic or opinion.
- RSVP ā a way to ārsvpā to a virtual (pr physical) event.
Both would use āplain textā on top of the way we already use Twtxt today and clients would render an appropriate UI/UX.
Am I the only one thatās confused by the discussions, and then the voting we had on the whole threading model? š¤ Iām not even sure what I voted for, but I know it wasnāt the one that won haha 𤣠(which Iām still very much against for based on an intuition, experience and lots of code writing lately).
dm-only.txt feeds. š
@andros@twtxt.andros.dev I give you not creating another file, but then Iād vote for commenting out DMs. See https://eapl.me/timeline/post/z5e2bna
Itās easier to find the DM in comments from your side, than asking all the client maintainers to add the regex =P
You can even use a Modified comment, such as
#! <DM content>
Or something like that
This approach is retro-compatible with current and older clients.
I do think integrating things like Salty.im might actually be a good idea. I can also see a future where we integrate other things like todo.txt and calendar.txt. Iād even love to see decentralised forms of āplain textā voting too.
twtxt, the voting period has started and will be open for a week.
https://eapl.me/rfc0001/
thanks @prologic!
@bender the idea of the RFC was to reach an agreement on a difficult problem, receiving proposals, and the voting is a simple count to gauge the sentiment of āis this a problem worth to be fixed?, are we committed to implement a change in our clients?ā
But thatās a fair point. What do the community expect? What do yāall expect?
For anyone following the proposals to improve replies and threads in twtxt, the voting period has started and will be open for a week.
https://eapl.me/rfc0001/
Please share the link with the twtxt community, and leave your vote on your preferred proposals, which will be used to gauge the perceived benefits.
Also, the conversation is open to discuss implementation concerns or anything aimed at making twtxt better.
@eapl.me@eapl.me Cool!
Proposal 3 (https://git.mills.io/yarnsocial/twtxt.dev/issues/18#issuecomment-19215) has the āadvantageā, that you do not have to āmentionā the original author if the thread slightly diverges. It seems to be a thing here that conversations are typically very flat instead of trees. Hence, and despite being a tree hugger, I voted for 3 being my favorite one, then 2, 1 and finally 4.
All proposals still need more work to clarify the details and edge cases in my opinion before they can be implemented.
@eapl.me@eapl.me Thank you for this!
I cast a test vote. Did it work? :-)
also Iāve made a draft of a voting page to receive preferences on each proposal
https://eapl.me/rfc0001/
Help me to play with it a bit and report any vulnerability or bug. Also any idea is welcome.
Itās been a long time since Iāve seen a project on Hacker News with 1300 votes (every few days something comes up with 600).
https://github.com/suitenumerique/docs
Hey everyone!
About the idea of improving the āthreadā extension, what if we set aside March 2025 to gather proposals and thoughts from everyone? We could then vote on them at the end of the month to see if the change and migration are worth it.
The voting could include client maintainers (and maybe even users too). That way, we get a good mix of perspectives before taking a decision in a decent timelapse.
What do you think? If this sounds good, we can start agreeing on this. Let me know your thoughts!
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
All commands sorted by votes https://www.commandlinefu.com/commands/browse/sort-by-votes>
Na, youāre spot on, @movq@www.uninformativ.de! The result is an expected, terrible disaster. It just seems the absolute catastrophy is delayed for another four years.
Even though Iām the last one who wouldnāt be glad about banning the nazis, Iām not a fan of banning parties in general. I believe that a healthy democracy has to withstand extremists. Whether itās still healthy is debatable. To me it appeared that the failed attempts to ban NPD in the past actually helped them gain more supporters.
The big established parties are all bad traitors. I blame them and their actions to help raise AfD. They just give a fuck about the ordinary people, theyāre only concerned about their private gain and power. I bet nothing will change, to the contrary, it will only get worse. The winners do have the chance to turn it for the better, but they just will not. No way, unfortunately.
But then, we must not forget that people are just dumb and stupid, too. Also, that wonāt change. AfD wonāt help these idiots either, but they still vote for them. I also donāt understand how there is still so much support for the other big parties left. Education is important. Very important. But I have the impression that weāre lacking it.
@bender@twtxt.net @prologic@twtxt.net The outcome was to be expected but itās still pretty catastrophic. Hereās an overview:

East Germany is dominated by AfD. Bavaria is dominated by CSU (itās always been that way, but this is still a conservative/right party). Black is CDU, the other conservative/right party.
The guy whoās probably going to be chancellor recently insulted the millions of people who did demonstrations for peace/anti-right. āIdiotsā, ātheyāre nutsā, stuff like that. This was before the election. He already earned the nickname āMini Trumpā.
Both the right and the left got more votes this time, but the left only gained 3.87 percentage points while the right (CDU/CSU + AfD) gained 14.72:

The Green party lost, SPD (āmid-leftā) lost massively (worst result in their history). FDP also lost. These three were the previous government.
This isnāt looking good at all, especially when you think about whatās going to happen in the next 4 years. What will CDU (the winner) do? Will they be able to āturn the ship aroundā? Highly unlikely. They are responsible for the current situation (in large parts). They will continue to do business as usual. They will do anything but help poor/ordinary people. This means that AfD will only get stronger over the next 4 years.
Our only hope would be to ban AfD altogether. So far, nobody but non-profit organizations is willing to do that (for unknown reasons).
I donāt even know if banning the AfD would help (but itās probably our best/only option). AfD politicians are nothing but spiteful, hateful, angry, similar to Trump/MAGA. If youāve seen these people talk and still vote for them, then you must be absolutely filled with rage and hatred. Very concerning.
Correct me if Iām wrong, @lyse@lyse.isobeef.org, @arne@uplegger.eu, @johanbove@johanbove.info.
twtxt (for now), although I see the community could be interested in.
I agree š, although itās easy to lose comments over time and are not so grouped by topic, itās not so easy to vote or make a survey about itā¦
I prefer a forum for that š
although I agree that it helps, I donāt see completely correct to leave the nick definition to the source .txt. It could be wrong from the start or outdated with the time.
Iād rather prefer to get it from the mentioned .txt nick metadata (could be cached for performance).
So my vote would to make it mandatory to follow @<name url> but only using that name/nick if the URL doesnāt contain another nick.
A main advantage is that when the destination URL changes the nick, itāll be automagically updated in the thread view (as happens with some other microblogging platforms, following the Jakobās Law)
Scientists to explore life creation from basic chemicals + 2 more stories
European scientists launch MiniLife project to create lab-made life, companies in Australia start mandatory climate disclosures, and discontent shapes global elections as incumbents lose votes. ā Read more
@quark@ferengi.one Yeah iām in deep red here. the governor race is getting split between a red and a maga that is running a write in.. but even if they split the vote 50-50% they will still be greater than what the blue will get.
@xuu@txt.sour.is done, and done, and done. The three of us dropped our mail-in ballots, and received confirmation they are counted. Living in a red state (well, kid said it is more like purple now) makes me sad, and mad, but I have done what I canāand that includes explaining things to others, and encouraging them to vote.
Unfortunately the US media has been making it a nail biter on purpose when in reality it is not. Get out and vote in numbers that cannot be denied. And then get everyone else around you to vote also.
Maybe one day enough states will make it into the NaPo InterCo to finally put the EC to rest.
Ocean Loop
ā Read more
Well crap. I think I just realized that if my profile photo was a person it could vote in this yearās election. Probably time for a new default one.
@prologic@twtxt.net the going theory is that openAI announced a new product that pretty much blew up the project of one of the board members. So that board member got 3 others to vote to fire Sam.
Red Line Through HTTPS
ā Read more
maxlenght?, I found a workaround by writing from Goryon on mobile, on PC i can simply change the limit with the inspector but isn't it there for a reason?
@mckinley@twtxt.net Agreed! š
Can we all vote on the new default being 1024 then perhaps? š¤
+1 from me
š Q&A: Letās discuss the removal of Editing and Deleting your last Twt. This is something @fastidious@twtxt.net has raised to me on IRC and something I find quite a valid approach to this. Over time I believe the utility and value of āEditingā and āDeletingā oneās last Twt isnāt as valuable as weād like and increased complexity and introduces all kinds of side-effects that are hard to manage correctly. I vote for the removal of this feature from yarnd, the mobile app nor API support this anywayā¦
@movq@www.uninformativ.de
With those two (Message-ID, and In-Reply-To) the hashing could become superfluous, and no longer needed. I would vote for that!
@saabeilin Voted 1 but the answer really depends on the context :)
Beautiful day for #voting https://t.co/9tvndcp9vJ