Login
You're viewing the mastodonapp.uk public feed.
  • James BaillieJubalBarca@scholar.social
    Oct 21, 2026, 4:56 PM

    Also this is a sour PSA, but I'm inevitably seeing people going "oh I'm so glad I don't use (thing having problem)" or "this is why you should all have used (my preferred alternative that isn't having problem)"

    This really isn't a great time to do that. It can across as smug or lecturing to people who are cooking themselves fixing stuff urgently in difficult circumstances, and people often do have valid reasons for not using or knowing how to use whatever your preferred technology is.

    #PHP

    💬 3🔄 7⭐ 0

Replies

  • 💬 1🔄 0⭐ 0
  • Adampseudomonas@mastodon.social
    Oct 21, 2026, 5:18 PM

    @kboyd @JubalBarca @Girgias Something that would be useful (quite possibly already exists): centralised website off-switch; a remote and trustworthy org that knows your tech stack and desired policies and which your server polls for instructions to disable/modify elements pending being patched, so you can get an SMS saying "this is now down until you fix it and turn it on again"

    💬 1🔄 0⭐ 0
  • 💬 1🔄 0⭐ 0
  • Adampseudomonas@mastodon.social
    Oct 21, 2026, 8:24 PM

    @kboyd @JubalBarca @Girgias Basically, yeah; there's plenty of times when a short period of downtime now is better than a long period later especially if you have to spend that long period testing how well your backup system has worked.

    Ideally you have some details about what you care about; you might care about remote code execution but not about say exfiltration of database contents if you don't host non-public data.

    💬 0🔄 0⭐ 0
  • AsbestosAsbestos@pnw.zone
    Oct 21, 2026, 5:26 PM

    @JubalBarca
    Not to mention that doing so increases the chances of your preferred alternative have a major issue by at least 1500%

    💬 0🔄 0⭐ 0
  • 💬 0🔄 0⭐ 0