If nobody on your server follows them, they don’t cause any load to your server. Also admins can suspend the whole instance.
It’s still going to waste electricity etc, but it can easily be cut off the fediverse.
If nobody on your server follows them, they don’t cause any load to your server. Also admins can suspend the whole instance.
It’s still going to waste electricity etc, but it can easily be cut off the fediverse.

“disk” is wherever root is mounted or …? No mention of supported OSes etc.

It’s also in the screenshot which is another “interesting choice”

Oh, I hold anti AI views :-) Just not so fierce that I want to be warned of every mention

Therefore, you’ll want to be able to sort by [Not AI]
No, I don’t. I’d rather have no tags at all and some AI posts in there than every post needing annoying tags in the title. Also not every post is related to a specific piece of software

Yes, the crowd will point it out if the author didn’t and you can decide what to make of it. It’s probably discouraging to post slopware if you know you’re in for a lot of criticism, I’m not sure if it’s better or worse than being forced to flag it [AI].

I’d be fine with the end, but it’d probably be overlooked a lot. Given how long some of these posts are, they would probably be hidden these as well unless the post starts with [Disclaimer: this has mostly been vibe coded]

I absolutely don’t want Meta Tags in every titles. It makes reading the list of posts super annoying.
I also don’t feel the need to know whether there’s some AI commits, but I do want to know if a project is largely vibe coded. I don’t have an objective metric on where this line could be drawn.
I think the status quo is kinda fine. Some commenter will point it out and will get enough upvotes to be visible on first glance. It’s not perfect but good enough for me.

But it’s annoying. Non AI should be default, AI has to be marked.

Any source, or just making up stuff?

It’s been a while, but I think I used this: https://wiki.archlinux.org/title/Dm-crypt/Encrypting_an_entire_system#LUKS_on_a_partition

Yes, the dual partition approach is what I usually do with LUKS
Good stuff as always. The “There Are No Instances in atproto” post was interesting, I think I finally kind of got the concept.