home.social

#fedimedi — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #fedimedi, aggregated by home.social.

  1. We're adding mastodon.cloud to our #Fediblock list due to the instance seemingly being abandoned with open signups and zero moderation. The burden of us suspending accounts locally is not practical when the instance is out of date and not being maintained.

    It's been flagged since August last year - social.growyourown.services/@F so I don't see it likely that anything is suddenly going to change.

    #MastodonAppUK #Universeodon #FediMedi #MastoAdmin

  2. We're adding mastodon.cloud to our #Fediblock list due to the instance seemingly being abandoned with open signups and zero moderation. The burden of us suspending accounts locally is not practical when the instance is out of date and not being maintained.

    It's been flagged since August last year - social.growyourown.services/@F so I don't see it likely that anything is suddenly going to change.

    #MastodonAppUK #Universeodon #FediMedi #MastoAdmin

  3. We're adding mastodon.cloud to our #Fediblock list due to the instance seemingly being abandoned with open signups and zero moderation. The burden of us suspending accounts locally is not practical when the instance is out of date and not being maintained.

    It's been flagged since August last year - social.growyourown.services/@F so I don't see it likely that anything is suddenly going to change.

    #MastodonAppUK #Universeodon #FediMedi #MastoAdmin

  4. We're adding mastodon.cloud to our #Fediblock list due to the instance seemingly being abandoned with open signups and zero moderation. The burden of us suspending accounts locally is not practical when the instance is out of date and not being maintained.

    It's been flagged since August last year - social.growyourown.services/@F so I don't see it likely that anything is suddenly going to change.

    #MastodonAppUK #Universeodon #FediMedi #MastoAdmin

  5. We're adding mastodon.cloud to our #Fediblock list due to the instance seemingly being abandoned with open signups and zero moderation. The burden of us suspending accounts locally is not practical when the instance is out of date and not being maintained.

    It's been flagged since August last year - social.growyourown.services/@F so I don't see it likely that anything is suddenly going to change.

    #MastodonAppUK #Universeodon #FediMedi #MastoAdmin

  6. Apologies for the blip there impacting a wide range of the sites we run ( #MastodonAppUK / #Universeodon / #FediMedi and for #MastoAdmin The Universeodon relay).

    It looks like the NIC in one of our app servers had some sort of weird failure which prevented traffic on one of the two interfaces and due to it being setup in aggregation and not failover it caused a total outage of that server and all the VM's and CT's running on it.

    We have also identified some issues with our secondary HAProxy instance which we need to get to the bottom of as things did not fail over as expected (Even though we know we haven't got full HA operational yet across all services because storage and RAM prices are through the roof and we need to add a third server for that).

    Apologies again, we should be back to normal for now.

  7. Apologies for the blip there impacting a wide range of the sites we run ( #MastodonAppUK / #Universeodon / #FediMedi and for #MastoAdmin The Universeodon relay).

    It looks like the NIC in one of our app servers had some sort of weird failure which prevented traffic on one of the two interfaces and due to it being setup in aggregation and not failover it caused a total outage of that server and all the VM's and CT's running on it.

    We have also identified some issues with our secondary HAProxy instance which we need to get to the bottom of as things did not fail over as expected (Even though we know we haven't got full HA operational yet across all services because storage and RAM prices are through the roof and we need to add a third server for that).

    Apologies again, we should be back to normal for now.

  8. Apologies for the blip there impacting a wide range of the sites we run ( #MastodonAppUK / #Universeodon / #FediMedi and for #MastoAdmin The Universeodon relay).

    It looks like the NIC in one of our app servers had some sort of weird failure which prevented traffic on one of the two interfaces and due to it being setup in aggregation and not failover it caused a total outage of that server and all the VM's and CT's running on it.

    We have also identified some issues with our secondary HAProxy instance which we need to get to the bottom of as things did not fail over as expected (Even though we know we haven't got full HA operational yet across all services because storage and RAM prices are through the roof and we need to add a third server for that).

    Apologies again, we should be back to normal for now.

  9. Apologies for the blip there impacting a wide range of the sites we run ( #MastodonAppUK / #Universeodon / #FediMedi and for #MastoAdmin The Universeodon relay).

    It looks like the NIC in one of our app servers had some sort of weird failure which prevented traffic on one of the two interfaces and due to it being setup in aggregation and not failover it caused a total outage of that server and all the VM's and CT's running on it.

    We have also identified some issues with our secondary HAProxy instance which we need to get to the bottom of as things did not fail over as expected (Even though we know we haven't got full HA operational yet across all services because storage and RAM prices are through the roof and we need to add a third server for that).

    Apologies again, we should be back to normal for now.

  10. Apologies for the blip there impacting a wide range of the sites we run ( #MastodonAppUK / #Universeodon / #FediMedi and for #MastoAdmin The Universeodon relay).

    It looks like the NIC in one of our app servers had some sort of weird failure which prevented traffic on one of the two interfaces and due to it being setup in aggregation and not failover it caused a total outage of that server and all the VM's and CT's running on it.

    We have also identified some issues with our secondary HAProxy instance which we need to get to the bottom of as things did not fail over as expected (Even though we know we haven't got full HA operational yet across all services because storage and RAM prices are through the roof and we need to add a third server for that).

    Apologies again, we should be back to normal for now.