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
In-reply-to » Anyone had any intereractions with @cuaxolotl yet? Or are they using a client that doesn't know how to detect clients following them properly? Hmmm 🧐

@prologic@twtxt.net @movq@www.uninformativ.de my setup is pretty old-school tw.txt hosting-wise. just a text file and a very simple static bridge for pikkulog-style subscribers on gemini. i do try to keep up on the twtxt format spec so i’m publishing a modern and well-formed feed. my dual-hosted website/gemcapsule is meant to eventually be entirely bespoke (my friend wrote the gemini server i’m using, so that counts enough for now) and i’d like to eventually support some of the server extensions that yarn has piloted. follow-wise, rn i kinda just manually try to pick up on who is following me by browsing random feeds. my custom clients usually do a FoaF crawl, but i don’t have anything that really works running rn.

⤋ Read More
In-reply-to » Apple Stands By Decision To Terminate Account Belonging To WWDC Student Winner TechCrunch's Sarah Perez reports: Apple is standing by its decision to terminate the Apple Developer Account of Appstun, a mobile app company created by one of Apple's own Worldwide Developer Conference 2021 student winners. According to an announcement published on Appstun's website, Apple moved to terminate the devel ... ⌘ Read more

@slashdot@feeds.twtxt.net At least Android has fDroid. Apple is a dominatrix.

⤋ Read More

The next jenny release will (probably) stop supporting the old ā€œHash Tag Extensionā€, which was deprecated at the end of 2022. It was once used for threading and looked like this:

<a href="https://twtxt.net/search?tag=tsvhqdq">#tsvhqdq</a>

I don’t see them being used in the wild anymore. But if you happen to fetch really old feeds (or some archived feeds), things might break a little.

⤋ Read More