Salta al contenuto
Citiverse è uno spazio aperto a tutte le comunità. Se vuoi aprire un gruppo locale o una sezione per la tua organizzazione, puoi contattare gli amministratori: pagina dei contatti.

Slrpnk.net is down

Fediverse
43 19 5
  • poVoq here. I am starting to think I am cursed, because everything works fine (or is at least fixable with a remote server restart) until the second I go on a longer business trip and can't easily access the hardware.

    Remote access is mostly lost, but I was able to triangulate the issue and of course it is something I had on my list of potential issues, but as a low priority item 🫠 At least it isn't the same problem again as in 2025.

    What exactly triggered the issue is unclear though. I was still able to access the reverse-proxy server yesterday (shortly before it went down) and tried to do some updates for that php security problem in a VM that runs on the same machine. I thought I had those covered, but there is a slight chance that it is related and someone chained another exploit to escape the VM.

    Anyways, it looks like the realistic / not overly optimistic scenario is that the server will stay down until christmas. I did have someone who could restart the servers on site until this summer, but they had to relocate to mainland Portugal for job reasons (tourism sector) and so they will also only return for christmas.

    So yeah, not great at all, and I will have to think more seriously about how compatible this kind of self-hosting is with my current job, which limits my access to the servers for a few weeks at least once a year. It was easier during the pandemic times when I started all this, as deployments were shorter and more seldom back then.

    scritto ultima modifica di supersquirrel@lemmy.ca
    #34

    poVoq here. I am starting to think I am cursed, because everything works fine (or is at least fixable with a remote server restart) until the second I go on a longer business trip and can’t easily access the hardware.

    Have you tried leaving for a couple hours and then coming back and giving the server a couple of bytes of a treat? You know, ease the server into you leaving a bit with some training.

  • poVoq here. I am starting to think I am cursed, because everything works fine (or is at least fixable with a remote server restart) until the second I go on a longer business trip and can't easily access the hardware.

    Remote access is mostly lost, but I was able to triangulate the issue and of course it is something I had on my list of potential issues, but as a low priority item 🫠 At least it isn't the same problem again as in 2025.

    What exactly triggered the issue is unclear though. I was still able to access the reverse-proxy server yesterday (shortly before it went down) and tried to do some updates for that php security problem in a VM that runs on the same machine. I thought I had those covered, but there is a slight chance that it is related and someone chained another exploit to escape the VM.

    Anyways, it looks like the realistic / not overly optimistic scenario is that the server will stay down until christmas. I did have someone who could restart the servers on site until this summer, but they had to relocate to mainland Portugal for job reasons (tourism sector) and so they will also only return for christmas.

    So yeah, not great at all, and I will have to think more seriously about how compatible this kind of self-hosting is with my current job, which limits my access to the servers for a few weeks at least once a year. It was easier during the pandemic times when I started all this, as deployments were shorter and more seldom back then.

    scritto ultima modifica di
    #35

    Thank you for your service, and thanks for the update. Would an IP KVM help here? Know some of them can cycle power remotely, and they're getting a lot cheaper

  • Thank you for your service, and thanks for the update. Would an IP KVM help here? Know some of them can cycle power remotely, and they're getting a lot cheaper

    scritto ultima modifica di
    #36

    I bought a chinese PiKVM copy last time it happened, but ran into issues with the usb otg connection which I procastrinated on to fix, so it currently only shares the screen but not the input. But I also connected it to the main router which is supposed to run the ssh tunnel and reverse-proxy eventually but right now those run on a seperare server and that one went down 🫠

    So yeah, I am victim of my own half finished stuff as well as security hardening that now locked myself out pretty much...

  • I bought a chinese PiKVM copy last time it happened, but ran into issues with the usb otg connection which I procastrinated on to fix, so it currently only shares the screen but not the input. But I also connected it to the main router which is supposed to run the ssh tunnel and reverse-proxy eventually but right now those run on a seperare server and that one went down 🫠

    So yeah, I am victim of my own half finished stuff as well as security hardening that now locked myself out pretty much...

    scritto ultima modifica di
    #37

    Happens to the best of us. I'm just glad it's a glitch not a crisis, and temporary not permanent 🙂

  • poVoq here. I am starting to think I am cursed, because everything works fine (or is at least fixable with a remote server restart) until the second I go on a longer business trip and can't easily access the hardware.

    Remote access is mostly lost, but I was able to triangulate the issue and of course it is something I had on my list of potential issues, but as a low priority item 🫠 At least it isn't the same problem again as in 2025.

    What exactly triggered the issue is unclear though. I was still able to access the reverse-proxy server yesterday (shortly before it went down) and tried to do some updates for that php security problem in a VM that runs on the same machine. I thought I had those covered, but there is a slight chance that it is related and someone chained another exploit to escape the VM.

    Anyways, it looks like the realistic / not overly optimistic scenario is that the server will stay down until christmas. I did have someone who could restart the servers on site until this summer, but they had to relocate to mainland Portugal for job reasons (tourism sector) and so they will also only return for christmas.

    So yeah, not great at all, and I will have to think more seriously about how compatible this kind of self-hosting is with my current job, which limits my access to the servers for a few weeks at least once a year. It was easier during the pandemic times when I started all this, as deployments were shorter and more seldom back then.

    scritto ultima modifica di
    #38

    So you're saying this might all be because of AI (which found the security flaw in PHP, which caused the maintenance, which happened sometime around when the server went down). Sounds fair to me.

    💕 Seriously, thanks for the update and I know sysadmining can be a stressy job. Take care of yourself.

  • So you're saying this might all be because of AI (which found the security flaw in PHP, which caused the maintenance, which happened sometime around when the server went down). Sounds fair to me.

    💕 Seriously, thanks for the update and I know sysadmining can be a stressy job. Take care of yourself.

    scritto ultima modifica di
    #39

    I don't think it was actually the php issue that took it down, but I don't wan't to rule it out entirely. But I had some issues with spotty remote connection for a while now that that is likely due to LLM scraper load.

  • I don't think it was actually the php issue that took it down, but I don't wan't to rule it out entirely. But I had some issues with spotty remote connection for a while now that that is likely due to LLM scraper load.

    scritto ultima modifica di
    #40

    Oh yeah, I was teasing about the php. From what I've read it's wicked hard to real-world implement an attack using it.

    Scrapers, I'd believe. They've been fierce lately.

  • poVoq here. I am starting to think I am cursed, because everything works fine (or is at least fixable with a remote server restart) until the second I go on a longer business trip and can't easily access the hardware.

    Remote access is mostly lost, but I was able to triangulate the issue and of course it is something I had on my list of potential issues, but as a low priority item 🫠 At least it isn't the same problem again as in 2025.

    What exactly triggered the issue is unclear though. I was still able to access the reverse-proxy server yesterday (shortly before it went down) and tried to do some updates for that php security problem in a VM that runs on the same machine. I thought I had those covered, but there is a slight chance that it is related and someone chained another exploit to escape the VM.

    Anyways, it looks like the realistic / not overly optimistic scenario is that the server will stay down until christmas. I did have someone who could restart the servers on site until this summer, but they had to relocate to mainland Portugal for job reasons (tourism sector) and so they will also only return for christmas.

    So yeah, not great at all, and I will have to think more seriously about how compatible this kind of self-hosting is with my current job, which limits my access to the servers for a few weeks at least once a year. It was easier during the pandemic times when I started all this, as deployments were shorter and more seldom back then.

    scritto ultima modifica di
    #41
    Questo post è eliminato!
  • poVoq here. I am starting to think I am cursed, because everything works fine (or is at least fixable with a remote server restart) until the second I go on a longer business trip and can't easily access the hardware.

    Remote access is mostly lost, but I was able to triangulate the issue and of course it is something I had on my list of potential issues, but as a low priority item 🫠 At least it isn't the same problem again as in 2025.

    What exactly triggered the issue is unclear though. I was still able to access the reverse-proxy server yesterday (shortly before it went down) and tried to do some updates for that php security problem in a VM that runs on the same machine. I thought I had those covered, but there is a slight chance that it is related and someone chained another exploit to escape the VM.

    Anyways, it looks like the realistic / not overly optimistic scenario is that the server will stay down until christmas. I did have someone who could restart the servers on site until this summer, but they had to relocate to mainland Portugal for job reasons (tourism sector) and so they will also only return for christmas.

    So yeah, not great at all, and I will have to think more seriously about how compatible this kind of self-hosting is with my current job, which limits my access to the servers for a few weeks at least once a year. It was easier during the pandemic times when I started all this, as deployments were shorter and more seldom back then.

    scritto ultima modifica di
    #42

    And here I was thinking I was silly for asking that question last month on where to find you if we're down. I ruined it guys, it's my fault. I jinxed it. 😂😭😭

  • Bad luck for Ecospheres community

    scritto ultima modifica di
    #43

    I was hoping it was just glitchy the last couple days because I was going to make wiki edits to !nolawns@slrpnk.net and !Cleanit@slrpnk.net ugh

  • 2 Votazioni
    61 Post
    0 Visualizzazioni
    openstars@discuss.onlineO
    I think what you are referring to is not content so much as that new communities needed - in the past - to have been added by someone before others could find them in the community listing. This was not restricted to admins though & people like Blaze had an army of alts and did much of that, as did I on my own instances as well. This was necessary before the first post could come in from each new community, needing to be performed on a per-community basis. However, PieFed made an improvement to not need to do this anymore, and then Lemmy followed suit as well, and now the whole process is much easier. Although it gives Lemmy.ml specifically veto power in that if a community is banned or the instance it is on is defederated from Lemmy.ml, then the automatic pulling in of the community name is no longer done. Technically admins - or again, I think anyone - can always add it the old way, but only if you know that it exists and how to make that happen (which isn't hard but requires crafting a URL rather than mere clicking on links). Also, the admins can designate a different instance than Lemmy.ml, though Lemmy.ml is set as the default, so this procedure is opt-out. Those PyLova devs are hella impressive!!! Rimu seems less interested in the Threadiverse these days and more in interoperability with Mastodon, despite how most of us seem to not even want that, and Mbin already exists. It's okay for him to work on whatever he wants, but it makes it all the more impressive to see how responsive the PyLova is to the needs of the people on the Threadiverse. I don't think that most instances do delete old content. Lemmy.world self-reportedly has content from decades in the past from nodeBB but I think their database got corrupted and I don't trust that. However, here is an example on my own instance https://discuss.online/post/5497584 showing the retaining of a post to a community on Lemmy.ml from 8 years ago. The PieFed thing was once again another of Rimu's rants against "unserious" meme content. He is obviously entitled to not feel forced into providing unlimited hosting for images, but I am saying that the limitation built into the PieFed software and enacted on e.g. PieFed.social may not be universally applied. I could well see e.g. lemmynsfw.app choosing differently to retain every image forever. Unfortunately there's almost no way to know short of directly asking the admin team, who may not even be aware themselves what settings are in place on their own machines. This is a limitation of all Fediverse software that I've seen, including Lemmy and Mbin, so not just PieFed. Though PyLova does have the most transparency of all of them... and yet I haven't seen even PyLova expose whatever these settings are to the public. Even though someone might make a choice as to which instance they want to make an account on (or even start up their own) if they could find the answer. I think even subscribable blocklists would only be the first part of an overall answer. Like UBlock Origin, it's going to require people to manufacture and maintain those lists. But... at least the software will support that now, so yes indeed this is the very important, crucial first step!!
  • 0 Votazioni
    1 Post
    16 Visualizzazioni
    Nessuno ha risposto
  • 0 Votazioni
    1 Post
    10 Visualizzazioni
    Nessuno ha risposto
  • 24 Votazioni
    6 Post
    30 Visualizzazioni
    X
    The style looked extremely AI to me: repetitive, "not X but Y", tiny sentences, even "every X a Y" variant. Tested and appears true.
  • 1 Votazioni
    76 Post
    94 Visualizzazioni
    hyblon@social.vivaldi.netH
    @smallcircles @spraoi @gumnos @evanBefore we started internalizing the jargon from across the pond, we Italians had a habit of simply calling someone a “testa di cazzo,” roughly “dickhead.” It was neutral and inclusive: it could apply to anyone. We didn't need words like fascist, racist, homophobe, antivaxxer, Russian troll, or whatever else is trendy. Someone could simply be a dickhead. Nothing less, nothing more.
  • 0 Votazioni
    3 Post
    26 Visualizzazioni
    evan@cosocial.caE
    @julian yes! We had a room full of about 30 people go through an 8-step onboarding. It worked really well!
  • 0 Votazioni
    2 Post
    35 Visualizzazioni
    cookifed@fosstodon.orgC
    We're still in kinda stealth mode, as we don't have any formal release yet, and our instances are invite-only.But we will publish our first release after the holidays, and start openly inviting folks around the same time.Until then, you can find us at https://cookifed.dev !
  • 0 Votazioni
    7 Post
    27 Visualizzazioni
    kentnavalesi@mstdn.socialK
    @julian@fediverse People always of think of the algorithm as something that delivers content -they don't think about the things it filters out.

Citiverse è un progetto che si basa su NodeBB ed è federato! | Categorie federate | Chat | 📱 Installa web app o APK | 🧡 Donazioni | Privacy Policy

Il server utilizzato è quello di Webdock, in Danimarca. Se volete provarlo potete ottenere il 20% di sconto con questo link e noi riceveremo un aiuto sotto forma di credito da usare proprio per mantenere Citiverse.