In-reply-to » My very strong opinion on the use of Twtxt is if you intend to use it, you should be prepared to let people pull your feed or at least check it and regular rentals.

đŸ€Ł Indeed. It’s like using disallow is only pointing them to look for more stuff to index. Those few kB’s for a twtxt file, meh.. shouldnt even be a discussion.

​ Read More

IMHO, the original spec had it right when it said (paraphrased) “just upload your tw.txt file wherever”. The essence of micro-blogging, as opposed to full-scale blogging, is low friction and low stakes. Imposing a norm that you can’t just use any ol’ url, looking down on people with insufficently cool urls (as in “Cool URIs don’t change” https://www.w3.org/Provider/Style/URI), puts up too much of a barrier to entry.

​ Read More
In-reply-to » After the behaviour of a clearly very angry feed author over the past few days, I'm very tempted to give up on Twtxt and allow it to go back to being dead. What really is the point of building and supporting a way to exchange little pieces of text with one another in a completely decentralised way, if you're just going to keep humping up against such hostility? I don't know why I do this anymore.

the test would be: how often does unwanted content get pushed on your feed? do incongruent posters easily disrupt harmonious connections? &c. less about the community, more about how the social dynamics play out as various groups and individuals interact.

​ Read More

Simplified twtxt - I want to suggest some dogmas or commandments for twtxt, from where we can work our way back to how to implement different feature like replies/treads:

  1. It’s a text file, so you must be able to write it by hand (ie. no app logic) and read by eye. If you edit a post you change the content not the timestamp. Otherwise it will be considered a new post.

  2. The order of lines in a twtxt.txt must not hold any significant. The file is a container and each line an atomic piece of information. You should be able to run sort on a twtxt.txt and it should still work.

  3. Transport protocol should not matter, as long as the file served is the same. Http and https are preferred, so it is suggested that feed served via Gopher or Gemini also provide http(s).

  4. Do we need more commandments?

​ Read More

Google tool makes AI-generated writing easily detectable
Google DeepMind has been using its AI watermarking method on Gemini chatbot responses for months – and now it’s making the tool available to any AI developer ⌘ Read more

​ Read More

Ethical framework aims to counter risks of geoengineering research
As interest grows in geoengineering as a strategy for tackling global warming, the world’s largest association of Earth and space scientists has launched an ethical framework as a guide to responsible decision-making and inclusive dialogue. ⌘ Read more

​ Read More
In-reply-to » So, uh, did anyone but me notice that the last character of a twt hash is always either an a or a q? Which is the natural consequence of taking the last digit in the base32 representation of a 256-bit hash -- 256 is not evenly divisible by 5 ! That final character is made up of one bit of actual information and 4 bits of padding.

@prologic@twtxt.net With respect, a client can not identify whether an edit took place. Not unless that same client witnessed both the original twt and the edited one. This won’t be the case if a person you’re following is joining a thread started by people you aren’t following after the first twt of that thread has already been modified. Or if you’re knocked offline by a multi-hour power outage that spans then entire time window between a twt getting uploaded and modified.

​ Read More
In-reply-to » So, uh, did anyone but me notice that the last character of a twt hash is always either an a or a q? Which is the natural consequence of taking the last digit in the base32 representation of a 256-bit hash -- 256 is not evenly divisible by 5 ! That final character is made up of one bit of actual information and 4 bits of padding.

It’s pretty hard to follow though, with the discussion being spread out over so many threads and with the https://search.twtxt.net UI displaying threads in a way that’s different than how https://twtxt.net does.

​ Read More
In-reply-to » So, uh, did anyone but me notice that the last character of a twt hash is always either an a or a q? Which is the natural consequence of taking the last digit in the base32 representation of a 256-bit hash -- 256 is not evenly divisible by 5 ! That final character is made up of one bit of actual information and 4 bits of padding.

I finally figured out that https://search.twtxt.net is not the same as https://twtxt.net/search. The former is open to the general public, unlike the latter which is only for registered users of twtxt.net. Meaning that I finally have some kind of access to an archive of the aforementioned debate.

​ Read More

So, uh, did anyone but me notice that the last character of a twt hash is always either an a or a q? Which is the natural consequence of taking the last digit in the base32 representation of a 256-bit hash – 256 is not evenly divisible by 5 ! That final character is made up of one bit of actual information and 4 bits of padding.

​ Read More
In-reply-to » @asquare (I wonder if that will ever show up without me mentioning you. 😅)

Probably going to stick to my original plan, which is to implement everything I need by hand. Becaus to me part of the appeal of twtxt is that it’s simple enough for it to be feasible to roll your own implementation.

​ Read More
In-reply-to » @asquare (I wonder if that will ever show up without me mentioning you. 😅)

I’m not using anything that you would recognize as a full-featured client. I upload twts with hut publish, “publicise my user agent” with manual curl invocations (when I remember to) (thanks to @movq@www.uninformativ.de for the informative guide https://www.uninformativ.de/twtxt-mention.html), and as for following other people’s feeds, I still haven’t decided how I’m going to do that.

​ Read More

It really bugs me when a Web site for a tool has a link called “How It Works”, but the actual information behind that link is “how to use”. A set of operating instructions for a tool and an explanation of the principles that enable the tool to function are two very different things.

​ Read More
In-reply-to » There’s a lot more activity in Geminispace than I realized: gemini://warmedal.se/~antenna/

@prologic@twtxt.net Actually, my twts from the last two days aren’t showing up on , so I guess that no-one is following me and the reason my earlier twts did show up is that yarnd does a one-off fetch of any feed @-mentioned by a pod member. Comments in the code suggest that this is the case, see internal/server.go, commit 7dcec70e, line 468. As the author of that code, can you confirm/deny?

​ Read More
In-reply-to » New post (mostly follow-up on the previous with a few new points) on the twtxt v2 discussion. http://a.9srv.net/b/2024-10-08

@2024-10-08T19:36:38-07:00@a.9srv.net Thanks for the followup. I agrees with most of it - especially:

Please nobody suggest sticking the content type in more metadata. 🙄

Yes, URL can be considered ugly, but they work and are understandable by both humans and machines. And its trivial for any client to hide the URLs used as reference in replies/treading.

Webfinger can be an add-on to help lookup people, and it can be made independent of the nick by just serving the same json regardless of the nick as people do with static sites and a as I implemented it on darch.dk. Try RANDOMSTRING@darch.dk on http://darch.dk/wf-lookup.php (source code) or RANDOMSTRING@garrido.io on https://webfinger.net

​ Read More

if twtxt 2 is dropping gemini support, i will probably move on and spend more time on my gemini social zine protocol instead. i think the direction of the protocol is probably fine, but for me web is a tier 2 publishing channel. if the choice is between gemini and http i’m always going to pick gemini. its been a fun ride, but i guess this is where i get off.

​ Read More

Hurricane Helene is passing by. Close enough to give us a day off tomorrow, but not that close to cause major harm. Well, we think. Hurricanes often have a mind of their own, and decide changes on their path. Either way, I shall be back at work on Friday đŸ˜©. LOL.

​ Read More

I’m not writing on ‘twtxt’ as much as I did in 2021-2022. While it has many advantages, I couldn’t get my close circle to join.

As part of my focus on digital minimalism, I aim to only use services that bring joy, value, and spark interesting conversations within the community.
That’s why I’m considering suspending my twtxt, switching to microblog on other platforms.

If anything of what I’ve written is interesting for you, or want to chat, you can find me on various platforms here:
https://text.eapl.mx/microblogging

​ Read More

@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.

​ Read More

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!

​ Read More

afaik nobody has done this, but i really need some numbers that can indicate the relative performance of various git servers (cgit, gitea, gitlab) on comparable hardware. cgit claims to be hyperfast, but what does that mean in practice?

​ Read More