I can open the post, but scrolling is not very smooth - it might be a memory issue given the size of the images?

This sounds pretty awesome tbh. Will check out the two books mentioned.

It started with a popular mastodon posts on how to block openai crawlers I think, and I’d like to know whether people are actually implementing it.

Private project, not really security related: Crawling robots.txts to gather some statistics on which bots people are most often excluding - weirdly I couldn’t find any recent/regularly updated stats on this.

I think this is a good idea and wish you all the best.

Moderation will be key of course, but the rules ( http://diagonlemmy.social/post/108 ) sound good.

At the same time, if somebody doesn’t even want to think about HP, they can easily block the entire instance, no harm no foul.

Pretty sure it’s lemmy.world that’s having problems: https://lemmy-world.statuspage.io/

When checking your profile the images you posted in lemmy.world communities won’t load for me either, while other images load just fine.

I really like the app for my personal reading tracking. Been using it for a couple years, and this year (?) there was a huge update that improved it a lot (better UX/UI and statistics if I’m not mistaken).

It’s mostly an app that does what it should, but not more, and gets out the way, which is awesome.

Don’t mind me, just testing ^^

Edit: true, should probably be changed.

Thanks for recommending it, it does look really nice. I’ll definitely check it out when a fitting project comes along.

Just in case you or another reader isn’t aware: Eternity is available in an alternative app repository that can be added to F-Droid in the settings.

https://apt.izzysoft.de/fdroid/repo?fingerprint=3bf0d6abfeae2f401707b6d966be743bf0eee49c2561b9ba39073711f628937a

This repo, as stated in the description, takes released built by the developers instead of building them directly.

Still looking forward to the official F-Droid release of course :)

I mean, this is a light-hearted meme, no offense to the people actually fixing things.

But at a company like GitHub the first status update should be and probably is created semi-automatic (just approved by a human). Afterwards they should follow a process to assign an incident communication lead, who takes over all communication so that the rest of the team can work on fixing the incident.

@GitHub: Hire me for more incident response tips from the backseat! :P

I’m actually not that into actual self-hosting (it feels too close to my day job). But i love the idea of it, and actually do host my own RSS Reader: It’s selfoss (PHP + SQLite, so, very simple) and i have been using ever since google reader shut down. It runs on my uberspace.de instance.