@bender@twtxt.net This is true 🤣 I’d you don’t specify one; one will be auto-generated 🤣

The text parameters are percent-decoded before matching. Dash (-), ampersand (&), and comma (,) characters in text parameters are percent-encoded to avoid being interpreted as part of the text directive syntax.

@doesnm@doesnm.p.psf.lt “in TWTXT.net, avatars are set for you!” 😂

The specific syntax must (should) be followed as well: https://wicg.github.io/scroll-to-text-fragment/#syntax

Pretty bland without an avatar though 😢

@doesnm@doesnm.p.psf.lt I never really thought about that to be honest 🤔

What if i want to delete avatar? Im deleted avatar meta field but still see avatar on twtxt.net

@doesnm@doesnm.p.psf.lt I did yes 👌

Seems he want “get permanarely unfollowed and ignored”. Btw did you unfollow him? I see follow in your feed

Done

@Codebuzz@www.codebuzz.nl yarnd actually uses WebSub between pods for this reason:

@Codebuzz@www.codebuzz.nl Yes! welcome yo the community 🙇‍♂️

@bender@twtxt.net Maybe so but likely only recently formalized right?

@bender@twtxt.net Same. I will also blacklist the domain shortly.

@Codebuzz@www.codebuzz.nl Welcome to Twtxt 🤗

Ya know; Rather than being an asshole and getting all angry, just be reasonable and reach out to the community or folks fetching (or trying) your feed.

Most clients respect caching if your feed is transported I’ve HTTP.

Otherwise you can add the # refresh hint to clients on your feed.

No need to be an obnoxious ass and flood your own feed. That will just get you permanarely unfollowed and ignored.

@sorenpeter@darch.dk your mentions are broken too. His shows fine:

# nick   = movq
# url    = https://www.uninformativ.de/twtxt.txt
# avatar = https://www.uninformativ.de/avatar.png#20240102
#
# [...]
#
# Legacy, don't use:
# nick_alias = vain
#
# prev = 6v47cua twtxt-old_2024-04-21_6v47cua.txt

What’s on the [...] is just a comment he added. Here is mine:

# nick        = bender
# url         = https://twtxt.net/user/bender/twtxt.txt
# avatar      = https://twtxt.net/user/bender/avatar#zccci5jyuxv266gelyggvufoacqp3elvhyv2k3t7sfl6hlggtkza
# description = "Yeah, well, I'm gonna go build my own theme park. With blackjack and hookers! In fact, forget the park."

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?

I think it could be yarnd’s avatar caching. That’s why my avatar field has a #20240102 at the end: To trick yarnd into reloading it.

Because the formatting of your twtxt.txt file “headers” is wrong. Everything in your twtxt.txt in here:

#        nick = sorenpeter
# description = visualist and livecoder
#         url = http://darch.dk/twtxt.txt
#      avatar = http://darch.dk/avatar.png
#     profile = http://darch.dk/timeline
#  webmention = http://darch.dk/timeline/webmention
#        prev = archive twtxt-archive.txt

I think it is being ignored. It should be:

# nick = sorenpeter
# description = visualist and livecoder
# url = http://darch.dk/twtxt.txt
# avatar = http://darch.dk/avatar.png
# profile = http://darch.dk/timeline
# webmention = http://darch.dk/timeline/webmention
# prev = archive twtxt-archive.txt

My first PC as a kid had an amber monitor, so this feels right at home:

https://www.youtube.com/watch?v=PeuH0YmWkI4

💛

@prologic@twtxt.net Why does twtxt.net still show my old avatar?

@Codebuzz@www.codebuzz.nl Welcome to the twt’verse 👋

@doesnm@doesnm.p.psf.lt finally someone read my blogpost ;)

@aelaraji@aelaraji.com Thank you, and yes I got more on my websites https://darch.dk/vj/ and https://algorave.dk/videos/

@prologic@twtxt.net it has been around for much longer (worked on Chrome, just recently does on Safari).

@anth@a.9srv.net that doesn’t work because you need encode that URL, like so http://a.9srv.net/tw.txt#:~:text=2024%2D10%2D08-,2024%2D10%2D23T18%3A59%3A49%2D07%3A00

I have muted the user. Everything is back to its peaceful “normality”. LOL.

@doesnm@doesnm.p.psf.lt someone started to follow a “dead” feed. And the feed’s owner is fed up with people following their dead feed, and they have come up with an “innovative” way to fight it.

@prologic huh? looks like someone flooding twtxt

According to this it was only published as a specification/standard last year. It’s no wonder 💭

@anth@a.9srv.net I admit I didn’t know about text fragments. How new is this? 🤔

Hm, seems i breaking something in twet code for handling mentions

@sorenpeter ’s webmentions uses this trick: http://darch.dk/mentions-twtxt

@aelaraji@aelaraji.com As long as you’re having fun, you’re doing the right thing. 😅 (Kind of. 😂)

@lyse@lyse.isobeef.org Now I feel like an ant. 🐜 (Imagine how ants must feel when they see this! 🤯)

@bender@twtxt.net Consider me stumped! 😅 Yeah, I can imagine this not being super fast. 🥴

@movq@www.uninformativ.de allow me to stump you! Our Oracle team runs scripts, java, and a few others from NFS shares. That has become a true problem when VMs have moved to Azure, and NFS servers remain on premises. NFS doesn’t like latency, especially when laced with high I/O activity.

@prologic@twtxt.net right, but “regular” forks have parents. An edited twt—currently—has none. Edits just create a new branch-less leaf.

I guess crashing the program with a SIGBUS is intentional. Here’s a blog post that describes this exact thing when running binaries off of NFS:

https://rachelbythebay.com/w/2018/03/15/core/

It’s just that this also happens locally nowadays and, thus, much easier and more often (I bet few people run programs via NFS these days). 🫤

Not a fan of this. (Time will tell if I have the energy to discuss this on the Linux kernel mailing list.)

@movq@www.uninformativ.de In our case at work the new behavior can indeed be considered an improvement. systemd would then restart the new version automatically if the old one crashed. Still, crashing in the first place is very uncool. We don’t have a recent enough kernel version, though.

@slashdot@feeds.twtxt.net wut da fuq?! What happened? What da hell was the Australian federal police even doing or asking? da fuq? I didn’t even know Session was based in Australia?! 🇦🇺 Oh my 😱 – I think this is worth enough to raise this with my local Federal MP (Elizabeth Watson Brown). This is nuts. The Australia FP can get bent 🤦‍♂️ I’d like to learn more about wtf happened here, seriously this is unacceptable and an overreach at first glance.

@lyse@lyse.isobeef.org Oh man that was very sexy indeed 🤣 The detail! Oh my 😮

Heck yeah, this is some amazing space porn from ESA! https://dlmultimedia.esa.int/download/public/videos/2024/10/023/orig-2410_023_AR_EN.mp4

@asquare@asquare.srht.site No need to apologise 😅 All very good points 👌

@asquare@asquare.srht.site This is absolutely true! 💯 However the natural behavior of editing a post is the same as forking. So from a community perspective, we’re actaully okay with how that works in reality. I think we’re all getting a bit too hung up on “exactness”. One of the things I think we’re finding hard to reconcile is the fine line between a decentralised ecosystem and distributed system.

I want it very much to remain decentralised. That means Content-based addressing makes sense, because you can have integrity about what a Twt Hash means. I don’t really mind if a thread gets forked because the OP was edited, that’s actually how forking works anyway 😅

In any case, yes Content addressing can break threads when the original content is edited that’s for sure, however we’ve since agreed and realized that technically speaking, we can actually identify from a clients perspective, whether an edit took place.

@asquare@asquare.srht.site Iant yhay what I said? Or did I fat-finger my reply 🤣

@asquare@asquare.srht.site Yeah my UI skillz aren’t so great sorry 🤣

@asquare@asquare.srht.site correct 👌