(#mowsvgq) @gallowsgryph Your feed is a bit off. I don’t think it makes sense to have a 2nd # url field that doesn’t point to the same Twtxt f …
@gallowsgryph @twtxt.prismdragon.net Your feed is a bit off. I don’t think it makes sense to have a 2nd # url field that doesn’t point to the same Twtxt feed 🤔 ⌘ Read more

(#mowsvgq) @bender@bender I’m not sure I get it 🤣
@bender I’m not sure I get it 🤣 ⌘ Read more

(#mowsvgq) What’s going on?
What’s going on? ⌘ Read more

(#rjapt4a) Is there a bug on my side?
Is there a bug on my side? ⌘ Read more

(#64gdl7q) @bender@bender Who did that? 🤔🤣
@bender Who did that? 🤔🤣 ⌘ Read more

@movq@www.uninformativ.de How hard would it be to implement something like (#<2024-10-25T17:15:50Z https://www.uninformativ.de/twtxt.txt>)in jenny as a replacement for (#twthash) and have it not care about if is http(s) or a g-protocol?

@Codebuzz@www.codebuzz.nl Speed is an issue for the client software, not the format itself, but yes I agree that it makes the most sense to append post to the end of the file. I’m referring to the definition that it’s the first url = in the file that is the one that has to be used for the twthash computation, which is a too arbitrary way of defining something that breaks treading time and time again. And this is the case for not using url+date+message = twthash.

@movq@www.uninformativ.de LOL, you are late! :-P Stores around started selling Christmas’s decorations early September. Like, wow! Usually the earliest is after Halloween, more often after Thanksgiving.

@movq@www.uninformativ.de interesting! So, what would the fix be, in this case, do you know? Aware of this, @prologic@twtxt.net?

@movq@www.uninformativ.de, having an issue fetching a twtxt context. I am getting:

Trying to fetch "#mowsvgq" from Yarn pod https://txt.sour.is ...
Trying to fetch "#mowsvgq" from Yarn pod https://twtxt.net ...
Twt could not be found

Yet, the twtxt is there: https://twtxt.net/twt/mowsvgq. Bug, or something else?

(#qaaeicq) @bender@bender This is true 🤣 I’d you don’t specify one; one will be auto-generated 🤣
@bender This is true 🤣 I’d you don’t specify one; one will be auto-generated 🤣 ⌘ Read more

(#uuuctoa) > The text parameters are percent-decoded before matching. Dash (-), ampersand (&), and comma (,) characters in text parameters are p …

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. ⌘ Read more

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

🥳 NEW FEED: @Codebuzz@www.codebuzz.nl

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?

@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 huh? looks like someone flooding twtxt

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

Huh. I had long forgotten about text fragment URLs. Seems relevant for linking to discussions around linking to individual twtxt posts. https://alfy.blog/2024/10/19/linking-directly-to-web-page-content.html

@Phys_org@feeds.twtxt.net …which will be entirely ignored when the 💩 hits the 🪭

“Interest grows in geoengineering” because pursuing the obvious, clearest, most direct solution–reducing fossil fuel use–is for some reason off the table. That is already an unethical arrangement. Pasting an ethical framework on top doesn’t change the rotten situation at its core.

@New_scientist@feeds.twtxt.net Pusher can detect own product. Film at 11.

@movq@www.uninformativ.de I didn’t realize elves were considered malicious either.

@prologic@twtxt.net Nice. My muscle memory defaults to visual block mode then insert across rows for this circumstance. It’s funny how you do things so often without thinking about a different way of doing it.

@bender@twtxt.net so much rain. a lot of us thought we were non-flooding (or non-evac and zone x) but still had water come in the houses in pinellas. been an interesting past month!

@aelaraji@aelaraji.com one i use quite frequently is when i have a list of items (1 per line) and want them sorted but only keep those which are unique: ggV}:sort u

🥳 NEW FEED: @asquare@asquare.srht.site

@2024-10-09T08:11:00Z@twtxt.net It an easy way of twt-adressing by using the timestamp instead of a nick, which is arbitrary anyhow. Just my suggestion for a new reply-model ;)

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

Setting up my twtxt site again

@prologic@twtxt.net currently? it wouldnt :D.

we would need to come up with a way of registering with multiple brokers that can i guess forward to a reader broker. something that will retry if needed. need to read into how simplex handles multi brokers

@bender@twtxt.net 🤣

@doesnm@doesnm.p.psf.lt Agree. salty.im should allow the user to post multiple brokers on their webfinger so the client can find a working path.

@movq@www.uninformativ.de i’m sorry if I sound too contrarian. I’m not a fan of using an obscure hash as well. The problem is that of future and backward compatibility. If we change to sha256 or another we don’t just need to support sha256. But need to now support both sha256 AND blake2b. Or we devide the community. Users of some clients will still use the old algorithm and get left behind.

Really we should all think hard about how changes will break things and if those breakages are acceptable.

@aelaraji@aelaraji.com Hmm that is worth trying. It is the same base Firefox I guess 🤔

@aelaraji@aelaraji.com Yep seems alright! Really fast too. I’m still using my main Firefox in general cos.. well it’s set up so much and it’s hardened, profile running in RAM, all that crazy stuff that got it working the way I want 😂

But keeping a good eye on Zen Browser’s progress.

@movq@www.uninformativ.de because sometimes resurrecting the dormant is worth it. Hello! :-)

@aelaraji@aelaraji.com LOL. I am everywhere! :-P

@prologic@twtxt.net I think printf is a more portable option than echo -e for interpreting \t as tab. E.g. printf ‘%s\t%s\t%s’ “$url” “$time” “$text”. In general I always prefer printf over echo for anything non-trivial in unix shell scripts. See last paragraph of https://en.wikipedia.org/wiki/Echo_(command)#History

@aelaraji@aelaraji.com easy as cake to get and
account here. Very reliable too!

Thanks @david@collantes.us, good to know, but we need to agree on what character we use, otherwise the hashes will not be the same:)

@aelaraji@aelaraji.com You could just remove the {getuser()} part because you added ~.

Ok, i know how to command working (not sure), but seems it only grab from cache. Maybe make fetch from twtxt.net if hash not found?

@prologic@twtxt.net Regarding the new way of generating twt-hashes, to me it makes more sense to use tabs as separator instead of spaces, since the you can just copy/past a line directly from a twtxt-file that already go a tab between timestamp and message. But tabs might be hard to “type” when you are in a terminal, since it will activate autocomplete…🤔

Another thing, it seems that you sugget we only use the domain in the hash-creation and not the full path to the twtxt.txt

$ echo -e "https://example.com 2024-09-29T13:30:00Z Hello World!" | sha256sum - | awk '{ print $1 }' | base64 | head -c 12

should i delete gemini support from twet? iirc in twtxt v2 it starts prohibited. And all of my fields are https

Hello @jdtron@jdtron.tilde.team

It has twts cache which used if timeline is set to jew. Maybe i.should fork twet to make wishes like newlines (i see two squares), showing conversations, showing twts if not found in cache and parsing medata to configure url, nick and followers (currenly it duplicated in config and twtxt file)

twet display twts in raw format with some formatting (sadly no newlines). And for reply messages i just seen (#hash). But which text hidden on hash? currenly im open twtxt.net/twt/hash to see this