Michael DiLeo

@mdileo
19 Followers
45 Following
187 Posts
I'm a digital nomad who sold everything and started traveling the world - and I don't know if I'll stop.
Bloghttps://blog.michaeldileo.org
Mastodon blog accounthttps://mastodon.social/@[email protected]ichaeldileo.org
Go to Socialhttps://gotosocial.michaeldileo.org/@mdileo
Keyboard Vagabondhttps://blog.keyboardvagabond.com/michaeldileo/

I just had a video chat over Signal with Nabil (@seengoals) and I’d like to welcome him to the Gaza Verified family.

Nabil is a 33-year-old software engineer and was the founder and CEO of his own company in Gaza before it was destroyed by Israel.

He is also a father struggling to keep his child alive in Israel’s ongoing genocide and the resulting famine.

They are, thankfully, in the South but they still need your help to survive.

“They stole my life, crushed my dignity, they killed me alive.” – Nabil

Please give Nabil and his son a warm welcome to the fediverse, donate to their fundraiser if you can, and share so others might too.

Thank you!

💕

https://gaza-verified.org/

(It might take a little while for him to add the link to his profile.)

#GazaVerified #Gaza #Palestine #israel #genocide #StooIsrael #SropTheGenocide #FreePalestine

Gaza Verified

We’ve personally had video conversations on Signal with the people from Gaza whose Mastodon accounts on the fediverse are listed here and we verify that their accounts are genuine. – Joy & Aral Balkan

Adventures in #selfhosting!
I just finished failing to do a "correct" and "proper" upgrade of cloud-native postgres, #cnpg, from using standard #longhorn volume backups to the barman cloud plugin.

I got the plugin loaded accord to the migration docs, but couldn't get it to write to #s3, nor could the pods become ready. I worked at it for hours, but I saw lots of other people online and recently having the same issues and log messages that I was.

The reason I did this in the first place was that I noticed that I had some duplicate backup jobs causing issues with #fluxcd reconciliation.

In the end, I gave up and went back to the original longhorn backups, which have worked and I've already done disaster recovery with (don't ask), and deleted the duplicates.

Currently I'm waiting for the previous primary/write node to fully restart and clear out the barman side car. Then I'll turn flux back on and hopefully things will be good.

#keyboardvagabond #kubernetes #comingSoonTM

More progress towards #keyboardvagabond, a fediverse space for digital nomads and backpackers! It's a baby step and a place holder, but www.keyboardvagabond.com is a thing that loads.

I already have 7 issues on my #gitea instance. It's more of an outline at this point, but things are getting closer. There's still a decent amount of work to do for prepping to go live in general for all of the services.

#fediverse #selfhost #kubernetes #piefed #mastodon #pixelfed #writefreely #picsur #digitalnomad #vagabond

The only reason you assassinate every Al Jazeera journalist left in Gaza is because you don’t want anyone to document the genocide you are about to accelerate.

Any politician, Democrat or MAGA or Independent, any journalist, liberal or conservative, who cannot call this genocide for what it is, is complicit, and I hope history remembers you as such.

It turns out that there's a problem when you want to run everything in the #fediverse.
I guess it's time to purchase a 3rd node ( ^ . ^ ;) ( T _ T )
#kubernetes #keyboardvagabond #outofmemory #dudewheresmyram.

Today's #adventuresInSelfHosting, I was having trouble with #cloudnativePG where I'd always have n-1 pods stable and they'd constantly restart between the replicas in a massive loop, then eventually switch with the primary and continue the process. So, I set the instance count to 3 so there'd at least be one stable read replica at a time.

I finally found out what was wrong. I have my #cnpg cluster in the postgresql-system namespace and I happened to see that I had an operator running in the default cnpg-system namespace. I don't know how long it had been there, so both it and the one in my namespace were both competing for the state. Deleting and cleaning up that old cluster brought immediate stability.

I also realized that I wasn't overriding the default #php configuration for #pixelfed, so when I uploaded an image taking on my phone, the web server would restart. I bumped the php memory up to 1GB for now. For the expected userbase for the upcoming #keyboardvagabond #fediverse space, this should be fine.

Right now the services are running well, but I need to do more testing and get mastodon into an "interesting" state for new visitors. Pixelfed seems the hardest for me in terms of getting content onto the server so that it doesn't look barren.

The todo list for now is:

  • comprehensive testing
  • get hcaptcha working on all services, or find an alternative
  • add the community block list to pixelfed
  • make pixelfed look interesting (any tips would be greatly appreciated!)
  • get bookwyrm running
  • create an intro landing website for www subdomain
  • get the #soonTM mascot in there! I'm super excited for what comes out of that
  • set up mastodon SSO/OAuth

It's getting close! The services are essentially ready, just not necessarily turned on for signups until I'm ready for a pre-launch or full launch. I want to make sure things are in a good state.

But with the 2 node #kubernetes #cluster, I think things should be good!
By then end, it should look like:

Just uploaded 4 new photos to my Flickr page: https://www.flickr.com/photos/stillugly/54712428666/ taken around Washington state. #photography
Satsop Nuclear Plant 2025 06 12 01

Flickr
Reality