It’s a Thing! ⌘ https://notiz.blog/b/71d

@movq@www.uninformativ.de

If you all were to clear your caches, would your clients fetch archived feeds?

No.

And I’m also thinking of nuking my pod at some point and starting over. But maybe after we refactor a few important things.

@mckinley@twtxt.net My process hasn’t changed. (But the Gopher hole is gone. Here’s the file from 2023: https://movq.de/v/72fddfd8fe/2023-05-31–backups.txt )

What is your backup target btw? This NFS drive you’re speaking of is probably hosted on one of your local servers running in your apartment/house?

@bender@twtxt.net 🤣 Bug free code, I wish. 😅

On a more serious note, how’s the adoption of Archive Feeds going? If you all were to clear your caches, would your clients fetch archived feeds? 🤔

(I’m kind of thinking about truncating my history, to be honest. There’s a lot of twts out there, many of them out-of-context by now. They’re of little use except maybe for showing that twtxt/Yarn is an “active platform”.)

@bender I think it comes down to one of the principles Yarn.social was founded on, which is to say, users should have choices and what they “see” is not driven by “algorithms”. The “Discover” view in and of itself has utility/value to others, and is otherwise just a “view” of a pod’s cache, but I agree with you. It was even getting noisey for me 🤣

@lyse@lyse.isobeef.org It’s great to see so much “green”. 👌

The sequence of photos makes it look like you throw this (pretty creepy) snowman to the ground. 😂

@mckinley not a problem, but I don’t want to see it. When I get to see it constantly, without following it, then it becomes a problem. Blogs being echo chambers do not bother. They don’t “come to me”. :-D

@aelaraji@aelaraji.com Unofficially yarn supports the type field

Meg https://feeds.twtxt.net/slashdot/twtxt.txt

@aelaraji@aelaraji.com Probably not? https://dev.twtxt.net/doc/metadataextension.html

@aelaraji@aelaraji.com Same to you!

Good Morning everyone! Wishing all of you a productive and Happy Monday!

@prologic I
wonder if there’s something I can add to this test feed’s metadata to get it unlisted so no
one follows it by accident.

In other words, there isn’t anything specifically wrong with the Twtxt spec (+extensions), but if you for example use a client and server combination that never considered the User-Agent header and check logs or intercept requests for your feed, than you end up missing an important part of the whole flow (unless you are of course deliberating ignoring that, e.g: 1-way feeds, news feeds, etc).

In my opinion, this can all be solved by a “better standard client”.

For example I noticed in this thread, someone, me, and you, and now it’s just a bad @-mention mentioned Soren Peter with a bad link :/

This also just reminds me of the other problems that exist:

• bad mentions.
  
• knowing whether someone will you’ve @-mentioned will even see your reply at all.

@mckinley@twtxt.net I think we just need a way of surfacing this information better for both users and operators? 🤔

@mckinley@twtxt.net I did!

@mckinley Yeah this is what was being “cleaned up”

Yo be honest I don’t think there is a good solution IMO

@prologic I think one-way feeds are okay and we shouldn’t discourage them so strongly. On the other hand, I think it’s the duty of a poderator to filter out feeds that are just noise from the Discover feed. I definitely consider a truckload of one-way posts mostly in another language to be noise. Did you get rid of Gopher Chat too? I’d call that noise, for sure.

You’re right we should
never be like Microshit 😆

@bender@twtxt.net Standard twtxt is a microblog in its purest form. A blog, but smaller. It’s just a list of posts to read, and that’s an echochamber in the same way my regular blog is an echochamber. I don’t think there’s anything wrong with that.

@prologic@twtxt.net I support the delisting of ciberlandia.pt in the Discover feed due to the sheer volume of posts from there and the fact that most of them are in Portuguese with this being a predominantly English-language pod.

@mckinley I think “posting to the void” was/is a poor choice of words hete.

@prologic@twtxt.net Why do we need to avoid posting to the void? That’s pretty much what twtxt was made for. I don’t like the “Legacy feed” terminology, either. I support the delisting of ciberlandia.pt but I think this change is heading in a bad direction.

I like @sorenpeter@darch.dk ’s suggestion. It gives the users the information and lets them make their own decision instead of putting a big scary warning in their face. That’s what Microsoft does, and we shouldn’t be Microsoft.

Today in the news

Microsoft is a security risk