RE: https://zdf.social/@ZDF/116601776009447156

Hey @ZDF ich haette da mal ne ganz pragmatische Loesung: anstatt eure Inhalte nur in den Mediatheken und auf Youtube zu veroeffentlichen:

a) #RSS

b) #Peertube

Das waere gemeinwohl-orientiert und ihr schafft damit einen digitalen Raum als Alternative zu kommerziellen Plattformen.

So und nun duerft ihr mir fuer dieses Hauruck-Consulting ein Monatsgehalt vom Erik ueberweisen, das ich dann an die UN-Fluechtlinghilfe spende!

#Fediverse

🛡️ #Cybersecurity news & tips across the #fediverse

“Related to the above: The Android app Nearby Glasses scans for the Bluetooth ID of Smart glasses and warns you when they're close. Available from Fdroid:
https:// apt.izzysoft.de/packages/ch.po cketpc.nearbyglasses...”

https://helvede.net/@fanden/116600365605130951

🤖 via RSS feed. Not an endorsement.

🛡️ #Cybersecurity news & tips across the #fediverse

“Disney Hit With Class Action Over Facial Recognition Technology at Park Entrances
# surveillance https://www. hollywoodreporter.com/business /business-news/disney-class-action-lawsuit-facial-recognition-disneyl...”

https://social.vivaldi.net/@rogerc2738/116598964911782261

🤖 via RSS feed. Not an endorsement.

🛡️ #Cybersecurity news & tips across the #fediverse

“Person of Interest is about # Surveillance , # BigData , *AND* # AlgorithmicInference ( # AI ). There's no story without those three elements in equal proportion. Without widespread (1. surveillance there isn't...”

https://mstdn.social/@ricardoharvin/116598249179670854

🤖 via RSS feed. Not an endorsement.

🛡️ #Cybersecurity news & tips across the #fediverse

“Oh joy, the # FBI wants to play Big Brother with a shopping spree for license plate readers. 🚓🔍 Apparently, they've decided that # privacy is so 2025 and have taken a liking to tracking our every move. Maybe next...”

https://mastodon.social/@ngate/116597554160940676

🤖 via RSS feed. Not an endorsement.

Did you know there is a #SelfHosted #Fediverse-enabled trails and hiking service?
I was very excited to discover #Wanderer last week and am about to host it as part of #GlitchySocial.

Currently, I'm trying to host OSM #Valhalla for my #Wanderer instance. To build the required data for the #Ukraine region, to be precise. The process got killed twice already, but I'm not giving up yet )

#homelab #selfhost #selfhosting

🛡️ #Cybersecurity news & tips across the #fediverse

“"The # FBI 🚨🚨🚨 says it wants to buy nationwide access to license plate readers. This would likely mean🚨
the FBI could track vehicles, and by extension people, without a warrant. FBI offering $36M. Only really two...”

https://toad.social/@KimPerales/116597022592536499

🤖 via RSS feed. Not an endorsement.

🛡️ #Cybersecurity news & tips across the #fediverse

“"Big tech is everywhere, it is the world that has been pulled over your eyes to blind you from the truth." Oops, sorry.. that's not "big tech" but is "The Matrix". Oh.. wait... # bigtech # deception # masssurv...”

https://mastodon.world/@ami/116596886026524385

🤖 via RSS feed. Not an endorsement.

🛡️ #Cybersecurity news & tips across the #fediverse

“1984 x Barbie 💗 for #minimalismmonday

Surveillance - but make it aesthetic 💅🏻✨

(This is just a shop CCTV - but we should all be worried about the normalisation and aestheticisation of surveillance 👀 📸)

...”

https://pixelfed.social/p/NotAHopeInHades/962037985277099956

🤖 via RSS feed. Not an endorsement.

🛡️ #Cybersecurity news & tips across the #fediverse

“King and Queen’s Royal Ascot procession facing challenges from 'biggest equine flu outbreak in recent history'

https:// web.brid.gy/r/https://www.mirr or.co.uk/sport/horse-racing/royal-ascot-procession-equine-flu...”

https://web.brid.gy/r/https://www.mirror.co.uk/sport/horse-racing/royal-ascot-procession-equine-flu-37173047

🤖 via RSS feed. Not an endorsement.

🛡️ #Cybersecurity news & tips across the #fediverse

“https:// youtu.be/v9Vb3hTxdP4?si=YkHt8X iUuV-zY3Hx Mostly of interest to Americans, but not exclusively. # privacy # CyberSecurity # usa # SurveillanceCapitalism # activism # activist # surveilla...”

https://mstdn.ca/@theyycmonk/116595824382923355

🤖 via RSS feed. Not an endorsement.

🔆 #FediTips for https://PrivacySafe.Social & the #fediverse

“Do you want to remove some of your followers without blocking them? There is a follower management system in Mastodon that lets you do this, here's a guide to how to use it: ➡️ https:// fedi.tips/how-do-i-remove-foll...”

https://social.growyourown.services/@FediTips/116597369663765610

🤖 via RSS feed. Your Mileage May Vary.

🛡️ #Cybersecurity news & tips across the #fediverse

“# scrum # scrumteam # dev # developer # qa # scrummaster # productowner # surveillance # surveillancesoftware # Meme # memes # Humor # humour”

https://techhub.social/@FakeScrumStats/116594587765362921

🤖 via RSS feed. Not an endorsement.

Wir haben beschlossen, aus meinem alten Podcast-Kanal "Marmor, Stein & Kopfsalat", einen Unter-Videokanal innerhalb von gabi&matthias zu machen.

In dieser ersten Ausgabe erzähle ich, was wir dort so vorhaben.

Die Themen entnehmt ihr einfach den unten stehenden Hashtags :)

Zu erreichen hier:
https://peertube.lebenswert.social/w/2sutVPUhDysRWiGkFgjY9V

Und wer noch auf Werbung, Algorithmen und Überwachung steht:
https://youtu.be/vEz1YBKYlOk?is=VCFIeUj-F0cSHT-m

#linux #fediverse #WindowsToLinux #mastodon #friendica #peertube #BigTech

🛡️ #Cybersecurity news & tips across the #fediverse

“Input your license plate to see if Flock cameras have scanned your car. https:// haveibeenflocked.com/ # Surveillance # Flock # Spying # Licenseplate”

https://kolektiva.social/@MHowell/116592599270306444

🤖 via RSS feed. Not an endorsement.

Pasta, 100 cloves of garlic, olive oil, and parmesan.

Slow-cook the garlic in oil, mash it, mix with parmesan until creamy, then coat the pasta in that garlic-cheese madness.

It tastes absolutely amazing.

But I’m pretty sure Dracula just left the planet. 🧄🧛‍♂️🚀

#Food #Pasta #Garlic #Cooking #Fediverse

Kennt ihr eigentlich schon #ZDFmitreden? Beteiligt euch über unsere Umfragen an gesellschaftlichen Debatten und gestaltet Programminhalte mit. Die nächste Umfrage wird sich auch mit dem Thema #Fediverse beschäftigen.
Link zur Registrierung: https://www.mitreden.zdf.de/h/s/6oQVcslmnPT1M5yoglLx4Y

#ZDF #3sat #Gemeinschaftsprogramm #Öffiverse #SocialMedia @ZDF

Alt...

Weiße Sprechblase vor türkisfarbenem Hintergrund. Auf der Sprechblase ist rechts das ZDF-Logo zu sehen und mittig steht: mitreden - Deine Meinung zählt. Oben links das 3sat-Logo.

RE: https://zdf.social/@3sat/116594285076724242

Ihr habt das schon gesehen? Nein? Dann jetzt (und teilt mal diesen Link eifrig)!
#fediverse #mastodon

AodeRelay boosted

3sat » 🌐 2026-05-18
@3sat@zdf.social

Kennt ihr eigentlich schon #ZDFmitreden? Beteiligt euch über unsere Umfragen an gesellschaftlichen Debatten und gestaltet Programminhalte mit. Die nächste Umfrage wird sich auch mit dem Thema #Fediverse beschäftigen.
Link zur Registrierung: https://www.mitreden.zdf.de/h/s/6oQVcslmnPT1M5yoglLx4Y

#ZDF #3sat #Gemeinschaftsprogramm #Öffiverse #SocialMedia @ZDF

Alt...

Weiße Sprechblase vor türkisfarbenem Hintergrund. Auf der Sprechblase ist rechts das ZDF-Logo zu sehen und mittig steht: mitreden - Deine Meinung zählt. Oben links das 3sat-Logo.

• #offiverse

Taking a trip back to the mid 2000s with my last media player before switching to a smartphone.

I tried to flash mod it by replacing the old spinning IDE hard drive with an SD card. It was a bit of a disaster, but we still explore the classic software interface and test how video and audio playback fares today.

Watch on PeerTube: https://tube.devwithzachary.com/w/obPPPUPa6ippC3MMqJdM3g
Or on YouTube: https://youtu.be/X_rzqGQ8d4w

#RetroTech #CreativeZen #HardwareHacking #PeerTube #Fediverse #TechRestoration #VintageTech

🛡️ #Cybersecurity news & tips across the #fediverse

“I don't have (nor would I recommend) doorbell cameras from Ring, blink, etc. I personally use a Reolink PoE doorbell camera that connects to a recorder locally and does not interact with the internet what so ever. If p...”

https://defcon.social/@Modus_Operandi/116591888671703097

🤖 via RSS feed. Not an endorsement.

🛡️ #Cybersecurity news & tips across the #fediverse

“🔍🛠️ It seems Americans have discovered their true calling: amateur demolition experts specializing in Flock cameras. Who knew that "disruptive innovation" meant taking a # sledgehammer to the # surveillance state...”

https://mastodon.social/@ngate/116591043046636425

🤖 via RSS feed. Not an endorsement.

🛡️ #Cybersecurity news & tips across the #fediverse

“@ h4ckernews I feel e x t r e m e l y ​ ​ s t r o n g ​ ​ c o n t e m p t towards the EU Brussels regime when I am reading that EU calls VPNs "a loophole that needs closing". # contempt # eu # brussels ...”

https://net.miaumuh.ch/@clock/116590930961161041

🤖 via RSS feed. Not an endorsement.

🛡️ #Cybersecurity news & tips across the #fediverse

“#^ Becoming Invisible, Part 19: You Only Think You Own Your Car



Modern vehicles had already become “rolling surveillance devices” by the beginning of this decade. But that’s just the start. Much more dystopia...”

https://hub.farthinghalearms.com/item/e7bcaecd-bb42-4d46-8b2b-2ed0990b1cab

🤖 via RSS feed. Not an endorsement.

A pleasant technical read this has been

The notes have been absorbed

@itnotes

#Programming #BSD #snac #Proxy #networking #rules #FediVerse #wisdom #KISS

🛡️ #Cybersecurity news & tips across the #fediverse

“@ shaedrich I feel e x t r e m e l y s t r o n g c o n t e m p t towards the US regime when I am seeing this # privacy # facialrecognition # us # regime # dystopia # surveillance # spying ...”

https://net.miaumuh.ch/@clock/116590907186482926

🤖 via RSS feed. Not an endorsement.

When I wrote about FediMeteo (https://it-notes.dragas.net/2025/02/26/fedimeteo-how-a-tiny-freebsd-vps-became-a-global-weather-service-for-thousands/) for the first time, I told the story from the beginning: the idea born almost by chance while checking the weather for a holiday, the memory of my grandfather, who for years had been my personal meteorologist, the decision to build something small and useful, and then the surprise of seeing people actually use it. What began as a personal experiment quickly became a small global service, still running with the same philosophy: FreeBSD, jails, simple scripts, snac, text, emoji, and a lot of small pieces doing their work quietly.

That article was mostly about the birth and growth of the project. This one is about one of the less romantic parts of the same story, although I have to admit that I find a certain beauty in it too: keeping the service light as it grows.

FediMeteo (https://fedimeteo.com) is still intentionally simple from the outside. A homepage, some numbers, a list of countries, and many ActivityPub accounts publishing weather forecasts. The posts are text and emoji. There is no JavaScript requirement to read the pages, no heavy frontend, no unnecessary media attached to every forecast, and no dynamic homepage recalculated at every visit just to show the same numbers. This is not accidental. It is the way I wanted the service to behave from the beginning.

But the more the service is used, the more the small details matter. A request that looks harmless when there are ten followers may become a repeated request when there are thousands of followers, remote instances, crawlers, previews, and other servers fetching the same public objects. In the Fediverse, the same small thing can be asked many times by many different places, each one with a perfectly legitimate reason. The backend doesn't care: it just needs to deal with the requests.

And in FediMeteo, the backend is snac (https://codeberg.org/grunfink/snac2).

I like snac very much precisely because it is small, clear, and efficient. It is not a giant application that tries to be everything. It does a focused job and does it well. But this also means that I want to respect its shape. I do not want to waste its threads on work that the reverse proxy can safely do. A snac thread serving the same public avatar again and again is not a tragedy, but it is still a waste. A snac thread answering the same public ActivityPub object several times in the same minute is doing real work, but often not necessary work.

This is the reason behind the HAProxy (https://www.haproxy.org) tuning I am currently using in front of FediMeteo.

It is not about making the configuration look clever. It is about keeping snac quiet.

A continuation of the same idea

This is especially important because snac uses a limited number of threads. I like that. Limits are healthy. They force us to understand what the service is doing, and they prevent a small program from pretending to be an infinite resource. But limits also make waste visible. If a few threads are busy serving files that could have been served from cache, those threads are not available for something more useful.

With FediMeteo the implementation is different because the reverse proxy is HAProxy, but the reasoning is the same. I have many small snac instances, each one in its own FreeBSD (Bastille (https://github.com/BastilleBSD/bastille)) jail, and one public entry point that has to route, terminate TLS, compress, cache, and generally remove as much repetitive work as possible from the backends.

This is, in a way, the natural continuation of the original FediMeteo design. In the first article I wrote that I wanted to manage everything according to the Unix philosophy: small pieces working together. This is another piece of that same puzzle. HAProxy does the edge work. snac does the ActivityPub work. Scripts generate forecasts. cron launches updates. ZFS gives me snapshots. FreeBSD jails keep countries separated. Nothing is particularly heroic by itself, but the whole system becomes pleasant because each part has a clear responsibility.

Why there is almost no media

FediMeteo does not use media in its forecasts.

No images attached to the posts, no generated weather cards, no maps for each city, no decorative banners. The forecasts are text and emoji. This was a deliberate decision. Weather information does not become more useful just because it is put inside an image, and every media file used by the service would become something to store, serve, cache, federate, expire, back up, and occasionally debug.

Text and emoji are enough. They are accessible, light, readable in text browsers, friendly to timelines, and understandable even when someone does not know the local language perfectly. This was one of the original design principles of FediMeteo, and it also helps the infrastructure. Less media means less work, fewer cache entries, fewer repeated fetches, fewer surprises.

There is one exception: the avatar.

All FediMeteo accounts use the same avatar, and this is also intentional. I could have used a different avatar for each country, or for each city, or created something visually richer. It would have been nicer in some screenshots, perhaps. It would also have been operationally worse.

With one shared avatar, the reverse proxy has one very useful object to cache. It is public, identical for everyone, small, requested often, and therefore almost always hot in cache. HAProxy can serve it directly instead of asking each snac instance to return the same file. Since avatars are requested by remote instances, browsers, profile previews, and all sorts of federation-related fetches, this single decision removes a surprising amount of pointless backend traffic.

So the avatar is not only a visual identity. It is part of the architecture.

This is the kind of optimization I like most, because it starts before the software. It starts with deciding not to create a problem.

The homepage is static because it can be static

It is a static HTML page generated from a template. Once per hour, a cron script updates the numbers and statistics. It counts the data I want to show, regenerates the page, and then the page remains static until the next run.

This is not because I cannot make a dynamic page. It is because I do not need one. Boring is good.

The homepage does not need to query all the country instances on every visit. It does not need a database request for each user who opens it. It does not need to ask snac anything in real time. The numbers are useful, but they do not need to be updated every second. Once per hour is enough, and it also fits the spirit of the whole project: do the work when it is needed, then serve the result cheaply.

I have seen too many small services become heavy because the first implementation was convenient rather than appropriate. A cron job and a template are not fashionable, but they are often exactly what a page like this needs.

Many countries, one entry point

fedimeteo.com
www.fedimeteo.com
it.fedimeteo.com
uk.fedimeteo.com
jp.fedimeteo.com
us.fedimeteo.com
usa.fedimeteo.com
can.fedimeteo.com
canada.fedimeteo.com

At the beginning, it is always tempting to write one ACL after another in the HAProxy frontend. It is quick, it is explicit, and for five hostnames it is perfectly fine. But FediMeteo did not remain at five hostnames. As countries and aliases grew, a long chain of ACLs would have turned the frontend into a list of names instead of a description of how the proxy behaves.

So I moved the hostname to backend mapping into a map file:

fedimeteo.com        backend_fedimeteo
www.fedimeteo.com    backend_fedimeteo
it.fedimeteo.com     backend_it
uk.fedimeteo.com     backend_uk
jp.fedimeteo.com     backend_jp
us.fedimeteo.com     backend_us
usa.fedimeteo.com    backend_us
can.fedimeteo.com    backend_ca
canada.fedimeteo.com backend_ca

use_backend %[req.hdr(host),field(1,:),lower,map(/usr/local/etc/fedimeteo.map,backend_fedimeteo)]

I like this because it keeps the configuration honest. The frontend contains the policy. The map contains the data. Adding a country means adding an entry to the map and defining a backend. I do not need to make the frontend more complicated every time the service grows.

Backends as small compartments

backend backend_it
    mode http
    http-reuse safe
    server srv1 10.0.0.2:8001 maxconn 30
backend backend_uk
    mode http
    http-reuse safe
    server srv1 10.0.0.7:8001 maxconn 30
backend backend_jp
    mode http
    http-reuse safe
    server srv1 10.0.0.32:8001 maxconn 30

The maxconn 30 value is not a magic number. It is a ceiling. I want each small backend to have a visible limit in front of it. If something starts hammering a country instance, I prefer the pressure to appear at the HAProxy layer instead of becoming unlimited concurrent work inside snac.

http-reuse safe lets HAProxy reuse backend connections where appropriate. This is another small reduction in unnecessary work. Opening connections repeatedly is not the biggest problem in the world, but avoiding it is still better, especially when many small services sit behind the same proxy.

The front door

frontend https_in
    bind :::443 v4v6 ssl crt /usr/local/etc/certs/ alpn h2,http/1.1
    mode http
    option http-keep-alive

ssl-default-bind-ciphersuites TLS_AES_128_GCM_SHA256:TLS_AES_256_GCM_SHA384:TLS_CHACHA20_POLY1305_SHA256
ssl-default-bind-options no-sslv3 no-tlsv10 no-tlsv11 no-tls-tickets

acl letsencrypt-acl path_beg /.well-known/acme-challenge/
http-request redirect scheme https code 301 unless letsencrypt-acl
use_backend letsencrypt-backend if letsencrypt-acl

http-request set-header X-Real-IP %[src]
http-request set-header X-Forwarded-Proto https

http-response set-header Strict-Transport-Security "max-age=31536000; includeSubDomains; preload"

Two caches, because the requests are different

cache mediacache
  total-max-size 128
  max-object-size 10000000
  max-age 3600
  process-vary on
  max-secondary-entries 12
cache jsoncache
  total-max-size 16
  max-object-size 1000000
  max-age 60
  process-vary on
  max-secondary-entries 12

The media cache is larger and has a longer maximum age. In FediMeteo, this mostly means the shared avatar and a few static-looking objects. Since there is intentionally almost no media, the important cached object is requested very often and remains warm.

The JSON cache is smaller and short-lived. It is there for public ActivityPub GET requests, not to store federation state forever. A 60 second cache is enough to collapse many repeated requests that arrive close together in time, without pretending that ActivityPub responses should be treated like immutable files.

This distinction is important. Caching is not one decision. It is a set of small decisions about what a response means, who can see it, how often it changes, and what happens if it is served again.

Recognizing media

acl is_media path_end -i .jpg .jpeg .png .gif .webp .svg .ico .mp4 .webm .mp3 .ogg .wav .flac .mov .avi .mkv .m4v

http-request set-var(txn.is_media) bool(true) if is_media

http-request cache-use mediacache if { var(txn.is_media) -m bool true }

http-response set-header Cache-Control "max-age=3600, public" if { var(txn.is_media) -m bool true }
http-response del-header Set-Cookie if { var(txn.is_media) -m bool true }
http-response del-header Vary if { var(txn.is_media) -m bool true }
http-response cache-store mediacache if { var(txn.is_media) -m bool true }

This is aggressive only if removed from its context. In this service, with this media policy, it is a reasonable choice. FediMeteo is not serving private media under these paths. It is mostly serving the same public avatar over and over.

For the same reason, I clean the request before it reaches the backend:

http-request del-header Authorization if { var(txn.is_media) -m bool true }
http-request del-header Cookie        if { var(txn.is_media) -m bool true }

The result is exactly what I want: the shared avatar becomes an almost perfect cache object. Small, public, repeatedly requested, and served by HAProxy instead of snac.

ActivityPub JSON microcaching

acl is_ap_json   req.hdr(Accept),lower -m sub application/activity+json
acl is_ap_ldjson req.hdr(Accept),lower -m sub application/ld+json
acl is_outbox    path_end /outbox
acl is_get       method GET
acl has_auth     req.hdr(Authorization) -m found
acl has_cookie   req.hdr(Cookie) -m found

So I only mark public ActivityPub GET requests as cacheable:

http-request set-var(txn.is_activitypub) bool(true) if is_get !is_outbox is_ap_json !has_auth !has_cookie
http-request set-var(txn.is_activitypub) bool(true) if is_get !is_outbox is_ap_ldjson !has_auth !has_cookie

It must be a GET, because I am not caching deliveries or anything that changes state. It must not be /outbox, because outbox collections are not the traffic I want to cache here. It must not have Authorization, and it must not have cookies, because authenticated or user-specific requests do not belong in a shared public cache.

Then the cache can be used and populated:

http-request cache-use jsoncache if { var(txn.is_activitypub) -m bool true }
http-response set-header Cache-Control "max-age=60, public" if { var(txn.is_activitypub) -m bool true }
http-response cache-store jsoncache if { var(txn.is_activitypub) -m bool true }

This is microcaching in the most practical sense. It reduces repeated work without changing the nature of the service.

Static media paths

acl is_short_path path_reg ^/[^/]+/s/
http-request cache-use mediacache if is_short_path

In FediMeteo this is less central than on a normal social instance, because I deliberately do not use media except for the avatar and basic static objects. Still, the rule fits the general policy: let HAProxy handle repeatable edge work, and let snac spend its threads where they are actually needed.

Vary, but not without limits

process-vary on
max-secondary-entries 12

For media, I remove Vary before storing the response. A shared avatar does not need to vary by Accept. For ActivityPub JSON, I am more careful because the representation matters.

Again, the important thing is not the number itself. It is the decision to make variation explicit and limited.

Seeing whether it works

http-response set-header X-Cache-Status HIT if !{ srv_id -m found }
http-response set-header X-Cache-Status MISS if { srv_id -m found }

Did this request reach snac?

A test can be as simple as:

curl -I https://it.fedimeteo.com/path/to/avatar.png
curl -I https://it.fedimeteo.com/path/to/avatar.png

For ActivityPub JSON, the test must use the right Accept header:

curl -I \
  -H 'Accept: application/activity+json' \
  https://it.fedimeteo.com/some/activitypub/object

curl -I \
  -H 'Cookie: test=value' \
  -H 'Accept: application/activity+json' \
  https://it.fedimeteo.com/some/activitypub/object
curl -I \
  -H 'Authorization: Bearer fake' \
  -H 'Accept: application/activity+json' \
  https://it.fedimeteo.com/some/activitypub/object

Compression and operational paths

filter compression
compression algo gzip
compression type text/css text/html text/javascript application/javascript text/plain text/xml application/json application/activity+json

There is also a local Prometheus exporter:

frontend prometheus
  bind 127.0.0.1:8405
  mode http
  http-request use-service prometheus-exporter
  no log

What this changes in practice

The map keeps hostname routing manageable. The backend definitions keep each country isolated and limited. The static homepage avoids dynamic work for something that changes once per hour. The shared avatar gives HAProxy one very hot media object to serve directly. The media cache keeps public files away from snac. The JSON microcache absorbs short ActivityPub bursts. Header cleanup prevents useless variation. Connection reuse avoids unnecessary backend connection churn.

But all of this is only a longer way of saying one thing:

fewer requests reach snac.

That is the metric I care about here.

Not because snac is slow. If anything, FediMeteo exists in its current form because snac is efficient enough to make this kind of project possible on a very small VPS. But precisely because the whole architecture is small and pleasant, I do not want to waste resources where there is no need.

This is also consistent with the rest of the project. Forecasts are serialized by scripts. Updates happen every six hours. The homepage is regenerated hourly. Countries live in separate jails. Snapshots and backups are handled outside the application. No single component tries to be the entire system.

HAProxy is just another small piece, but it sits in the right place to remove a lot of repeated work.

Caveats

It matches FediMeteo as it is now: almost no media, one shared avatar, static homepage, public forecasts, many small snac instances, and ActivityPub traffic that can benefit from a short public cache when there are no cookies or authorization headers.

If I decide one day to use media in forecasts, the media cache rules will need to be reviewed. If I use different avatars for each city or country, the cache will still work, but I will lose the very nice property of one shared, always-hot avatar. If ActivityPub responses become actor-dependent, public JSON caching must be reconsidered. If one country grows a very different traffic pattern from the others, it may deserve a different limit or policy.

This is why I do not like presenting configurations as magic. A good configuration is a written form of the assumptions behind a service. When the assumptions change, the configuration must change too.

Conclusion

The HAProxy layer follows this idea. It terminates TLS, routes hostnames through a map, reuses backend connections, serves the shared avatar from cache, microcaches public ActivityPub JSON, avoids authenticated and cookie-based traffic, and gives me a small diagnostic header to see what is happening.

There is no single brilliant directive here. There is only the usual work of matching infrastructure to reality.

FediMeteo publishes weather forecasts as text and emoji. The homepage is static HTML updated every hour. The accounts share the same avatar because it is enough, and because it is better for the cache. Each country has its own snac instance in its own FreeBSD jail. HAProxy stands in front of them and tries, quietly, not to bother them unless it has to.

I like this kind of infrastructure.

Not because it is invisible, but because when it works well, it leaves very little to say.

https://it-notes.dragas.net/2026/05/18/fedimeteo-haproxy-and-the-art-of-not-wasting-snac-threads/

#ITNotes #NoteHUB #fediverse #freebsd #haproxy #hosting #jail #networking #ownyourdata #server #snac #snac2 #social #web

Kleine Frage ins #Fediverse: wie macht ihr das mit verstorbenen Menschen, die ihr in euren Kontakten habt?

#poll #umfrage #pleaseboost

The old web was decentralized:

- Newsgroups
- Personal Websites
- Bulletin board
- Email as a service, not a platform
- Internet relay chat (IRC)
- Early blogs

Then corporations arrived with money and lock-in, turning the internet into centralized ad farms (Meta, X, TikTok). Users became consumers, trapped in algorithms, tracking, and enshittification. Revenue more important than people.

The Fediverse is a way back: no ads, no algorithms, no dark patterns. People first. A web worth reclaiming. And open source is the engine of this transformation.

Take back the web. Decentralize again 💪 Bring people to the Fediverse, promote open source and build federated services.

#TakeBackTheWeb #Decentralized #Fediverse #StopBigTech #OpenSource #DeGoogle #UnplugTrump

🛡️ #Cybersecurity news & tips across the #fediverse

“THE # PALANTIR IMPERIUM - w/ Senator Shoebridge https://www. youtube.com/live/gNi20i8xruU # AlexKarp 🤮 # Fascism # TechnoFascism # tech # technology # ai # antifa # antifascism # re...”

https://zirk.us/@JazzyKindaFella/116590720233107190

🤖 via RSS feed. Not an endorsement.

🛡️ #Cybersecurity news & tips across the #fediverse

“A # security researcher says # Microslop secretly built a # backdoor into # BitLocker , releases an # exploit to prove it # YellowKey exploit bypasses BitLocker full volume # encryption via USB stick...”

https://mastodon.online/@jonsnow/116590657498491131

🤖 via RSS feed. Not an endorsement.

🛡️ #Cybersecurity news & tips across the #fediverse

“"This may not be the Nuremberg trial, but we all know that the excuse of “following orders” is not an alibi when you know what you are doing. And everybody at Meta knew what they were doing. They knew they were designing...”

https://tldr.nettime.org/@remixtures/116590108321864222

🤖 via RSS feed. Not an endorsement.

🛡️ #Cybersecurity news & tips across the #fediverse

“https://www. europesays.com/uk/966552/ WHO declares global health emergency over Ebola outbreak – POLITICO # Borders # Data # DemocraticRepublicOfCongo # Ebola # GlobalHealth # Health # Infectious...”

https://pubeurope.com/@uk/116589814983476607

🤖 via RSS feed. Not an endorsement.

🛡️ #Cybersecurity news & tips across the #fediverse

“Unbelievable... https:// travel.state.gov/content/trave l/en/News/visas-news/announcement-of-expanded-screening-and-vetting-for-visa-applicants.html # democracy # socialmedia # surveillance # gdpr”

https://mastodon.social/@anthrazit/116589329336863800

🤖 via RSS feed. Not an endorsement.

🔆 #FediTips for https://PrivacySafe.Social & the #fediverse

“If anyone shares a link to my website on here, there will automatically be a smaller link to my account below the website link's preview (see the screenshot below for an example of this in action). If you would like thi...”

https://social.growyourown.services/@FediTips/116591232819434456

🤖 via RSS feed. Your Mileage May Vary.

Es kommt nicht auf die Größe an. #mastodon #fediverse Tagesschau

Alt...

Das Bild enthält einen Text, der zwei Online-Plattformen, Mastodon und Bluesky, diskutiert und ihr Engagement für das Gemeinwohl hervorhebt. Es wird erwähnt, dass Mastodon ein deutsches Unternehmen ist und Bluesky aus den USA stammt, mit Benutzerstatistiken für beide Plattformen: Nicht nur Größe relevant Beide Plattformen haben sich dem Gemeinwohl verpflichtet. Mastodon ist ein deutsches Unternehmen, Bluesky stammt aus den USA - und war ursprünglich eine Ausgründung von Twitter. Mit den Nutzerzahlen der Mega-Plattformen können sie nicht mithalten: Mastodon hat rund 750.000 monatlich aktive Nutzerinnen und Nutzer. Bei Bluesky existieren rund 41 Millionen Konten. X kam im Juli 2025 dagegen auf rund 600 Millionen monatliche Nutzer und Schätzungen zufolge auf 400 bis 600 Millionen aktive Nutzerinnen und Nutzer.

🛡️ #Cybersecurity news & tips across the #fediverse

“WHO declares global health emergency over Ebola outbreak – POLITICO The WHO typically only declares a public health emergency of international concern — one rung below pandemic in…
# UnitedStates # US # USA #...”

https://pubeurope.com/@UnitedStates/116589154027447187

🤖 via RSS feed. Not an endorsement.

🛡️ #Cybersecurity news & tips across the #fediverse

“Technofascism https:// third-bit.com/2026/05/15/techn ofascism/ # HackerNews # technofascism # technology # dystopia # digitalrights # surveillance”

https://mastodon.social/@h4ckernews/116586080061484239

🤖 via RSS feed. Not an endorsement.

Dear friends and followers,

Please consider following me at my alt account @boeckli@mas.to as I might have to stop using this self-hosted #Mastodon account due to the cost of hosting plan.

If I’m currently following you and you boost a lot, I might have to unfollow you to reduce the media usage. But I will make sure to follow you from my alt account.

Thank you for your understanding.

#FediVerse

Dear friends and followers,

Please consider following me at my alt account @jboeckli@mas.to as I might have to stop using this self-hosted #Mastodon account due to the cost of hosting plan.

If I’m currently following you and you boost a lot, I might have to unfollow you to reduce the media usage. But I will make sure to follow you from my alt account.

Thank you for your understanding.

#FediVerse

🛡️ #Cybersecurity news & tips across the #fediverse

“RE: https:// eigenmagic.net/@arichtman/1165 83583697455397 cue Admiral Akbar’s IT’S A TRAP dot jiff # honeypot # infosec # surveillance # finance”

https://mastodon.social/@blogdiva/116585950263860470

🤖 via RSS feed. Not an endorsement.

🛡️ #Cybersecurity news & tips across the #fediverse

“Has anyone got any information pertaining to the FCC Enhanced Know-Your-Customer Requirements proposal (FCC-26-27)? They're looking to force phone providers to verify customer addresses and IDs before turning on service,...”

https://expressional.social/@LovingLoudly/116585510639821517

🤖 via RSS feed. Not an endorsement.

🛡️ #Cybersecurity news & tips across the #fediverse

“The Atlas of # Surveillance is a searchable database and map that reveals which technologies, such as drones and automated license plate readers, are used by domestic law enforcement agencies across the United States....”

https://mas.to/@evedazzle/116584745794945840

🤖 via RSS feed. Not an endorsement.

Son bisken vermisse ich das Meer ja jetzt schon. Im Mai goennen ich mir noch einmal ein Wochenende in Kenting!

Moin #Fediverse und euch einen gesunden Start in diesen Sonntag. Alles wird gut 🙏

Alt...

Selfie eines Mannes mit dunkler Sonnenbrille und schwarzer Baseballkappe vor einem Strand bei bedecktem Himmel. Er traegt ein blau-weiss kariertes Hemd ueber einem dunklen T-Shirt und hat einen schwarzen Ohrhoerer im linken Ohr. Im Hintergrund fuehrt eine Holztreppe hinunter zum Sandstrand. Mehrere Menschen stehen oder sitzen am Wasser, einige baden im Meer. Am Strand stehen gestreifte Liegestuehle und Sonnenschirme in Pastellfarben. Rechts im Bild befindet sich ein Holzpfosten mit mehrsprachigen Schildern, darunter „Information Desk“, „Ice Lollies“ und „Beach Activities“. Das Meer wirkt ruhig, waehrend dunkle Regenwolken ueber dem Horizont haengen. Rechts hinten ragt eine bewachsene Landzunge ins Wasser.

Lieber @Orkan_der_rechtspflege

in Anbetracht dessen wie schnell jetzt im Starterpaket

https://fedidevs.com/s/MTAwNQ

eine ganze Menge cooler #Fediverse Accounts zusammengekommen sind und wir einen durchaus lebhaften Austausch zu einem markanten Hashtag für die #Jura|bubble erzeugen konnten, stellt sich mir die Frage, ob wir es zusammen schaffen könnten, die Rechtsanwaltskammern zu #Mastodon & Co zu lotsen?

Ich gestehe, dass ich Dich nicht nur frage, weil Du selbst offensichtlich ein Überzeugungstäter bist, sondern auch wegen des #Podcast (R)echt interessant.

https://www.brak.de/recht-interessant/

Wenn ich das richtig verstanden habe, bist Du Pressesprecherin der #BRAK - wie sind die Aussichten, dass Ihr mit gutem Beispiel vorangeht, gelegentlich über #Friendica oder Mastodon postet, vielleicht sogar ein Netzwerk etabliert und/oder z.B. den Podcast auch über #PeerTube laufen lasst?

Unabhänigig sind #FediJur und #Juriverse jetzt vorgestellte Hashtags in unserem Profil. Wer macht mit?

🛡️ #Cybersecurity news & tips across the #fediverse

“""The European Union has failed to prevent member states from exporting surveillance technology to governments with well-documented histories of using technology to spy on activists, journalists, and other critical voice...”

https://tldr.nettime.org/@remixtures/116584686269041800

🤖 via RSS feed. Not an endorsement.

🛡️ #Cybersecurity news & tips across the #fediverse

“TechNadu spoke with Jillian C. York from EFF about internet shutdowns, surveillance, metadata exposure, and digital safety during conflict situations. “Digital security is about reducing risk, not eliminating it.” 📖 R...”

https://infosec.exchange/@technadu/116584637794420471

🤖 via RSS feed. Not an endorsement.

🛡️ #Cybersecurity news & tips across the #fediverse

“That free online tool is tracking you – here’s how it works https:// anonyome.com/resources/blog/fr ee-online-tools-tracking/ # privacy # surveillance”

https://mastodon.thenewoil.org/@thenewoil/116583904112798786

🤖 via RSS feed. Not an endorsement.

🛡️ #Cybersecurity news & tips across the #fediverse

“# children are clever If you forbid something they'll look for a workaround https:// techcrunch.com/2026/05/06/some -kids-are-bypassing-age-verification-checks-with-a-fake-mustache/ # ageverification does no...”

https://chaos.social/@Katika/116583677332807214

🤖 via RSS feed. Not an endorsement.