@bender@twtxt.net What is?! 😆

@prologic@twtxt.net “it’s a thing!” 🤣

@lyse@lyse.isobeef.org Ahh yea! I’ll setup some CD for it this weekend 👌

@bender@twtxt.net Hmmm? 🤔

@movq@www.uninformativ.de it is all in the context. When referring to computers, if the person uses Microsoft Windows, then colloquially the user “is on Windows”, for example.

For PowerPoint is simpler, as nothing else is called that way, nor have the same spelling. But yeah, similar to “gonna grab a Coke”. It is intrinsically embedded in the language.

@bender@twtxt.net lol 😂

So you don’t feel a bit weird when you say “Windows” or “PowerPoint”? It’s just a brand, nothing special?

@prologic@twtxt.net Speaking of broken mentions, do you want to install a more recent yarns version so that my error log is not spammed anymore with 404s? 8-)

@movq@www.uninformativ.de Zero progress on mine. :-( I still rely on the official twtxt client to download the (main) feed.

Thanks, @movq@www.uninformativ.de! Hahaha, didn’t think of that. :-D Nah, this guy is not creepy, he’s just a melting flower snowman. ;-) Rest assured, he was unharmed on the table, you can see him here: https://lyse.isobeef.org/waldspaziergang-2024-04-21/23.JPG

Google:

I often wonder what it must be like for native English speakers to use all these so-called brand names. “I use window 11! This is a KraftPoint presentation. I got the code for this script from the idiot turnstile.” All that sort of thing.

🤣🤣🤣

@movq@www.uninformativ.de I figure the same as for non-native. LOL. All translation services are doing a poor job at translating your twtxt. 😭

Jaja, @movq@www.uninformativ.de, immer schön aufmerksam der guten Steckdosenpräsi folgen und im Anschluss in der Exzellenztabelle was eintragen und ausrechnen lassen! :-D Klingt alles recht albern. Ich schätz aber mal, dass einem das gar nicht mehr auffällt.

@bender@twtxt.net Fenster 11 → Windows 11; KraftPunkt (or Steckdose) → PowerPoint; Deppendrehkreuz (awesome translation btw, I had to laugh hard!) → GitHub.

Absolutely lovely. 🫢

Ich frag’ mich schon oft, wie das für die englischen Muttersprachler sein muss, all diese sogenannten Markennamen zu benutzen. „Ich benutze Fenster 11! Das hier ist eine KraftPunkt-Präsentation. Den Kode für dieses Skript habe ich vom Deppendrehkreuz.“ All sowas. 🤔

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

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

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

Image

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

Ex-White House Cyber Policy Director: Microsoft is a National Security Risk
This week the Register spoke to former senior White House cyber policy director A.J. Grotto — who complained it was hard to get even slight concessions from Microsoft:
“If you go back to the SolarWinds episode from a few years ago … [Microsoft] was essentially up-selling logging capability to federal agencies” instead of ma … ⌘ Read more

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

@bender@twtxt.net +1

@dfaria@twtxt.net And here I thought you never or we’re not capable (client?) of interacting with other users? 🤣

@lyse@lyse.isobeef.org Same 😢

@eapl.me@eapl.me We went out for nice breakfast and put the camper trailer away 😅

@mckinley@twtxt.net Yeah pretry by hand at the moment.I only backup what I cannot reproduce.