Remote profile

@ernmander I suggest starting here: https://mastodon.social/@mastohost/117361644335860123

It's possible the answer to your question but reach out if you want me to have a look.

@ikklegemzuniverseplus 🤗

@krisfreedain 🤗

@ALFA 🤗

@shane I try to be fast ;)

Upgrade installed!

Everyone running on Masto.host is now on Mastodon v4.7.3.

Any issues or questions, please let me know.

Thanks 🐘

I will start installing Mastodon v4.7.3 on Masto.host.

There will be about 15 seconds of downtime during the upgrade.

Changelog: https://github.com/mastodon/mastodon/releases/tag/v4.7.3

@gjorgji_vasileski Happy to help! Just a small reminder: I said opt-in, not opt-out 😄 With a handful of artists it's easy to just ask them first. Good luck with it!

@gjorgji_vasileski Using the API itself is fine, that's what it's there for. The tricky part is consent. A lot of people on the fediverse really don't like their posts being pulled into other platforms without asking, and there's been a fair bit of backlash against projects that did it.

If you go ahead, I'd make it opt-in, or at the very least respect people's "discoverable"/noindex settings and #nobot tags, and make sure deletes and edits carry over. Also worth checking instances rules.

@crystalmoon it could technically, but then your browser would load every image straight from the remote server. That leaks your IP to whoever runs it, and they could swap the image for something malicious or something else entirely. Mastodon downloads and re-processes the media and saves it locally to avoid that sort of problem. Also, it would hammer small servers when a post goes viral.

@j Great :) Thanks

@stux 🤗

Some Mastodon servers have been seeing sudden spikes in remote media storage over the past few months, caused by bots crawling public pages and forcing Mastodon to re-download old media.

I wrote a short post on what's happening and how to reduce it:
https://masto.host/sudden-spikes-in-remote-media-storage/

@hosting @samsteiner Thank you for offering. I have not gone the Postfix route yet but I have been seeing the same spam pattern on my end in the last weeks. Currently I am using a combination of NGINX pattern detection of multiple registrations with failed email delivery in a short period of time to block registrations to the UA. It’s helping to somewhat mitigate it but I’m still not happy with the solution. Will continue to explore alternatives. Welcome suggestions.

@j 🤗