Skip to content

Piero Bosio Social Web Site Personale Logo Fediverso

Social Forum federato con il resto del mondo. Non contano le istanze, contano le persone

It has been nagging me a lot, but I finally decided to shut down my Pixelfed server.

  • It has been nagging me a lot, but I finally decided to shut down my Pixelfed server.

    There are several reasons. Here are the ones off the top of my mind.

    • Pixelfed governance is unclear and its maintenance is spotty and obscure. The project has no clear roadmap and it all feels very off. Even though I was enthusiastic about @PixelfedGlitch, it still seems like this fork is not attracting enough interest and participation to establish a forward-looking plan.
    • Beyond governance, I share these concerns.
    • I don’t want to maintain a whole instance merely for a single profile—especially after it has been inactive for a long while. Friends and folks who are curious and interested in exploring the Fediverse are welcome to join pan.rent, that is a collective, communal, and cosy instance.
    • I am having trouble with the pixelfed_ynh package for YunoHost. PHP dependencies are a mess and services constantly fail. I believe it’s not the fault of YunoHost packaging, but I am no expert, just a feeling. No energy and not worth figuring it out. I tried for a while, I gave up.
    • I am generally against the idea of having multiple Fediverse accounts on multiple servers for different uses. Instead, I believe we should improve filtering and sorting posts depending on their type, and having one single account linked to one identity. Overall, Mastodon Glitch Edition does the job for my occasional image and video posting, even if it’s not optimal.
    • I want to use the domain https://tmi.pics for a different purpose, probably an Immich server.

    Now, a question for all the sysads out there: what are the best practices you recommend before shutting the server down? I have a strong emotional attachment to the ~15 pictures and posts I have on my profile there.

    What I am doing, so far:

    • saving all Web pages of profiles and posts on the Wayback Machine
    • performing and archiving a YunoHost backup of the application
    • ?

  • It has been nagging me a lot, but I finally decided to shut down my Pixelfed server.

    There are several reasons. Here are the ones off the top of my mind.

    • Pixelfed governance is unclear and its maintenance is spotty and obscure. The project has no clear roadmap and it all feels very off. Even though I was enthusiastic about @PixelfedGlitch, it still seems like this fork is not attracting enough interest and participation to establish a forward-looking plan.
    • Beyond governance, I share these concerns.
    • I don’t want to maintain a whole instance merely for a single profile—especially after it has been inactive for a long while. Friends and folks who are curious and interested in exploring the Fediverse are welcome to join pan.rent, that is a collective, communal, and cosy instance.
    • I am having trouble with the pixelfed_ynh package for YunoHost. PHP dependencies are a mess and services constantly fail. I believe it’s not the fault of YunoHost packaging, but I am no expert, just a feeling. No energy and not worth figuring it out. I tried for a while, I gave up.
    • I am generally against the idea of having multiple Fediverse accounts on multiple servers for different uses. Instead, I believe we should improve filtering and sorting posts depending on their type, and having one single account linked to one identity. Overall, Mastodon Glitch Edition does the job for my occasional image and video posting, even if it’s not optimal.
    • I want to use the domain https://tmi.pics for a different purpose, probably an Immich server.

    Now, a question for all the sysads out there: what are the best practices you recommend before shutting the server down? I have a strong emotional attachment to the ~15 pictures and posts I have on my profile there.

    What I am doing, so far:

    • saving all Web pages of profiles and posts on the Wayback Machine
    • performing and archiving a YunoHost backup of the application
    • ?

    @tommi Mi dispiace, purtroppo non saprei che consigli dare (non essendo un sysadmin). Però posso consigliarti Vernissage: https://mastodon.social/@vernissage
    Sono piuttosto trasparenti su roadmap e costi. Non so se supportano altri media oltre alle foto. È molto foto-centrico come software

    Mi trovo nella stessa situazione con NeoDB. E credo che sia impossibile creare un software "one size fits all". Penso Bonfire possa fare al caso tuo dovrebbe essere super modulare 🐱

  • @tommi Mi dispiace, purtroppo non saprei che consigli dare (non essendo un sysadmin). Però posso consigliarti Vernissage: https://mastodon.social/@vernissage
    Sono piuttosto trasparenti su roadmap e costi. Non so se supportano altri media oltre alle foto. È molto foto-centrico come software

    Mi trovo nella stessa situazione con NeoDB. E credo che sia impossibile creare un software "one size fits all". Penso Bonfire possa fare al caso tuo dovrebbe essere super modulare 🐱

    Grazie @emanuelecariati! In realtà trovare un’alternativa è l’ultima delle mie necessità, sto benissimo così ahah

    Però non appena sarà possibile vorremmo provare a migrare tutto pan.rent da Mastodon Glitch Edition a Bonfire, dato che @ivan mi ha già accennato diverse volte che fare una migrazione del database è abbastanza fattibile se ti mantiene lo stesso dominio.

  • Grazie @emanuelecariati! In realtà trovare un’alternativa è l’ultima delle mie necessità, sto benissimo così ahah

    Però non appena sarà possibile vorremmo provare a migrare tutto pan.rent da Mastodon Glitch Edition a Bonfire, dato che @ivan mi ha già accennato diverse volte che fare una migrazione del database è abbastanza fattibile se ti mantiene lo stesso dominio.

    @tommi @ivan Oh wow. A me piacerebbe fare la stessa cosa con varese.social.

    Sto pensando di spostare l'istanza da masto.host su un VPS dedicato. Potrebbe essere una buon occasione per cambiare e passare a Bonfire.

    Sarei super curioso di sapere quanto sia fattibile!

  • @tommi @ivan Oh wow. A me piacerebbe fare la stessa cosa con varese.social.

    Sto pensando di spostare l'istanza da masto.host su un VPS dedicato. Potrebbe essere una buon occasione per cambiare e passare a Bonfire.

    Sarei super curioso di sapere quanto sia fattibile!

    This post is deleted!

Gli ultimi otto messaggi ricevuti dalla Federazione
Post suggeriti
  • Ah bello!

    Uncategorized wannabeadmin fediadmin ovhcloud
    1
    0 Votes
    1 Posts
    5 Views
    Ah bello! Come mai nessuno mi ha detto che serviva un CDN e dell’ObjectStorage per Mastodon? E mo? Ha senso usare OVHCloud per tutto oppure spezzetto e trovo in giro provider che offrono i servizi a basso prezzo? Chiedo agli admin che salvano tutto su VPS se ha senso a lungo andare oppure no#wannabeadmin #fediadmin #ovhcloud
  • 0 Votes
    9 Posts
    58 Views
    @julian just for reference, this was the 2013 spec. https://www.w3.org/TR/web-intents/@dansup.bsky.social @dansup
  • 0 Votes
    4 Posts
    20 Views
    @rperezrosario if I just boost, I'd guess the language setting comes from the boosted post? (Do you know?)
  • 0 Votes
    2 Posts
    16 Views
    @WeirdWriter @rysiek These two paragraphs struck me in particular:> That’s in stark contrast to, say, Google+, which despite corporate backing, incomparably larger budget, and being pushed down people’s throats through forced integration with YouTube, survived mere seven years, nine months, and a week.Because unfortunately Google probably doesn't see that as a problem. Or even as the Fedi winning. For them, longetivity doesn't matter, but peak user count.> And once it shut down, it shut down. A social network of millions just blipped out of existence one day. All those moments – lost in time, like tears in rain.This, too, for them is a good thing. No-one else can profit from "their" data.This just makes it so crystal clear how the big one's interests aren't aligned with ours. Google+ wasn't really failing in their book, it had served its purpose and then ceased to do so. To us, this is loss. To Google this is just business.