@gallowsgryph@prismdragon.net do you mind updating the fragment part of your avatar url? 🙏

@movq@www.uninformativ.de Don’t we use the last url for hashing? 🤔

@movq@www.uninformativ.de you are absolutely right! And it did happen once more in the past as well. The difficulty about this particular new behavior though is that I’ve also had to blacklist it and remove it from the search engine and crawler for obvious reasons.

@prologic@twtxt.net I don’t understand that behavior either, but I’m afraid stuff like that is always going to happen. (I think it already happened once in the past?) As long as we have an easy way to ignore such a feed and remove it from our databases, we should be fine. 🤔

@sorenpeter@darch.dk As a replacement, it should be doable. But it won’t work together with hashes. So the community has to agree on one or the other first.

@prologic@twtxt.net I’m not sure this isn’t a bug. The feed’s URL must have changed at some point but Yarn is still using the old URL for hashing. And it’s inconsistent now:

curl -s -H 'Accept: application/json' https://twtxt.net/twt/mowsvgq

This gets you a twt which, when hashed again now using all the information from that API reply, does not yield the hash mowsvgq but bjs6aua.

But when you use the URL http://prismdragon.net/twtxt.txt for hashing instead of http://twtxt.prismdragon.net/twtxt.txt, it’s mowsvgq.

So I would expect Yarn to either know about mowsvgq (showing the new URL http://prismdragon.net/twtxt.txt) or about bjs6aua (showing the old URL http://twtxt.prismdragon.net/twtxt.txt). But not mowsvgq with the old URL. 😅

I don’t see how the second # url = metadata field is relevant here. 🤔

@gallowsgryph@twtxt.prismdragon.net Cool! 👌

My very strong opinion on the use of Twtxt is if you intend to use it, you should be prepared to let people pull your feed or at least check it and regular rentals.

Otherwise get out and go use something that’s either a distributed (Mastodon, AT, etc) or centralized (Facebook, X, etc) network.

I just find a very frustrating when you have these very small number of people that lash out unnecessarily and get so angry over nothing.

@cuaxolotl@sunshinegardens.org I think we’ve done that here right? 🤔 we seem to have collectively formed a community of folks that are interested in interacting with one another in a completely decentralized way and minimal way.

@bender@twtxt.net Agreed. I just find it an abhorrent that certain folks just don’t even bother to spend the few mins that it takes to reach out. Compares to hours of their time to cause havoc and mischief. Seriously wut da fuq?! 🤦‍♂️

@bender@twtxt.net Haha if she let you 🤣

@prologic@twtxt.net I might join from mum’s house. That’s, if she let me. 😅😅😅

@prologic@twtxt.net don’t let anyone bum you out, mate. We take corrective action, and move on.

I mean, you will quit twtxt when you please, but not because of some irrelevant feed. Won’t you agree?

After the behaviour of a clearly very angry feed author over the past few days, I’m very tempted to give up on Twtxt and allow it to go back to being dead. What really is the point of building and supporting a way to exchange little pieces of text with one another in a completely decentralized way, if you’re just going to keep bumping up against such hostility? I don’t know why I do this anymore.

@sorenpeter@darch.dk@darch.dk Cool! 😎

I’m planning to be there tomorrow (message from yesterday, since we can not all live in the future;)

Who’s coming to the online meetup today? 🤔

The real crux of the matter is this whole moving feeds around to different uri(s). This makes things hard. I think it’s worth revisiting @anth@a.9srv.net ’s UUID idea for its merits.

@movq@www.uninformativ.de I’m assuming jenny is doing some kind of validation and verifying if that Twt really does exist on the feed uri? 🤔 But the hash is all kinds of wrong now because @gallowsgryph for whatever reason decided it might be a good idea to have a 2nd # url that doesn’t actually point to the same Twtxt feed (bad idea).

@bender@twtxt.net @movq@www.uninformativ.de AFAICT this isn’t a bug with yarnd, but a. bug with the feed itself. The feed is now completely broken in that regard. See #27nifeq

@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 🤔

@bender@twtxt.net I’m not sure I get it 🤣

@prologic@twtxt.net looks like. See @movq@www.uninformativ.de’s explanation.

@prologic@twtxt.net it is hard to explain. I replied to OP, mention didn’t work. Then replied again, to start mention didn’t work. Then @movq@www.uninformativ.de replied. Then I replied, but my replied to OP was overwritten by my last reply, no idea how. This (https://twtxt.net/twt/zyo3buq) was my reply to this (https://twtxt.net/twt/rzuepoq).

What’s going on?

Is there a bug on my side?

@bender@twtxt.net Who did that? 🤔🤣

@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.

@bender@twtxt.net That broken mention might have the same cause as the other issue you mentioned. Changed URL and all that. 🤔

@bender@twtxt.net Well, I can’t help it. I just saw the parse error popping up. ¯_(ツ)_/¯

Oh, and the lang metadata field is indented with tabs, breaking the nice visual alignment.

There might be a bug in jenny that causes it to re-fetch archived feeds on every run. Probably happens on edits/deletes. I’ll look into it soon-ish.

@lyse@lyse.isobeef.org that’s Lyse, doing god’s work! :-P

@sorenpeter@darch.dk I like that. It pretty much matches what I already had in mind. (The implications of part two of point 0 are obviously controversial and I don’t know if we can ever agree on that. 😅)

@quark@ferengi.one Oh dear. 😅 I’m one of the first around here, though. 🤪

@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.

Hey @Codebuzz@www.codebuzz.nl, looks like your second twt has a broken timestamp. :-)

Time to put up the christmas decoration, I guess. 🤷✨

@quark@ferengi.one At some point, Yarn must have fetched the feed and used the correct URL (otherwise it wouldn’t have gotten the correct hash). And at that point, it should have updated the uri field for this twt in its database, I guess? Disclaimer: I know nothing about the internals of Yarn. 😅

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

@quark@ferengi.one That’s confusion on Yarn’s part, I’d say.

Yarn’s API says that twt comes from the URL http://twtxt.prismdragon.net/twtxt.txt – but when using that URL for hashing, I get the hash bjs6aua instead of mowsvgq. That’s not the correct hash, so jenny says the twt could not be found.

Inspecting the feed using jenny -D … yields the correct hash. When looking at the raw feed, we can see:

# nick = gallowsgryph
# description = Green living and permaculture enthusiast, writer, otherkin, weird.
# url = http://prismdragon.net/twtxt.txt
# url = https://dreamwidth.org/gallowsgryph/
# avatar = http://prismdragon.net/img/gallows.png#20241025

So it’s a different URL. When I use http://prismdragon.net/twtxt.txt for hashing, I get the correct hash.

I find it ironically amusing when people leaves twtxt, which anyone can, or could, read (no needs for sign ups, etc.), and move to Twitter. 🤦🏻‍♂️

@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?

Well, that mention didn’t work. Yarn has been very unreliable on that front (amongst others). Hmm.

@movq@www.uninformativ.de I see. If I edit it, is shows as @gallowsgryph@twtxt.prismdragon.net.

WOAH! What happened here? I replied to https://twtxt.net/twt/rzuepoq, just now, and this twtxt shows “2h ago”.

@doesnm@doesnm.p.psf.lt like OP, that will not work, as it has wrong/incomplete information.

@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!” 😂