@movq@www.uninformativ.de From what I can tell, they use strict semantic versioning and backwards compatibility. There are two versions of the storage, v1 and v2, but it doesn’t look like v2 is enabled yet.

@movq@www.uninformativ.de LOL 😂

B

A

@aelaraji@aelaraji.com Haha 🤣 I’d say it’s just yet-another-bad-bot 🤖 I’ve blocked a lot of such bots and often their entire networks (ASN) 🤦‍♂️

I use restic and Backblaze B2 for offline backup storage at a cost of $6/TB/month. I don’t backup my entire ~20TB NAS and its datasets however, so I’m only paying about ~$2/month right now. I only backup the most important things I cannot afford to lose or annot re-created.

Yes

@javivf@adn.org.es merged in to the repo of specs:

@kate I’ll cut a release soon™, but still a few more things to iron out 🤣 One of the new challenges is figuring out what to do with the “Discover” view now that is has an unconfined limit, on my pod (at least) it’s now basically just “noise” 🤦‍♂️

@kate Been missing your jovial posts too and your friends 🤣

@quark@ferengi.one No editing old Twts that are the root of a thread with replies in the ecosystem. Just results in a fork. Unless the client has an implementation that does not store Twts keyed by Hash.

@movq@www.uninformativ.de Oh dear 😂

@kate The re-fetch should work just fine 🤞

@david@collantes.us Thanks I’ll fix.

@bender@twtxt.net Sure 👻👻👻

@bender@twtxt.net That’s what I’m trying to figure out 🤔

@andros@twtxt.andros.dev Curious where this root twt is?! 🤣 Apparently my pod doesn’t have it and I can’t find it anywhere. It’s suppose to be #l4doaxa

@andros@twtxt.andros.dev For what purpose? 🤔

@xuu@txt.sour.is Yeah @-mentioning@twtxt.net someone you don’t have a local alias for is broken somehow :( I haven’t looked into it yet…

@xuu@txt.sour.is Seems to be fine here?

$ bat https://twtxt.net/twt/yfv5kfq | jq '.text'
"!<dm-echo https://dm-echo.andros.dev/twtxt.txt> U2FsdGVkX1+QmwBNmk9Yu9jvazVRFPS2TGJRGle/BDDzFult6zCtxNhJrV0g+sx0EIKbjL2a9QpCT5C0Z2qWvw=="

@fastidious@tilde.town Haha 🤣

@<@marado@ciberlandia.pt https://tilde.pt/~marado/twtxt.txt> Hey! do you see this? 🧐

@bender@twtxt.net I don’t no. I mostly just use whole themes. And my facourite it AMOLED

@doesnm.p.psf.lt@doesnm.p.psf.lt It was always intended to have both Yarn.social and Salty.im integrate together. Yes. This includes having a set of specifications that anyone can write clients to.

@javivf@adn.org.es Generally speaking if it has been reviewed, discussed and merged, then we accept it as a standard to the set of specs we support. However we might want to document this process and set some guidelines about this to be clear 🤣 We’ve been fairly lax/lose here and I think that’s okay given teh size of our community 👌

@bender@twtxt.net Ahhh ha!!! 🤣 I’m too dumb to have thought of that 🤣

@bender@twtxt.net Do we still want this feature? 🧐

@bender@twtxt.net Would they even accept a server from me? 🧐😂

@eapl.me@eapl.me This is one of my concerns too. The moment you post publicly ciphertext, you open yourself up for future attacks on the ciphertext, which you really want to avoid if you can. If you have a read of the Salty.im Spec you’ll note we went to great lengths to protect the user’s privacy as well as their identity and make it incredibly hard to guess at inboxes. It’s still a WIP, but I’d love to see it progressed even further – I truly feel strongly about a purely decentralised messaging ecosystem 👌

@bender@twtxt.net ping! 🏓

@hacker-news@feeds.twtxt.net I like this 👌

@andros@twtxt.andros.dev Nice! 😊

@bender@twtxt.net Close enough 🤣

@andros@twtxt.andros.dev No worries! 😉

@bender@twtxt.net Sadly my earlier Twt back in ~2020 is now gone from at least this pod’s cache 🤣 – It might still exist in other pods though? 🤔 It does! https://txt.sour.is/twt/o6dsrga

I think I would encourage anyone in this community is to care less about supporting “legacy clients” and focus more on value-add whilst balancing the burden of client authors – which have very precious little “spare time” 🤣

I do think integrating things like Salty.im might actually be a good idea. I can also see a future where we integrate other things like todo.txt and calendar.txt. I’d even love to see decentralised forms of “plain text” voting too.

@andros@twtxt.andros.dev I don’t see any “fighting” here. This is just good experimentation. Unfortunately there hasn’t really been enough time or effort by other “client authors” yet, me especially as I’ve been super busy with ya’ know my “day job” that pays the bills and refactoring yarnd to use a new and shiny and much better SqliteCache 🤣 – I certainly don’t think your efforts are wasted at all. I would however like @doesnm.p.psf.lt@doesnm.p.psf.lt encourage you to look at the work we’ve done as a community (which was also driven out of the Yarn.social / Twtxt community years back).

https://salty.im/

@eldersnake@we.loveprivacy.club No worries! 👌

Morning y’all 👋

@andros@twtxt.andros.dev Ahh I see 👌

@prologic@twtxt.net Yes, it is a security hole. All dm-echo messages are readable. I intend it to be a debugging tool. Maybe I can include a warning message. If many of you see that it is a serious problem, I can remove the links.

@andros@twtxt.andros.dev your feed is spitting out dupes? 🧐

Image

@andros@twtxt.andros.dev I honestly think IRC is better anyway 🤣

@movq@www.uninformativ.de Damn that’s a sexy pidgeon 🤣

@bender@twtxt.net Haha 😆

@bender@twtxt.net I think mentions are fixed 🤣

Oh hello @yarn_police@twtxt.net 🚨

@doesnm.p.psf.lt@doesnm.p.psf.lt Why would you want that lol 😂

This is nuts. Lemme eat dinner first (pizza on the way!) and I’ll fix this utter nonsense 🤣