eupolicy.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
This Mastodon server is a friendly and respectful discussion space for people working in areas related to EU policy. When you request to create an account, please tell us something about you.

Server stats:

205
active users

#micro

9 posts1 participant0 posts today

As you can see in this photograph a level of stability has been reached in the installation and configuration of this 64bit SBC.

The configuration that was chosen by the maintainers of the Pi distro is one, where Super User needs to be run at any time, for root commands, because access to the root account has been disabled by default.

Security wise the SBC is fair provided that you do not allow others to get close to it in a physical plane.

I already have two installations one is on a microSD card the other is on a USB stick

It is important to realize that when you boot from the USB stick your USB-C power supply needs to be able to produce 5,000 milliamps, at 5V DC otherwise there will not be enough current for that control to be smooth.

Note:
The second display that you see does not belong to the control of the Raspberry Pi.
I need to get myself a second longer microHDMI to HDMI cable to reach the other IPS LED panel

I've done the first steps to get my SBC in the bootstrap.

Before bootstrapping the machine I first oriented myself to what I got. I photographed everything and I was amazed at the Simplicity of the GPIO. I love the fact that this SBC was actually produced in Great Britain. I dislike the fact that I could not get the 16 GB one because those ste still not produced in proper volumes

I love the fact that the system is now 64 bits.

The first step was easy just take the USB-C power supply and fire it up.

Since I have a very nice set of possibilities in USB-C to power the Pi up, I just chose one of them. No video output was needed. The machine has a combo LED which goes from Red to Green and I also have a Pi case which has a nice cooling fan for the CPU. When power is applied to the system the LED goes from Red to Green and the fan starts running about 2 seconds afterwards.

Today I took a couple of other steps. I connected a UTP network cable to the machine, which is mapped to one of my routing systems.
Then I got at least one micro HDMI output working. That was an easy step, I just need to to buy a micro HDMI to HDMI cable, USD 12 for 90cm length of cable.

With just Power Connected to my USB-C multi device which has a Power pass through, and my HDMI port 0 chained to one of my IPS LED displays, I fired up the machine again. I got a nice Little logo and I got a diagnostic screen telling me what is connected to the SBC.

When I connected a USB keyboard a very nice Splash appeared at the next boot. I was then also invited to connect the UTP cable so that the machine itself could get an image of the Operating System and write that to the micro SD card that I had inserted also.

The look is quite polished very nice and very easy. Of course I pressed Escape so that I could see the diagnostic screen again but you understand that.

After that I purchased some internet bandwidth so that I could do an actual installation.

Then I read on the Raspberry Pi website that Debian is used as the main operating system. That is from me very very nice because I just love anything Debian when it comes down to Linux.

Currently I'm at the step where I have already written the image, not the microSD card but a USB Stick which has ventoy running the imaging show. I will stick into one of the USB 3 ports on the machine and then do another post.

There's one snafu

My Ventoy is compiled for X86, the Raspberry Pi is an ARM system. It shall not be able to boot the Ventoy image manager.
So all I will be able to see, is that the machine actually seeks the USB stick, it recognizes the stick and then the post will stop.

I have the Raspberry Pi imaging software for Linux x86 which can write to a stick but it wants to WIPE the WHOLE stick.

This means I will have to take my small 16 gig stick, back up the data, and then wipe it just to see that my single board computer starts and then install the operating system on the MicroSD card that I have for it

This is my current plan van aanpak NL

https://elenarossini.com/2025/07/my-adventures-in-self-hosting-day-211-cdn-edition/

My dear federated WordPress blog,

Sorry for all the tests I put you through in the last 48 hours.

First, I changed your Webfinger setup, which broke federation. Then I reverted back those changes… I posted a test message that immediately federated (yay) but when I replied to it from my Mastodon account, I set off the infamous Mastodon stampede: 5000+ requests in the span of seconds, which took you offline (ouch). I had to delete my reply on Mastodon, flush your cache, and you were back online (yay).

Ever since, I have been on a mission to safeguard you against the Mastodon Hug of Death – a very familiar phenomenon that I experienced with my self-hosted Ghost blog.

The solution I found for it (on Ghost) was installing Varnish Cache. And my oh my has it been effective! A real champion, even at times when my blog posts trended all day on Mastodon (like the one announcing the release of my Fediverse promo video).

But I’m digressing.

My dear WordPress blog, you need protection against sudden surges of traffic brought on by the Fediverse.

This morning, I tried it all:

  1. My plan A was setting up Cloudflare for you. I am SO GLAD that didn’t work out, though, because in the past year I have developed a real distaste for all things Big Tech and I couldn’t really reconcile using Cloudflare as your Content Delivery Network. Why this didn’t work out? It’s a very convoluted explanation… it had to do with DNS records and the way it’s set up. Basically if I manually connected Cloudflare to some DNS records for elenarossini.com, this association would take over ALL DNS records from the POV of my hosting provider, including subdomains… even if I didn’t add them. And I have LOTS of subdomains linked to self-hosted instances for Fediverse software and did not want to do that. I’m probably explaining things badly, but suffice it to say, it wasn’t ideal to tinker with DNS for a variety of reasons. Moving on.
  2. My plan B was exploring how to set up Varnish cache for this website by using shell access. That, unfortunately, is impossible: Varnish needs Nginx or Apache and on a shared hosting plan you simply cannot tinker with that stuff. What to do?
  3. My plan C was setting up BunnyCDN for this site. I first heard about it via the superb website European Alternatives (basically, a database of alternatives to Big Tech platforms and services from the US). Bunny is based in Slovenia and I heard praises of it. Now, I had tried to use it for Ghost earlier this spring, but never managed to complete its setup, and opted for Varnish instead. I decided to give it another go. Guess what? Bunny didn’t ask me for DNS records – its setup was easy and instantaneous, with its native WordPress plugin. I connected it to my Bunny account and was good to go – no tinkering with DNS.

I have double-checked in Developer mode that this site’s images are already going through Bunny. All good!

Disclaimer: unlike Cloudflare, Bunny doesn’t offer a free plan, so I will need to monitor costs. But I’m curious to see how it will do and how much it will cost on a monthly basis. Of course, I will report back about this (at the moment I have $50 in free credits).

Now the real test will be hitting “publish” on this blog post… and replying to the federated post with my Mastodon account. This simple action took my site offline yesterday.

If the site doesn’t go offline, I would up the ante and actually share the link to this blog post from my Mastodon account (to an audience of 8000+ people on hundreds of different servers).

Wish me luck!!!

Elena

Update: how did the test go? Well, the post federated and appeared immediately on my Mastodon feed. I replied to it and within seconds the site went offline, showing an “error establishing a database connection.” I refreshed the page and saw the homepage – fully functional, but extremely slow. If I tried to click on any items in the navigation menu, nothing happened. I deleted the Mastodon reply, flushed the cache… and the site remained largely unresponsive. Needless to say, I need to conduct more tests with Bunny. I am not giving up quite yet…

Elena Rossini · My adventures in self-hosting: day 211 (CDN edition) — Elena Rossini
More from Elena Rossini

https://elenarossini.com/2025/07/my-adventures-in-self-hosting-day-210-viva-foss/

There has never been a better time to join the world of Free Open Source Software or begin self-hosting essential digital services.

Some recent news that made me feel grateful for my forays into self-hosting:

  1. The software Pocket, which made it easy to save, organize and read later articles in a really elegant interface shuts down this year. Another fantastic app/service to add to Mozilla‘s graveyard. Looking at YunoHost‘s app catalog, I noticed several superb alternatives to Pocket that are free, open source, and can be self-hosted, so I am thinking: never again will I give that power to an outside company. Cherry on top: the Pocket archive I requested the other day landed in my email… and the file contains an error, so I cannot download it (expired token even if it didn’t pass the 72 hour threshold they set). I look forward to self-hosting my next “save and read later” bookmark service.
  2. The file sharing company WeTransfer was in the news this morning because they recently updated their terms of service, with alarming language, telling users: “You hereby grant us a perpetual, worldwide, non-exclusive, royalty-free, transferable, sub-licensable license to use your Content for the purposes of operating, developing, commercializing, and improving the Service or new technologies or services. Such license includes the right to reproduce, distribute, modify, prepare derivative works based upon, broadcast, communicate to the public, publicly display, and perform Content. You will not be entitled to compensation for any use of Content by us under these terms.” News about this spread like wildfire with people saying this language implies content shared via WeTransfer would be used to train AI models. Now, why is this a big deal you may wonder? In my filmmaking / film editing days I would use WeTransfer DAILY to share cuts of my projects. WeTransfer is THE file sharing app for most creatives and film professionals. I used it extensively in May and June to share versions of the Fediverse promo video with my interns. Well, even if WeTransfer backtracks following the backlash, I would never again consider using it. It’s a happy coincidence that last month I set up my own NextCloud instance and I plan on using it to share files from now on. Excellent timing.
  3. Tangentially-related, but an article in Engadget today revealed that users of the microblogging platform Threads rarely click on external links. The numbers are pretty shocking: 28 million referral links in 30 days for a platform with allegedly 350 million monthly active users. This is precisely why I love the Fediverse: external links are never downranked because there are no algorithms. Writers and content creators have far higher engagement with their audience because of chronological feeds and more genuine relationships.

On my to do list for the fall: looking into taking full advantage of NextCloud‘s ecosystem because this software is incredibly sophisticated… the FOSS equivalent of a Swiss Army knife.

For those curious about it, here is their official website with documentation: https://nextcloud.com

Onwards and upwards!

Elena

Elena Rossini · My adventures in self-hosting: day 210 (viva FOSS!) — Elena Rossini
More from Elena Rossini

https://elenarossini.com/2025/07/my-adventures-in-self-hosting-day-204-experimenting-with-wordpress-edition/

Hello Fedi friends,

Yesterday I started posting #MySoCalledSudoLife messages on my WordPress site (aka here) so that it will be easier to find and organize them in the future. Having them live on my GoToSocial account started to feel counterproductive… as search in the Fediverse is still hard to do.

So far so good!

The script I mentioned in yesterday’s post did its job – so these “micro blogs” do not show up on my main blog feed, but are in a category of their own.

This is what “My So-Called Sudo Life” blog category looks like right now:

a screenshot showing how my website displays “my so-called-sudo life” blog posts in a masonry grid

I just installed Alex Kirk‘s plugin Enable Mastodon Apps for WordPress – which means that I was able to log onto my federated WordPress site… in the app Ivory for iOS!

It’s amazing to see all my blog posts in Ivory’s feed… and to think I can interact with readers there.

Now a little hiccup I’m experiencing in Ivory is that I’m not able to follow other Fediverse accounts for some reason; I keep getting a “server failure” error but I wonder if it’s a problem on my end with the security settings I have in place. Up next: logging onto my WP account in Phanpy.social and the app Mona for iOS for further testing. I will report back tomorrow about how it went.

It’s exciting to think I could turn my WordPress blog into a social hub. Thank you for this @alex !

If you’re seeing this post in your Fediverse feed, I have a favor to ask: can you please add a quick comment, so I can test if I can reply from Ivory / Phanpy or Mona? And follow you from there? Thank you!

Onwards and upwards!

Elena

P.S.: for all my social links, check out: elena.social

https://elenarossini.com/2025/07/my-adventures-in-self-hosting-day-203/

Hello Fedi friends!

I’m currently experimenting with the POSSE method of publishing (“Publish [on your] Own Site, Syndicate Elsewhere”) on my federated WordPress site (this one) so that I can more easily organize posts and retrieve them in the future. This is the first of such posts.

I have created a “micro” post category and edited the functions.php file of my WordPress blog to exclude such posts from the main blog.

Here is the code I’m using:

function exclude_category( $query ) {
if ( $query->is_home() && $query->is_main_query() ) {
$query->set( ‘cat’, ‘-2132’ );
}
}
add_action( ‘pre_get_posts’, ‘exclude_category’ );

Where -2132 is the number assigned to the category “micro”.

You can find the category number by hovering over it in the Categories menu.

I also plan to tweak my site’s navigation menu to make “micro” appear under the blog category.

At some point in the future that will replace the “blog”… otherwise it’s too confusing to follow how many blogs I actually have.

I am also debating whether to migrate my GoToSocial account to WordPress using the MOVE function. What’s holding me back for now? I will need to be able to implement Serdy’s blocklists here before I do that. I experienced some terrible trolling and abusive messages when I didn’t have blocklists in place on my GoToSocial account last month, so I learned my lesson.

And I’d like to see how “social” the Friends for WordPress plugin by Alex Kirk is, before I consolidate my two accounts.

Anyway, this is all really exciting, made possible by the magic of #ActivityPub and the ActivityPub for WordPress plugin by @pfefferle. Thank you Matthias!

Onwards and upwards!

#MySoCalledSudoLife

Elena Rossini · My adventures in self-hosting: day 203 — Elena Rossini
More from Elena Rossini