Someone was trying to access /api/v1/streaming/public at bolha.one with the following user-agent:

```
http.rb/4.4.1 (Mastodon/3.3.0; +https://squid.cafe/) Bot
```

But @chigh posted (and pinned the post) saying that they don't have a bot/crawler and their instance is using Mastodon 4.4.9, not 3.3.0.

🦑 https://squid.cafe/@chigh/114438681305116700

Squid.cafe instance IP is 165.227.78.15 (DigitalOcean 🇺🇸), but the crawler came from 37.187.151.114 (OVH 🇫🇷).

So #mastoAdmin be aware of those bots faking user-agents and pretending to be another instance.

You can also require authentication to access your public feeds. I'm doing so and the bot received an error.

Me: fumbles around for the last 2 months trying to define media lifecycle rules on our two OVH S3 buckets—one for the main data and one for backups—meaning the rules aren’t exactly the same & the volume grows and shrinks rapidly, with a significant inertia)

OVH: waits for my rules to finally be somewhat robust and effective before launching... the rule management UI and the associated documentation 😑

https://help.ovhcloud.com/csm/fr-public-cloud-storage-s3-bucket-lifecycle?id=kb_article_view&sysparm_article=KB0066010

#MastoAdmin #S3 #OVH

PSA: social.okoyono.de läuft jetzt mit Version 4.5.9

#mastoadmin

Alasan geser ke glitch-soc:

• bisa markdown
• bisa markdown
• bisa markdown
• pokoknya bisa markdown deh

#mastodon #mastoadmin #glitch

Ihr habt die Erschütterung der Macht vermutlich gespürt, wir waren kurz offline. Grund: Ich habe das aktuelle Update eingespielt ;) Damit ist der brettspiel.space mit einem Tag Verspätung auf Version 4.5.9

#mastoadmin