@kat@yarn.girlonthemoon.xyz We missed you too 🤗

You’re all wrong 😑 @anth@a.9srv.net will happily tell you (hopefully) that we’ve been doing this whole “microblogging” / “status update” thing decades earlier than anything you’ve ever seen in the form of finger 🤣 and “plan” files 😅

@kat@yarn.girlonthemoon.xyz Yeah okay, I’ll see if I can reproduce this silly nonsense version string 🤣 cheers! 🍻

@andros@twtxt.andros.dev Yeah I think @xuu@txt.sour.is has built some interesting stuff around this? 🤔

@andros@twtxt.andros.dev I’m not entirely sure what this means:

development that requires a database

Obviously I wasn’t in the discussion so I feel like I’m missing some context here 🤔

@doesnm@doesnm.p.psf.lt Actually that’s a fantastic idea 🙌

@eapl.me@eapl.me@eapl.me@eapl.me 🤗😍

@eapl.me@eapl.me@eapl.me@eapl.me No worries 🤗 My emotionally state are my own to sort out 🤣

@kat@yarn.girlonthemoon.xyz Welcome back! 🙌

@kat@yarn.girlonthemoon.xyz Actually that’s’ a known bug I haven’t worked out yet hmmm 🧐

@kat@yarn.girlonthemoon.xyz Arw you running make build or go build?

@lyse@lyse.isobeef.org I also think we need to remove ourselves a bit from the “Twtxt” format as it was originally designed by Buckket.

The beauty of twtxt is, you put one file on your server, done. One.

I’m not talking (nor ever was here) about that. We should be allowed to and encourage dot evolve its usage and our own.

It would be far better as a community to focus on the utility of our tools, services, protocols, formats and specifications as well as our own clients and usages thereof rather than this “idealised” design from © 2016.

If you strongly disagree with this, then I think I’ll just honestly step away from all of this as the back ‘n forth on this whole “beaty” and “simplify” argument is honestly wearing me down 😢

@lyse@lyse.isobeef.org Sorry I didn’t mean to upset you or anyone here in the community. I am/was merely trying to solve what I perceive to be a problem and an ask in the community:

How do I know what a hash refers to?

I believe the reason for this stems from a curiosity of the user of whether they might find that thread interesting or whether there are new interested feeds to follow?

Although my idea increases complexity slightly (introducing a new concept) I don’t think it’s particular hard to understand, reason about or implement (complicated). One could even even make the implementation quite simple in fact.

Either way, the idea of a service (cantralised) or participating clients/registries (distributed) providing reverse hash lookups doesn’t sound too bad really.

What do you propose to solve the above problem? 🤔

One of the biggest gripes of the community with the way the threading model currently works with Twtxt v1.2 (https://twtxt.dev) is this notion of:

What is this hash?
What does it refer to?

Idea: Why can’t we all agree to implement a simple URI scheme where we host our Twtxt feeds?

That is, if you host your feed at https://example.com/twtxt.txt – Why can’t or could you not also host various JSON files (let’s agree on the spec of course) at https://example.com/twt/<hash> ? 🤔

That way we solve this problem in a truly decentralised way, rather than every relying on yarnd pods alone.

@unexplained_mysteries@feeds.twtxt.net Interesting article on the philosophy of thougjts 🙌

Power outages throughout south east queensland (map)

We’ve now had centimeters of rainfall in the last 24hrs 😱 – Yesterday afternoon the local creek near us had already gone several inches over the footbridge too! 😱😱

@emmanuel@wald.ovh That’s not good mate 😢 Hope you’re feeling better? 🤗

So… Cylone Alfred made landfall (whatever that means) last night, and I watched it hit my wife’s Uncle/Aunt’s place on one of the outer islands, then move westwards and sort of fizzle out. It’s now been downgrade to a “Tropical Low” (I guess not good enough for a Cat X anymore?), but we’re still in the Eye of it, and there’s still a swirling mass of winds (just not as fast). Now we get to look forward to flooding 🤣

@andros@twtxt.andros.dev I think you’ve done an amazing job of this client 🙌

Update:

Another view!

This is what I’ll be facing into in the next few hours and over the next couple of days! Cyclone Alfred 🌀

@lyse@lyse.isobeef.org Same I think it’s not worth it either

@xuu@txt.sour.is Awww thanks bro 😎

@movq@www.uninformativ.de I know right? 🤣 Fuck this geoip blocking censored shit™ 💩

@movq@www.uninformativ.de Hmm

Video unavailable

🥲🥲

@eapl.me@eapl.me@eapl.me@eapl.me That should be fine 🤞

This seems to be capable of supporting edits as you noted. But I need to think a bit more (~2am here now) of whether this can be abused in any way… The advantage of Content-based Addressing (hashing the content) is that the hash is then immutable, meaning that we can have integrity that the hash actually represents that content from that author at that time.

@eapl.me@eapl.me@eapl.me@eapl.me I kind of like the idea of 96473B4F_1 – That is SHA256SUM(feed_url)_<monotomic_feed_post_id>

Example feed I guess? ☝️

# default_lang = en
# discovery_url = https://example.com/discovery/
# follow = alice https://example.com/alice.txt ABCDEF12
# follow = alice gemini://example.com/alice.txt
# avatar = https://example.com/avatar/alice.png
# avatar = gemini://example.com/avatar/alice.png

1	2025-03-03T15:00:00-04:00	{lang=en} Hello, world! Welcome to my twtxt feed. UTF-8 check: é, ö, ü.
2	2025-03-03T15:05:00-04:00	{lang=es} ¡Hola, mundo! This tweet is in Spanish.
3	2025-03-03T15:10:00-04:00	{url=ABCDEF12,id=1} Replying to tweet 1 using its URL hash.
4	2025-03-03T15:15:00-04:00	{edited=1} This tweet has been edited once.
5	2025-03-03T15:20:00-04:00	{lang=fr} Bonjour le monde! A French twt overriding the default language.
6	2025-03-03T15:25:00-04:00	Regular twt without metadata defaults to en.

@eapl.me@eapl.me Some really good idea in this post of yours 👌👌

@xuu@txt.sour.is Oh 🤔

@andros@twtxt.andros.dev Reading… 👀

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

@xuu@txt.sour.is Is this why threads are getting a bit messed up lately? 🧐

@xuu@txt.sour.is redirects to https://text.eapl.mx/main-en for me?

@xuu@txt.sour.is Um sorry?! A “smart” toilet?! 🤦‍♂️

@eapl.me@eapl.me@eapl.me@eapl.me This sounds great! 🙌 Will you coordinate this activity? 🙏

@xuu@txt.sour.is What do you mean by this? 🧐 If we implement and other clients don’t, Then we end up forking the community no? 🤔

@lyse@lyse.isobeef.org Pros/Cons. I’m not so Vince’s that switching to location based addressing will be better.

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

@movq@www.uninformativ.de I agree, extremism either way, and bad temper’s never amount of anything good 😢