So some bad news regarding our account here on Mastodon and the #Fediverse
I'm going to have to suspend, at least for now, posting any links to content on our website on this platform. The #MastoDdos effect is only getting worse, and it now brings our website down for a solid 5 to 7 minutes everytime I post a URL. We've tried to fix this on our end, without any real luck. Caching, Cloudfare, etc etc. None of it works.
What I'll do instead is post links to our Threads account when new content is posted on our website. A bit of a weird fix, but until the infrastructure in the fediverse evolves to deal with this growing problem, I can't have our website go down that often. It has further unintended side effects (like harming our SEO ranking).
Of course, I'll still be participating here daily on coffee subjects!
Actually, I can still post content links here to CoffeeGeek, but I have to be smart about it: I have to post them as links, and also attach a photo to my post, so that the link doesn't trigger a card call to our website.
So, going forward (for now at least), when we do post new content on CoffeeGeek, I will post the link here, but also attach a photo related to the story. The link should still work, but not bombard our website from 1000s of instances looking for a card.
@coffeegeek this doesn't work, unfortunately. The software still requests the link preview.
I've seen it tested in real time and saw the linked site go down immediately.
@coffeegeek so we need regional service fedi instances that do card caching. Technically doable, politically impossible, I guess
@venite another solution could probably be to establish a mechanism which loads the card when posting something and then embed all the information into the post. @coffeegeek