I think it uses the first # url
too. See here and here – @xuu Can you confirm this to be the case? 🙏 GetN("url", 0)
will return the first found # url
comment right?
@doesnm@doesnm.p.psf.lt No I’m just frustrated 🤗
@movq@www.uninformativ.de I will check when I get home 😅
@gallowsgryph@prismdragon.net Very nice 👌
@movq@www.uninformativ.de Only because I build and maintain additional services right? 🤔
@gallowsgryph@prismdragon.net That’s mixh better 🥳
@gallowsgryph@prismdragon.net Thays mixh better 🥳
@movq@www.uninformativ.de Hmmm now I’m confused 😅 I’ve made no changes anywhere – we still need to all agree, especially client authors and maintainers 🤣
@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.
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 🤣
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! 😎
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 🤣
What’s going on?
Is there a bug on my side?
@bender@twtxt.net Who did that? 🤔🤣
@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.
avatar
field has a #20240102
at the end: To trick yarnd into reloading it.
Pretty bland without an avatar though 😢
avatar
field has a #20240102
at the end: To trick yarnd into reloading it.
@doesnm@doesnm.p.psf.lt I never really thought about that to be honest 🤔
@doesnm@doesnm.p.psf.lt I did yes 👌
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.
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? 🤔
@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 😮
a
or a q
? Which is the natural consequence of taking the last digit in the base32 representation of a 256-bit hash -- 256 is not evenly divisible by 5 ! That final character is made up of one bit of actual information and 4 bits of padding.
@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 😅
a
or a q
? Which is the natural consequence of taking the last digit in the base32 representation of a 256-bit hash -- 256 is not evenly divisible by 5 ! That final character is made up of one bit of actual information and 4 bits of padding.
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.
a
or a q
? Which is the natural consequence of taking the last digit in the base32 representation of a 256-bit hash -- 256 is not evenly divisible by 5 ! That final character is made up of one bit of actual information and 4 bits of padding.
@asquare@asquare.srht.site Iant yhay what I said? Or did I fat-finger my reply 🤣