La #audiopoesia de mi poesía escrita mientras hacía la compra en el LIDEL aquí. https://mastodon.green/@fanta/115310503903271565
Es un audio en el toot. La voz de @CorioPsicologia
Traducción al inglés de @Karramarro ⌘ Read more****
# I am the Watcher. I am your guide through this vast new twtiverse. # # Usage: # https://watcher.sour.is/api/plain/users View list of users and latest twt date. # https://watcher.sour.is/api/plain/twt View all twts. # https://watcher.sour.is/api/plain/mentions?uri=:uri View all mentions for uri. # https://watcher.sour.is/api/plain/conv/:hash View all twts for a conversation subject. # # Options: # uri Filter to show a specific users twts. # offset Start index for quey. # limit Count of items to return (going back in time). # # twt range = 1 195904 # self = https://watcher.sour.is?offset=195419 # next = https://watcher.sour.is?offset=195519 # prev = https://watcher.sour.is?offset=195319
banner
would) for clients having no knowledge of it.
display_name
will be redundant, and add to the "busy" factor. That is, the opposite of simplicity.
display_name
is worthwhile, since nick
is functionally a display name
display_name
: To show a human readable alternative for a nick, it fallback to nick
if not definedbanner
: Using the same format as avatar
but the image expected is wider, inspired by other socials around#<https://example.com/tw.txt#yyyy-mm-ddThh:mm:ssZ>
is foolproof)
@<...>
being mentions
(#abcdefghijkl https://example.com/tw.txt#:~:text=2025-10-01T10:28:00Z)
, because it can be simply hacked in to clients currently on hashv1 and provides an off-ramp to location-based addressing2025-10-01T10:28:00Z
? That’s not necessarily correct. And, to be proper URLs that Firefox and Chromium understand, it would also need to be written as 2025%2D10%2D01T10:28:00Z
. The dash carries meaning, sadly. I think all this just creates needless complication. How about we just go with https://example.com/tw.txt#2025-10-01T10:28:00Z
?)
18:16 <aelaraji> quark 🙏 much appreciated but it won't be necessary, since there isn't much to miss out on in most of where I hang out, so I could just disconnect and spare everyone else the noise
18:17 *** aelaraji (aelaraji@776014f5a3edd32f1ed19658b7b85c8c655945b0feacaedd92fe60e61a3c0ae2) has quit (/ME goes "yeeeeet..!")
18:18 <quark> No noise for me.
18:18 <quark> It’s all good.
18:18 <quark> What would IRC be without on/offs?
18:19 <quark> Preeeety boring!
18:19 <quark> Ah, he was gone.
18:19 <quark> Well, I will twtxt this to him. LOL.
url
field it finds. If there is none, it uses the URL that I’m using for fetching the feed.url
field, but then what? You will still show up as zvava
in my client or, if you also change your nick
field, as movq (zvava)
.
url
to be used for hashing. No matter if it points to a different feed or whatever. Just unsubscribe from malicious feeds and you're done.url
is used for hashing, it must never change. Otherwise, it will break threading, as you already noticed. If your feed moves and you wanna keep the old messages in the same new feed, you still have to point to the old url
location and keep that forever. But you can add more url
s. As I said several times in the past, in hindsight, using the first url
was a big mistake. It would have been much better, if the last encountered url
were used for hashing onwards. This way, feed moves would be relatively straightforward. However, that ship has sailed. Luckily, feeds typically don't relocate.
(#abcdefghijkl https://example.com/tw.txt#:~:text=2025-10-01T10:28:00Z)
, because it can be simply hacked in to clients currently on hashv1 and provides an off-ramp to location-based addressing (though i still think the format should be changed to smth like #<abc... http://example.com/...>
so it's cleaner once we finally drop hashes)
url
(with the url as a fallback), the key could even be a public key so it can be used verifieable in crypto functions[#THREAD_ID] Hello world
and replies with (#REPLY_ID) Ahoy
) so the content can change without affecting the thread reference, and anyone can use their own schemes freely
cors-anywhere
via docker in a minute and it would work the same.