@bender@twtxt.net Makes sense. We definitely need the ability to mute feeds from the Discover feed.

@movq@www.uninformativ.de I remember your solution. It’s very simple, I like it.

Yes, my backup target is my home server. I have a hard drive dedicated to Restic repositories. It’s still not a real backup as I don’t have anything offsite but it’s better than my previous solution. I had two very old hard drives I kept plugged in to my desktop PC and I would (on very rare occasion) plug in another hard drive and copy all the files over to it. Luckily, I’ve never suffered any significant data loss and I would rather not start now. Once I have automated backups on each of my machines, the next project is getting those backups offsite.

@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.

@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 🤣

@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!

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 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@twtxt.net 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

@slashdot@feeds.twtxt.net Oh boi! 😆 Gotta take a screenshot of this in case Microsoft demand the article be taken down 🤣

@dfaria Also, I don’t really care whether you continue to use my pod or not frankly.

One more reason not to use https://twtxt.net/

negative comments like this are completely unconstructive and have no basis in merit. If you have issues with the way I administer my pod, speak up, provide alternatives. If you have good technical suggestions for Twtxt/Yarn, we’re all ears. We are only trying (or attempt to try) to make things better for all, which as you can appreciate is a hard thing to do.

Next time, please leave your constructive criticisms at home. No-one forces you to use my pod (for free).

Oh never mind! 🤦‍♂️ That’s your other feed that you syndicate some stuff to? 🤔 Research?

@dfaria And btw, even if I block a feed or whole domain, it doesn’t stop you from following. it just removes it from the “Discover” view.