sigmoid.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A social space for people researching, working with, or just interested in AI!

Server stats:

591
active users

#cdn

1 post1 participant0 posts today
:rss: Hacker News<p>Crafting your own Static Site Generator using Phoenix (2023)<br><a href="https://fly.io/phoenix-files/crafting-your-own-static-site-generator-using-phoenix/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">fly.io/phoenix-files/crafting-</span><span class="invisible">your-own-static-site-generator-using-phoenix/</span></a><br><a href="https://rss-mstdn.studiofreesia.com/tags/ycombinator" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ycombinator</span></a> <a href="https://rss-mstdn.studiofreesia.com/tags/fly" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>fly</span></a> <a href="https://rss-mstdn.studiofreesia.com/tags/fly_io" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>fly_io</span></a> <a href="https://rss-mstdn.studiofreesia.com/tags/blog" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>blog</span></a> <a href="https://rss-mstdn.studiofreesia.com/tags/elixir" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>elixir</span></a> <a href="https://rss-mstdn.studiofreesia.com/tags/docker" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>docker</span></a> <a href="https://rss-mstdn.studiofreesia.com/tags/cdn" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>cdn</span></a> <a href="https://rss-mstdn.studiofreesia.com/tags/hosting" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>hosting</span></a> <a href="https://rss-mstdn.studiofreesia.com/tags/servers" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>servers</span></a> <a href="https://rss-mstdn.studiofreesia.com/tags/networking" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>networking</span></a> <a href="https://rss-mstdn.studiofreesia.com/tags/deploy_app_servers" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>deploy_app_servers</span></a> <a href="https://rss-mstdn.studiofreesia.com/tags/close_to_users" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>close_to_users</span></a> <a href="https://rss-mstdn.studiofreesia.com/tags/postgresql_clusters" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>postgresql_clusters</span></a> <a href="https://rss-mstdn.studiofreesia.com/tags/heroku_competitor" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>heroku_competitor</span></a> <a href="https://rss-mstdn.studiofreesia.com/tags/heroku_alternative" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>heroku_alternative</span></a></p>
Marcel SIneM(S)US<p><a href="https://social.tchncs.de/tags/Cloudflare" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Cloudflare</span></a> vs. KI-Bots: "Die Menschheit braucht vom Menschen gemachte Inhalte" | heise online <a href="https://www.heise.de/hintergrund/Cloudflare-vs-KI-Bots-Die-Menschheit-braucht-vom-Menschen-gemachte-Inhalte-10493072.html" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">heise.de/hintergrund/Cloudflar</span><span class="invisible">e-vs-KI-Bots-Die-Menschheit-braucht-vom-Menschen-gemachte-Inhalte-10493072.html</span></a> <a href="https://social.tchncs.de/tags/ArtificialIntelligence" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ArtificialIntelligence</span></a> <a href="https://social.tchncs.de/tags/ContentDeliveryNetwork" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ContentDeliveryNetwork</span></a> <a href="https://social.tchncs.de/tags/CDN" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CDN</span></a></p>
Elena Rossini on GoToSocial ⁂<p>🏕️ my adventures in <a href="https://aseachange.com/tags/selfhosting" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>selfhosting</span></a> - day 212 (consolidating edition) 🎛<br><br>If you followed my (mis)adventures yesterday and all the issues I had with caching and <a href="https://aseachange.com/tags/cdn" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CDN</span></a> for my <a href="https://aseachange.com/tags/wordpress" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Wordpress</span></a> site, well, I found a solution.<br><br>💫​ Something that had been in front of me the whole time<br>💫​ ZERO additional costs<br><br>Ta-da: 👻​<br><br>🔗​: <a href="https://news.elenarossini.com/my-so-called-sudo-life/my-adventures-in-self-hosting-day-212-consolidating-edition/" rel="nofollow noopener" target="_blank">https://news.elenarossini.com/my-so-called-sudo-life/my-adventures-in-self-hosting-day-212-consolidating-edition/</a><br><br><a href="https://aseachange.com/tags/ghost" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Ghost</span></a> <a href="https://aseachange.com/tags/varnishcache" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>VarnishCache</span></a><br></p>
Miguel Tavares<p>My <a href="https://pkm.social/tags/mastodon" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>mastodon</span></a> <a href="https://pkm.social/tags/instance" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>instance</span></a> (pkm.social) has been having trouble displaying <a href="https://pkm.social/tags/media" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>media</span></a> for me. I’m in <a href="https://pkm.social/tags/Portugal" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Portugal</span></a>; if I connect to a Dutch <a href="https://pkm.social/tags/VPN" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>VPN</span></a> server, most images are shown, but not videos. Instance owner says it’s a <a href="https://pkm.social/tags/CDN" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CDN</span></a> problem.</p><p>I’d like to stay in this instance, but unless there’s a solution or workaround, I can’t.</p><p>Any ideas?</p>
Elena Rossini on GoToSocial ⁂<p>🏕️ my adventures in <a href="https://aseachange.com/tags/selfhosting" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>selfhosting</span></a> - day 211 (CDN edition)🛡️​<br><br>A "micro" blog post detailing recent experiments with my <a href="https://aseachange.com/tags/wordpress" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Wordpress</span></a> blog and efforts to protect it against the Mastodon Hug of Death / stampede:<br><br>🔗​: <a href="https://elenarossini.com/2025/07/my-adventures-in-self-hosting-day-211-cdn-edition/" rel="nofollow noopener" target="_blank">https://elenarossini.com/2025/07/my-adventures-in-self-hosting-day-211-cdn-edition/</a><br><br>Was 🐇​ CDN successful? I'll publish an update soon.<br><br><a href="https://aseachange.com/tags/mysocalledsudolife" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>MySoCalledSudoLife</span></a> <a href="https://aseachange.com/tags/fediverse" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Fediverse</span></a> <a href="https://aseachange.com/tags/wordpress" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Wordpress</span></a> <a href="https://aseachange.com/tags/cdn" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CDN</span></a> <a href="https://aseachange.com/tags/webdev" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>webdev</span></a> <a href="https://aseachange.com/tags/mastodon" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Mastodon</span></a></p>
Elena Rossini<p><a href="https://elenarossini.com/2025/07/my-adventures-in-self-hosting-day-211-cdn-edition/" class="" rel="nofollow noopener" target="_blank">https://elenarossini.com/2025/07/my-adventures-in-self-hosting-day-211-cdn-edition/</a></p><p>My dear federated WordPress blog,</p><p>Sorry for all the tests I put you through in the last 48 hours.</p><p>First, I changed your <a href="https://wordpress.org/plugins/webfinger/" rel="nofollow noopener" target="_blank">Webfinger setup</a>, which broke federation. Then I reverted back those changes… I posted a <a href="https://elenarossini.com/2025/07/testing/" rel="nofollow noopener" target="_blank">test message that immediately federated</a> (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).</p><p>Ever since, I have been on a mission to safeguard you against the <a href="https://news.itsfoss.com/mastodon-link-problem/" rel="nofollow noopener" target="_blank">Mastodon Hug of Death</a> – a very familiar phenomenon that I experienced with my self-hosted Ghost blog. </p><p>The solution I found for it (on <a href="https://news.elenarossini.com" rel="nofollow noopener" target="_blank">Ghost</a>) was installing <a href="https://varnish-cache.org/docs/3.0/tutorial/introduction.html" rel="nofollow noopener" target="_blank">Varnish Cache</a>. 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 <a href="https://news.elenarossini.com/fediverse-video/" rel="nofollow noopener" target="_blank">Fediverse promo video</a>).</p><p>But I’m digressing.</p><p>My dear WordPress blog, you need protection against sudden surges of traffic brought on by the Fediverse.</p><p>This morning, I tried it all:</p><ol><li>My plan A was setting up <a href="https://www.cloudflare.com" rel="nofollow noopener" target="_blank">Cloudflare</a> 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.</li><li>My plan B was exploring how to set up <a href="https://varnish-cache.org/docs/3.0/tutorial/introduction.html" rel="nofollow noopener" target="_blank">Varnish cache</a> 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?</li><li>My plan C was setting up <a href="https://bunny.net" rel="nofollow noopener" target="_blank">BunnyCDN</a> for this site. I first heard about it via the superb website <a href="https://european-alternatives.eu/category/cdn-content-delivery-network" rel="nofollow noopener" target="_blank">European Alternatives</a> (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 <a href="https://wordpress.org/plugins/bunnycdn/" rel="nofollow noopener" target="_blank">WordPress plugin</a>. I connected it to my Bunny account and was good to go – no tinkering with DNS.</li></ol><p>I have double-checked in Developer mode that this site’s images are already going through Bunny. All good!</p><p>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).</p><p>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.</p><p>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).</p><p>Wish me luck!!!</p><p>Elena</p><p>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… </p><p><a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://elenarossini.com/tag/bunnycdn/" target="_blank">#BunnyCDN</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://elenarossini.com/tag/cdn/" target="_blank">#CDN</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://elenarossini.com/tag/cloudflare/" target="_blank">#Cloudflare</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://elenarossini.com/tag/micro/" target="_blank">#micro</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://elenarossini.com/tag/my-adventures-in-self-hosting/" target="_blank">#myAdventuresInSelfHosting</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://elenarossini.com/tag/my-so-called-sudo-life/" target="_blank">#mySoCalledSudoLife</a></p>
panigrc<p><span class="h-card" translate="no"><a href="https://tech.lgbt/@ck0" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>ck0</span></a></span> <span class="h-card" translate="no"><a href="https://aseachange.com/@elena" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>elena</span></a></span> most small websites don't need a <a href="https://mastodon.social/tags/cdn" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>cdn</span></a><br>Use caching and compressed images.<br>Using the latest <a href="https://mastodon.social/tags/PHP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>PHP</span></a> version would help as well.</p>

Never a dull day in this #selfhosting journey: editing important #DNS records while your child is on summer holiday - and may come see you every few minutes - is a very interesting exercise in concentration.

Special thanks to nonna (grandma) for helping with childcare this morning 😅

I'm hoping I'm successful in setting up a more solid #CDN for my personal website because I keep DDOS'ing myself (from a simple Mastodon reply to a federated Wordpress post - 8k followers will do that).

Wish me luck!

P.S.: another moment of gratitude / deep appreciation for #VarnishCache which has been providing rock solid caching to my #Ghost site. Now I need to take care of my #Wordpress site with a pro CDN solution (Varnish isn't an option sadly bc of the Wordpress setup / I don't have direct access to the server)

Someone mentioned using #BunnyNet as a CDN on here (I wish I remembered to get a referral code from them... they shoulda gotten some credit).

I moved my only serious web site to it. What's interesting to look at is how much visibility I got over traffic, and then how it gave me the ability to fight off the bots. There's a story in this graph.

On the 11th I switched over. You can see this huge spike in green 4XX traffic. Some bot out of Singapore hammered the site overnight. I got up and turned on bot detection, but it was in detect only mode. So you can see the yellow line at the bottom (5XX errors) and the green line still quite high. These bots trigger a lot of errors (possibly intentionally).

There's a mysterious 2-hour window yesterday where it seems I did no traffic at all. I don't think it was -that- bad, but I was definitely messing with stuff.

Finally I put the bot detection into "challenge" mode. The 5XXs have basically stopped, and the 4XXs represent (I think) failed challenges, plus the inevitable bots looking for wp-login.php and various attack probes. So far, I'm quite happy with it. I've pretty much moved all my websites to it, though everything else adds up to basically nothing. 😃

I also added the overall traffic graph to show the normal traffic for comparison. And I included some graphs of the VM's performance over roughly the same time period.

And of course, if you want to give it a go, here's my referral link. (I'm gonna have to figure out who I saw mention it and just paypal them some cash or something)

bunny.net?ref=otfq1cq96c

Während ich mir die Performancergebnisse zu meinem metalhead.club CDN angesehen habe, ist mir aufgefallen, dass die Namensauflösung einen beträchtlichen Teil der Ladezeit für internationale User ausgemacht hat.

Woran lag's? An CNAMES!

Wieso CNAMES problematisch sein können, erfahrt ihr in diesem zweiten Blogpost, den ich während meiner Arbeiten am CDN geschrieben habe:

"Globale DNS-Auflösung durch Verzicht auf CNAMES beschleunigen" -
thomas-leister.de/globale-dns-

Seit einigen Tagen werden Medien meiner Mastodon-Instanz metalhead.club global verteilt über ein eigenes CDN ausgeliefert. :goose_hacker:

Das verringert die Latenzen für Benutzer aus nicht-EU Ländern und sorgt für weniger Frust bei den Ladezeiten.

Was ein CDN ist, welche Implementierungsmethoden es gibt und wie ich mein kleines CDN umgesetzt habe, erfahrt ihr in meinem neuen Blogpost:

"Ein eigenes kleines CDN für meine Mastodon-Instanz metalhead.club" - thomas-leister.de/mastodon-med

I keep seeing governments treat DNS resolvers like censorship tools. Obviously, they’re not meant to be.

Blocking at the DNS level is imprecise and doesn’t remove bad actors. It’s like trying to fix a leaky faucet with a sledgehammer.

Now they're going even further, pressuring CDNs like cloudflare to block access to piracy or malicious content. But here's the catch: CDNs serve thousands of sites from shared infrastructure. One misfire, and you can literally break half the web.

Just looking at what happened in Spain with La Liga is a perfect example of how not to fight piracy. To block access to illegal streams of soccer matches, La Liga pushed for CDN-level blocking.

Instead of just stopping shady streams, the blocks affected entire domains. Legit websites went offline. Entire CDNs were caught in the crossfire, news outlets, small businesses, hobby sites. All because they happened to sit on the same servers/ips as of flagged URLs.

For instance, none of them are discussing reducing ticket fees, so normal people can take their family to a stadium, or even streaming subscription costs. It's a shame.

#DNSBlocking
#CDN
#InternetFreedom