You can now check if the handles in your own Twitter profile are found. They are not added to the export. If there are issues with your profile, let me know.

Thanks for the idea @nelson. #twittermigration #neuhier #nieuwhier

I was able to reduce the wait time by around 40% by moving the domain checks to after the page got rendered. I fear some rate limiting issues came from people reloading before receiving a response.

False positives are kept in the visible list, but striked through. They are still removed from the exported CSV to reduce server load on imports.

Next up: Lists. They are the most requested feature. #fedifinder

Support for lists arrived in #fedifinder.

It shows you your own lists as well as the lists you are subscribed to. You can scan each of them and the found handles are added to the visible list as well as the download. (False positives of the previous scan are removed from the visible list with each additional scan.)

I made the scan of the followings optional in #fedifinder to improve speed, reduce the amount of rate limiting errors (eg. users reloading the page) and make it easier for people who only want to scan lists or maybe something else that gets added in the future.

Rate limiting errors aren't displayed as json anymore, but tell you how to fix them (wait, wait and wait).

More improvements for #fedfinder.

The results now display basic stats for each instance and if the registration is open. Thanks for the hint @pfefferle.

Better check if something is part of the #fediverse.

Data handling is still a mess, but less messy now, which results in fewer requests to the server and less jumping text.

Tiny changes on the frontend, massive ones in the backend. #fedifinder

- Option to scan the profiles of your followers
- Twiter handle where the fediverse account was found
- Handles of failed servers can be displayed

- Switched to API v2
- Pinned Tweets are included
- You can now scan up to 15k followings and 15k followers
- Better handling of rate limits
- Caching of reason of unreachability of servers (and limited amount of retries for servers that timed out)
- better regex

I am currently looking through the #fediverse software options to find more URL patterns of profiles. Here is what I have at the moment. Most of them are easy to detect. But for pleroma I saw some servers with and some without the @ in the username. Makes it harder.

domain.tld/@name
mastodon, misskey, pleroma, funkwhale

domain.tld/profile/name
friendica, hubzilla

domain.tld/u/name
diaspora

domain.tld/c/name/videos
peertube

domain.tld/name
pleroma, gnusocial

Today wasn't fun. While I was outside, I got many messages that #FediFinder didn't work. I checked it and saw that it was overloaded and crashed every few minutes. I then tried to fix it from my mobile, but with each line of code it seemed like I added multiple new bugs. Not good. So I added a message that its broken and to check back later.

I spent the whole afternoon and evening trying to fix the mistakes of past me and clean up the code to make it at least slightly easier in the future.

The important thing: #FediFinder is back!

While https://fedifinder.glitch.me seems to work fine again, I added two backups that you can use as well:
https://fedifinder-backup.glitch.me and https://fedifinder-backup2.glitch.me

New feature: You can now click on the usernames for the fediverse (may not always work because of different formats of software) and Twitter.

Instead of building a better export, I made the sessions persistent, so that not everyone re-logins when I change something and the server restarts.

You can now watch as #FediFinder checks the domains. And even retry if it gets stuck (should add a 10 second timeout there as well).

And I added links to the backup servers and info about donations to the homepage.