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
• ?

#Pixelfed #YunoHost #Fediverse #PixelfedAdmin #admin #FediAdmin #sysAd #systemAdministration #sysAdmin

Good morning Fedi friends!

I'm currently in the east of France visiting extended family.

We're snowed in, everyone in the house is still asleep and I'm in the kitchen, near the fire, sipping coffee and setting up a new self-hosted app: #Umami (a privacy-respecting website analytics app).

How long did it take me to connect my 3 websites? 5 minutes.

Thank you #YunoHost for making all this possible!

#MySoCalledSudoLife

Good morning Fedi friends!

I'm currently in the east of France visiting extended family.

We're snowed in, everyone in the house is still asleep and I'm in the kitchen, near the fire, sipping coffee and setting up a new self-hosted app: #Umami (a privacy-respecting website analytics app).

How long did it take me to connect my 3 websites? 5 minutes.

Thank you #YunoHost for making all this possible!

#MySoCalledSudoLife

#SelfHosting week 0, phase 1B: DNS records settings. Performed @_elena 's instructions on her "self hosting for newbies" part 2. Except for the post-install as I run it through terminal and not through web UI. For an ms-dos-born it's easier to perform a simple command such as "yunohost tools postinstall" rather than go to web, then type, then search for the various UI elements.
Everything went smooth, except for letsencrypt at first. But in the end it seems to have worked. It got stuck because hostinger panel didn't get one suggested parameter, the numeric 3600, every record has a parameter which is 3, 4 or 5 numbers.
Created the domain and subdomain to point it to yunohost admin interface, and then obstacle came.
Opening browser to subdomain, just returns "connection timed out".
Checked for nginx parameters through yunohost terminal, using the desired Sudo commands.
Then, "sudo yunohost diagnosis run"
"sudo yunohost diagnosis show --issues --human-readable"
and I got explanation on reverse dns which was wrong.
After that, I searched on the web (and on AI, I admit) the position on hostinger panel to set them, and I found "set tpr record"
placed the desired domain name.
And now it's time to wait for propagation. But what about the "connected timeout", in the article posted in blog.elenarossini.com no such obstacle was mentioned.
I'm back to my 20s when I spent the night (it's almost 4 in the morning), learning commands.
Last but not least, accessibility issue: I'm using an app called WebSSH pro, downloaded on app store. Set it up, and VoiceOver for iOS does not read the keys I press on keyboard so I'm very slow to type commands there. Pc is better. In a few hours I'll try hostinger's terminal.
UPDATE: I have just found I set one DNS wrong, now I'll wait for it to propagate. Next update in some hours. I placed a useless number. Such as 72.162 (wrong) instead of 72.62 (right).
Like when you start developing on your own and everything crashes due to a missing semicolumn in a string of code.

#accessibility #yunohost #selfhost #blind