Full stack web developer currently working mostly with #PHP / #Laravel, Vanilla #Javascript and #SCSS. Love learning more about (almost) anything, but particularly #MySQL and #InfoSec. Currently learning Arabic. Husband, father of two boys, Christian.
The reason I'm suggesting this, is because if you are a small/medium instance with open registrations, and spammers find and abuse your instance, I imagine that other instances will limit/suspend your instance without hesitation, given how willing some were to limit/suspend the much larger mastodon.social.
But do note this comment on the PR:
“To give some context to people seeing this: this is an emergency feature backport from Glitch SOC to help mitigating an ongoing spam wave, this feature may not make it in a next release, or with significative changes.”
Edited to add: multiple people have rightly commented on the accessibility concerns with hCaptcha: hCaptcha is really really really bad for blind and visually impaired people.
Please have a look at this excellent reply for more details:
This is VERY bad news for users of small instances like myself.
I do understand the reasoning behind it, and I'm not sure there is a good alternative. But it sure feels a bit like a deja vu from the self hosted email days ...
Today I was reminded that Enums where only introduced into PHP with version 8.1, which is less than 2 years old.
It’s one of my favourite little additions to PHP ever, and I really don’t want to work in a codebase that doesn’t have Enum support ever again. (I actually upgraded two apps I’m responsible for to 8.1 shortly after release, just to gain Enum support).
I've noticed a lot of chatter about setting up Elasticsearch for Mastodon 4.2's new full text search over the last few days, including what hardware is required, how difficult is it, etc.
So I thought I’d write down my experience, including the hardware I'm running Elasticsearch on for my single user instance:
I think he expresses a lot of things that I have held for a long time. And I believe more and more (although I might be wrong of course 😉) that people not grasping these things is a big big reason for the polarisation and partisanship of our age.
So, read the article! And pay particular attention to the four takeaways at the bottom.
This release brings no new features, but simplifies and unifies configuration of it: Instead of a large list of command line flags / environment variables, FediFetcher is now configured using a JSON file.
You don't need to update to this version immediately, but if you are running FediFetcher as a GitHub Action, you'll need to update and create a JSON file with options eventually, as configuration through Environment variables will no longer be possible going forward.
THIS IS A BREAKING CHANGE, so please read the release notes for detailed instructions, and let me know if you have any questions.
I’m not a big fan of summary/details generally because it’s just too inconsistent, but dialogs are great. And I didn’t actually know about input type="color" yet.
I just checked, and it appears that only about 1% of all 300k Mastodon users that my instance knows about currently have opted into full text search 😢
Really hoping that number will increase!
Also, does anyone know how Mastodon indexes users from non-Mastodon fediverse servers? These presumably don't have the indexable flag set. I hope Mastodon still indexes those, given that pretty much all other Fediverse software indexes all users?!
(edit: been asked a few times how i got those numbers: Two simple SQL queries: select count(*) from accounts; followed by select count(*) from accounts where indexable = true;)
I know it's been a long time since I tagged a new version of FediFetcher, but it's time to do so again:
I just released version 7.0.3. This is mostly a maintenance release fixing a number of bugs, but we also introduce support for the Iceshrimp fork of Misskey.
Please check the release notes for full details including update instructions:
I think this is actually the first release where I haven't contributed any code myself. A huge thank you to the amazing contributors @toadking, @root, @zotan, @jonas, @jaytay, and IhoBas (sorry, I don't know your fedi handle)
@shawnhooper probably also worth pointing out that the display of the quoted post therefore also depends on the client:
Most now support ‘quote boosting’ (ie a special preview for links to mastodon posts), but some (notably the official mastodon web and mobile clients) do not.
Got to say: Just been through upgrading an app from #PHP 8.1 to 8.3 and it's really nice and painfree.
Very few breaking changes, and the few that are there are stuff that a sensible person would've addressed a long time ago.
Unfortuantely that means that apart from readonly classes, there are also few exciting new things in there. But I guess these also are just point updates after all…
Almost boring 😉 (Not a bad thing! Stability is also nice.)
@BeAware I think Mailgun by default sort of suggests setting up mx records, but you don’t need them if you only use Mailgun for mastodon, and can remove them without any effect whatsoever.
Personally I use Mailgun for sending from mastodon, and Fastmail for everything else on the same domain. It’s definitely possible
So....I want to migrate from Mastodon to Sharkey. The catch is, I would LIKE to end up back on my current domain....is this possible at all?
I have a domain I could park a Sharkey instance to migrate to, but if I make a new Sharkey instance on my current domain after I shut the Mastodon instance down, will I be able to migrate back with little issue?🤔
@BeAware you might be able to do this via a 2 step migration:
Firstly migrate to an instance at temp.beware.live. Then do a self destruct on your old instance. Importantly wait for all sidekiq jobs (including retries of failed jobs!) to finish afterwards. This may take hours, days, or weeks.
Finally set up a new instance on your domain and migrate to it.
This may or may not work, so do at your own risk, but this is the only way I could conceptually imagine it might work. I’ve never heard of anyone actually attempting it, though, so this seems unknown territory…
