tw.txt file wherever". The essence of micro-blogging, as opposed to full-scale blogging, is low friction and low stakes. Imposing a norm that you can't just use any ol' url, looking down on people with insufficently cool urls (as in "Cool URIs don't change" https://www.w3.org/Provider/Style/URI), puts up too much of a barrier to entry.
@asquare@asquare.srht.site What do you mean by “Cool URLs”?
# nick as a sort of "identifier". This gets us out of this mess of when feeds move locations or authors decide to host on 3 or 4 different protocols 🤣 Downside? Something picks the same nick? (they'll still hash differently, so that's fine).
Yup that’s right.
@Codebuzz@www.codebuzz.nl I really like this idea of just using the Feed’s # nick as a sort of “identifier”. This gets us out of this mess of when feeds move locations or authors decide to host on 3 or 4 different protocols 🤣 Downside? Something picks the same nick? (they’ll still hash differently, so that’s fine).
👋 PR to Update Metadata ext to clarify avatar field cc @lyse@lyse.isobeef.org @movq@www.uninformativ.de @sorenpeter@darch.dk and @Codebuzz@www.codebuzz.nl
@cuaxolotl@sunshinegardens.org not sure that really applies strictly in a purely decentakised system? 🤔
The call is on! Come join us!
@stigatle@yarn.stigatle.no Cominf yo yhe call? 🤔🤗
@xuu@txt.sour.is Thanks!
I think it uses the first # url too. See here and here – @xuu@txt.sour.is 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 🤣
@asquare@asquare.srht.site Yeah my UI skillz aren’t so great sorry 🤣
twtxt.net. Meaning that I finally have some kind of access to an archive of the aforementioned debate.
@asquare@asquare.srht.site correct 👌
text file busy. Example:
I guess the question now becomes;
Why does it cause the running process to crash?
text file busy. Example:
@movq@www.uninformativ.de Sounds like you’ll be submitting a bug report upstream though at some point when you have time? 🤔
text file busy. Example:
@movq@www.uninformativ.de Is this on a particular Kernel version? 🤔
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 We’ve collectively as a community (welcome to the community too! 🥳) had a many-week, multi-thread debate over this. It all boils down to Content Addressing vs. Location Addressing and the benefits, pros/cons of each approach. Ultimately though threads in Twtxt take advantage of a convention we formalized as the Twt Subject. This is combined with a Location-based Addressing, the Twt Hash extension. In the end we are likely to stay with this approach, but fix the parameters we use and truction.
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 Yeah we know 🤣 Still debating changes to the extension 😅
gg=G and to va", ci", di{... in vim the other day 😆 Life will never be the same, I can feel it. ref
@bmallred@staystrong.run I always get to imagine vim with its roots from vi and ed
@asquare@asquare.srht.site Hehw 🤣
@asquare@asquare.srht.site This is true! Even true of the extensions 👌
hut publish, "publicise my user agent" with manual curl invocations (when I remember to) (thanks to @movq for the informative guide https://www.uninformativ.de/twtxt-mention.html), and as for following other people's feeds, I still haven't decided how I'm going to do that.
@asquare@asquare.srht.site So basically very manual? 🤔
@movq@www.uninformativ.de Seems like a cool game 🤔 Hard to play on mobile though 🤣
gg=G and to va", ci", di{... in vim the other day 😆 Life will never be the same, I can feel it. ref
The V: pattern itself is quite good because you can do quite a lot of powerful things with selected text.
For example: ggV}:s/^/ -/ will insert a - at the beginning of every line turning your bunch of lines into a Markdown list of items 😅
@movq@www.uninformativ.de Same here 🤣 My fingers know everything, my brain does not 😅 Same with passwords too, at least the important ones, master password, passwords for my machine(s) and work laptop. Don’t ever try to interrogate me for them, only my fingers know 🤣
Offen Fair Web Analytics This looks pretty good., might give this a try. Been using GoatCounter, but it’s pretty bland in that it doesn’t really tell me much 😅
👋 Reminder folks of the upcoming Yarn.social monthly online meetup:
- Event: Yarn.social Online Meetup
- When: 26th October 2024 at 12:00PM UTC (midday)
- Where: Mills Meet : Yarn.social
@slashdot@feeds.twtxt.net seriously who the fuck is asking for this shit?
@slashdot@feeds.twtxt.net WHO does Tim Cook think he is anyway?! 🤦♂️
@aelaraji@aelaraji.com Noice 👌
gg=G and to va", ci", di{... in vim the other day 😆 Life will never be the same, I can feel it. ref
@aelaraji@aelaraji.com And pray tell/share with us what these magical commands do? 🤣
@lyse@lyse.isobeef.org What do you love about this gist?
@xuu@txt.sour.is Seems pretty cool 👌
@movq@www.uninformativ.de Just some rubbish trashy youtube videos on stupid crap I don’t believe in 🤣
@bender@twtxt.net No no, I’m quite sane 🤣
The world has gone mad.
@movq@www.uninformativ.de Yeah I noticed that earlier, and forgot 😅 That explains everything now 🤣
yarnd does a one-off fetch of any feed @-mentioned by a pod member. Comments in the code suggest that this is the case, see internal/server.go, commit 7dcec70e, line 468. As the author of that code, can you confirm/deny?
@asquare@asquare.srht.site And actually…
does a one-off fetch of any feed @-mentioned by a pod member
What is true here is if someone visits your “profile” on a pod whilst logged, it, yes yarnd fetches it in the background if it wasn’t already cached, as a “once off”. This is true.
@asquare@asquare.srht.site By the way… It might be nice to set yourself up with an Avatar 👌
yarnd does a one-off fetch of any feed @-mentioned by a pod member. Comments in the code suggest that this is the case, see internal/server.go, commit 7dcec70e, line 468. As the author of that code, can you confirm/deny?
@asquare@asquare.srht.site I see your reply now that I’m following you 🤣 The commit you’re ferring to btw is for WebMentions, which has little practical value IMO, it works but is rarely useful 😅
@asquare@asquare.srht.site Welcome to Twtxt 🤣 Discovery definately does work, but it also helps if you use a client that publicises your user-agent or you turn it on 🤣
@movq@www.uninformativ.de Ahh yes, that is probably the case 🤣 To be fair I don’t think too much about how things enter my cache, I just assume it’s either someone on my pod following them or whatever.
I didn’t follow at first because:
asquare may not follow you
Which probably means @asquare is probably using a client that doesn’t publicise its user agent or has it turned off? 🤔
@bender@twtxt.net Haha 😛
@bender@twtxt.net Fair enough 🤣 To be honest, I don’t really have an opinion either way, I think what he’s done is a bit “silly” of course, but I dunno. I’ve never. been invested in Wordpress as I said. I’d like to think I’d behave much better than Mat in a similar circumstance, but then again I’m not lucky? enough to be in that position (stink’n rich and wealthy), so who knows 😅
@bender@twtxt.net Did I say he was a “good guy”? 🤔 😅
@aelaraji@aelaraji.com So, what’s your salty addr? I tried to guess it by doing a lookup, but I guess I didn’t guess right 😅
@aelaraji@aelaraji.com Congrats 🥳
The WordPress ecosystem has lost its mind… - YouTube 👈 This is a pretty good summary of how fucked up the Wordpress ecosystem is now thanks to Mat 🤦♂️ (not that I’ve ever used Wordpress uggh 💩)
@lyse@lyse.isobeef.org Yeah I would never use something that is “Internet” connected 🤣 In any case, most of the places we go camping is basically in “tim buck too” 🤣
If you mean, remote code execution, none of these devices are remotely, even connected to anything that resembles any kind of network connectivity.
@lyse@lyse.isobeef.org Sorry what’s RCE?
I can’t decide which DCDC charger to. buy for my Camper trailer. Help me! 🙏 Currently it’s a choice between:
- KickAss 12V/24V 25A DCDC Charger With Solar MPPT + Pre-Wired Anderson
- iTECHDCDC25 12V/24V 25A DCDC & MPPT Battery Charger
- Renogy DCC30S 12V 30A Dual Input DC to DC Battery Charger with MPPT
The only advantage of the Renogy over the KickAss/ITech models is it has Bluetooth monitoring and an App capabilities so you can check the state of the battery/charging/etc from your phone.