Agreed

But I forgot to update the mentions. Oh well. I don’t bother breaking hashes once more, so I just leave it at that. :-)

@prologic@twtxt.net I simply have absolutely no interest in selling my thoughts to others. I don’t like things behind paywalls. Each to their own, but I’m not gonna contribute to that.

(Let’s not rush things, obviously. Such a change would have to be well thought through and actually be worth it. It’s not like the current state of Yarn/twtxt is completely unusable.)

@lyse@lyse.isobeef.org @prologic@twtxt.net Sorry, I have hardly slept last night. 😅 I probably didn’t chose the best words to describe this. 🥴

Yes, I’m all for dedicated message IDs. That would be a whole new format then. But I would be fine with it.

Honestly, me too. When Yarn originally showed up, I was concerned that it would extend twtxt in dramatically incompatible ways or, worse, change it in a way so that you needed server software. 😅 The latter would have ruined it for me. A major reason why I still use twtxt/Yarn is that it’s still just a file you put somewhere. If there was the need to run a daemon, I’d give up and just use some ActivityPub thingy instead.

What I did not expect, however, was that the original twtxt itself would just … die. There has been no development in the original software anymore and virtually all the original feeds are dead. Some feeds are left, but they’re just used as an alternative to Atom/RSS for some blogs. I don’t know what happened behind the scenes that killed off twtxt (I have a few guesses, though), but the sad truth is that it’s gone.

So, yeah, maybe this gives us the freedom now to break with the original twtxt spec (if needed) and come up with a format that fixes the issues we’re seeing.

(Oh god. Are we re-inventing Usenet then? Again? 😂)

@prologic@twtxt.net https://lyse.isobeef.org/tmp/hashes.png Yep, broken hashes. I just fixed them after refollowing on the new URL (my client doesn’t know metadata fields).

@prologic@twtxt.net Yes, that’s when I noticed. Luckily, I had another knive in my bagpack. But I cannot find the folding one at home either. Damn. I already lost my other knive at the flea market in May this year, now the next one. This sucks.

@bender@twtxt.net A Fred changed its url metadata field 🤣

@prologic@twtxt.net “I’m now 100% certain this is what happened”, what exactly happened?

After unfollowing and refollowing on the new feed URL, I’m now 100% certain this is what happened for @cuaxolotl@sunshinegardens.org 🤣 The real problem is really this:

How do we identify a feed?

It cannot be the URL, because the author could change where they serve it from. This was as “good” as we could get it, but time and time again this has proven to be problematic for, well, a few folks that change their mind, which frankly should be allowed 😅

For supporting edits, I was thinking more along the lines of: If a client edits a Twt already published, it should put the hash of the previous Twt. Something like:

2024-09-05T13:37:40+00:00   (edit:mp6ox4a) Hello world!

To be honest, I don’t really see “editing” as a problem. I see that as a natural behavior of “forking” in the first place, that just forms a. new sub-tree. What’s really problematic here is when a feed author changes the “identity” of their feed and changes the # url = metadata field, which is what I believe @cuaxolotl@sunshinegardens.org has just done, though I’m not 100% certain, I’m like 98% sure haha 😝

@lyse@lyse.isobeef.org Did you check your pocket? 🤣

@movq@www.uninformativ.de It sounds complicated. After reading it only twice, I haven’t gotten it. :-D

Yes, I’m all for dedicated message IDs. That would be a whole new format then. But I would be fine with it. The only thing is that all our clients have to be touched. At the moment, I do not worry about spoofing (however, I definitely should).

Fuck, I lost my pocket knive somewhere.

@movq@www.uninformativ.de Sorry but what’s a partial hash exactly? 🤔

All this hash breakage made me wonder if we should try to introduce “message IDs” after all. 😅

But the great thing about the current system is that nobody can spoof message IDs. 🤔 When you think about it, message IDs in e-mails only work because (almost) everybody plays fair. Nothing stops me from using the same Message-ID header in each and every mail, that would break e-mail threading all the time.

In Yarn, twt hashes are derived from twt content and feed metadata. That is pretty elegant and I’d hate see us lose that property.

If we wanted to allow editing twts, we could do something like this:

2024-09-05T13:37:40+00:00   (~mp6ox4a) Hello world!

Here, mp6ox4a would be a “partial hash”: To get the actual hash of this twt, you’d concatenate the feed’s URL and mp6ox4a and get, say, hlnw5ha. (Pretty similar to the current system.) When people reply to this twt, they would have to do this:

2024-09-05T14:57:14+00:00	(~bpt74ka) (<a href="https://txt.sour.is/search?q=tags:hlnw5ha">#hlnw5ha</a>) Yes, hello!

That second twt has a partial hash of bpt74ka and is a reply to the full hash hlnw5ha. The author of the “Hello world!” twt could then edit their twt and change it to 2024-09-05T13:37:40+00:00 (~mp6ox4a) Hello friends! or whatever. Threading wouldn’t break.

Would this be worth it? It’s certainly not backwards-compatible. 😂

@cuaxolotl@sunshinegardens.org Did you recently change the url metdata key of your feed?

# url = https://sunshinegardens.org/~xj9/twtxt/tw.txt

Was this at one point # url = https://sunshinegardens.org/users/xj9/twtxt/tw.txt?

@lyse@lyse.isobeef.org Please for the love of god, elaborate 😅

@lyse@lyse.isobeef.org da fuq?! same here, what did you just reply to?! 🤔

@lyse@lyse.isobeef.org da hell are you replying to?! 🤣

Offline backups currently cost me around ~$2.00 AUD per month.

Spent the day performing backups (hadn’t done it in a while 😱) and wrote a full backup definition internal document that defines my backup process, scope, security, frequency, backup locations, capacity and backup and restoration procedures. Very happy with the doc and the updated (now fully documented) plan and scheduled backup frequency (once per month, which I’ll put into my calendar as it’s done by hand for now, with tools). So far backing up ~410GB out of a possible ~12.8TB worth of data in two locations – I deliberately don’t backup everything as much of the data can be re-created (music, videos, tv shows, etc). #Backups #Data

@cuaxolotl@sunshinegardens.org Yes, that’s how it works. It never occurred to me that I just start changing things without a plan first.

@cuaxolotl@sunshinegardens.org Hahahaha! :-D

@prologic@twtxt.net Not my cup of tea.

I’ll share my opinion on this later 🤣

What do we think about this? 😅

Swa this pop up in my Github news feed today 🤔

Which links to https://github.com/musingstudio/go-subclub

A Go (golang) library for interacting with the sub.club API.

So I got curious and had a peek 👀

Let’s fund the Fediverse

Posting or hosting on the open social networks no longer means you have to do it for free. Developer Preview now available.

And further down:

Monetize your feeds

If you post quality content and you’ve developed a loyal audience, you should be able to ask your most passionate followers to support you with a premium subscription.

That’s a promise not available on the Fediverse …until now.

Hmmm 🤔

@slashdot@feeds.twtxt.net I can only see a mass exodus of uses fleeing telegram as the service becomes less secure or less privacy focused and basically more shit.

@quark@ferengi.one cheers 🍻

it might have made sense in the days of hose and buggy and smoke signals to centralise everything, but these days we have a globalized interconnected society with fast transport and communications. There is no reason for this model anymore 🤣

@slashdot@feeds.twtxt.net Can we please stop this whole “Back to the Office” garbage nonsense?! 😱 If a job does not require the physical presence of a person(s) to perform their role, or they are not “customer facing” or in a job that’s required to “serve the public”, let’s just stop this utter nonsense. As much as I want my shares in Cromwell to go up, I really don’t care. Let the corporate office buildings burn to the ground for all I care, turn them into cheap housing estates or apartments. Why we ever thought centralizing in once place to live and work is beyond me 🤦‍♂️

@cuaxolotl@sunshinegardens.org No you’re not the only one. I do this too, I often think about a problem in my head, even imagine the code, sometimes for weeks, hell even months, before I even write a line of code 🧑‍💻

@lyse@lyse.isobeef.org Thankfully it’s quite cool here so far 👌

Telegram Disables ‘Misused’ Features As CEO Faces Criminal Charges
Following the arrest of its CEO Pavel Durov last month, the encrypted messaging service said it has disabled some “outdated” and “misused” features used by anonymous users. The Verge reports: The first changes to the app following his arrest in France last month affect its built-in blog posts and a “People Nearby” location-based feature. […] … ⌘ Read more

One can tell the weekend is fast approaching, as things around these parts tend to slow down then. Cheers everyone! :-)

@bender@twtxt.net Hahaha, that’s what you get, suckers!

Je cherche un espace où publier une sorte de blog. Juste du texte. Un truc comme faisait rawtext.club ou midnight.pub, mais qui accepte les nouvelles inscriptions. Vous auriez des suggestions? #smolweb

PwC ‘Tipping the Balance’ of Hybrid Working and Will Start Tracking Its Workers’ Locations
PwC has demanded staff spend less time working from home – and it’s going to start tracking their location to ensure they comply. From a report: The accountancy firm informed its 26,000 U.K. employees in a memo that from January they’ll be expected to be at their desks – or with clients – at leas … ⌘ Read more

@lyse@lyse.isobeef.org funny that you mention it. Sendgrid, for better or worse, cancels your account after X amount of inactivity. It does it in such way you can’t reopen it, you must create a new one. So, I logged in on the account, but really couldn’t do anything. Such predicament would have awaited for the would be phishers as well. So, you see, they were pre-destined to failure without even knowing it. LOL.

@prologic@twtxt.net Tomorrow is getting hot again and then we might be lucky in that the summer is over.

It would be even funnier if @bender@twtxt.net didn’t have a Sendgrid account in the first place. Good catch!

@prologic@twtxt.net it is the attention to detail. Evidently no one from Australia tried to login on my Sendgrid account, but the IP the used correlates to the GeoIP DB.

Interesting 🤔

Notice the detail on the IP address mentioned. It is one assigned to Australia: https://ipgeolocation.io/browse/ip/203.0.113.78

This happened yesterday:

Screenshot of an email, allegedly from Sendgrid

The first give away is the sender, sendgrid@autovitalsinc.com. Not Sengrid. Now, check the URL on the link provided to check the account activity:

https://u906946.ct.sendgrid.net/ls/click?upn=u001.eXk7eIEvNT22LuyWQ0fseoc5VY1jItvxPoavh2wfNVs292YMzvTAPj5D6nek1U6K7UfW_AsM5Hq3TBeAGlZrT-2F3g23iWCcJRPGZ-2B58DJxpgMgOTjgWklNQiAdGiHqmR6FFVhfWZJhnu1PSRslMuKGg1XNZs5e1lGu8kmdKhv7otlghl6qLMXiiXYZcvaUB5NruWwSBFcLdvi31NY-2Fru5oyrcrugm2iLYA0u5TiufyvA7SNTo3sDHx6WtS-2FmfEyN2svb9k1S4QGRFhuDseidMiFm0f9Q-3D-3D

I was curious, so I follow it on my dedicated VM for these kind of things. It took me to a page looking exactly like a Sendgrid login, with a sendgrid.net URL. Upon entering yourmotherisahamster@gmail.com, as username, and yourfathersmellsofelderberries as password, it sent me to https://screenprank.com/gandalf/.

It was well done. This morning the same link renders a blank page with a “Not found” link that takes you to a 404. Hmm…

@bender@twtxt.net That sucks 😢 Sorry to hear you didn’t sleep well 😴

@prologic@twtxt.net well, that’s a mighty reason not to do anything else! It has been already 8 hours, but I wish and hope you had a good night sleep. I woke up today, using 50% of my will power to do so.

rm -fr, remove french-style: merciless colonizer. thief and destroyer of worlds.