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 fedifinder.glitch.me seems to work fine again, I added two backups that you can use as well:
fedifinder-backup.glitch.me and 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.

I added an API (kinda) to #FediFinder. The only endpoint is /api/known_instances.json. It returns all instances it knows at the moment.

Currently, It is used to share data with @debirdify.

I don't know if it will stay public/available and/or if the structure will change in the future.

#FediFinder Day 9(?). I moved the handle identification from the backend to the frontend to improve performance. The server is only responsible for getting the data from Twitter and checking domains. No changes for the users.

With the functions, I moved some tests to the frontend. Only visible on the staging server or the code.

If handles are detected on the user profile, I show links to their import. Thanks @nart for the idea.

JSON export (including accounts without handles).

Fixed bugs.

There are people who had problems using #fedifinder. Not everyone knows what a CSV is or where to find the import. But I have a solution: Follow buttons!

If one or more #fediverse handles are identified on the profile of the person using fedifinder, they can now toggle on follow buttons to get directly to the follow request on their own instances. This should make it much easier.

(At the moment they only work for mastodon instances. I am open to pull requests for other software.)

But Luca, not everyone is in the fediverse. The export is useless for the other accounts. And in my Twitter archive are only the IDs of the people I followed. Not their names or websites. What about them?

If you scroll to the bottom of #Fedifinder, you can now view a table of the accounts that you have scanned. Even if they have no handle in their profile. Or one that wasn't correctly detected.

I updated the ReadMe to help people run their own #Fedifinder (no coding skills needed) and how to contribute.

github.com/lucahammer/fedifind…

And fedifinder got a new API endpoint. api/check. You can use it with a domain and/or handle as query parameters and get back the cached information fedifinder has for that: fedifinder.glitch.me/api/check…

Full speed! Thanks to the latest update, #Fedifinder scans my 2k followings within 10 seconds. From login to exported file.

The solution to a slow databases wasn't a fast database, but no database at all. Finally, I can tell you to share fedifinder with all of your contacts without fearing that the
service will go down because of it.

Go and find your people! fedifinder.glitch.me/

Only a small update for #FediFinder today: Splitting up functionality to multiple servers.

The main server is only responsible for getting data from Twitter from now on. A second server does the handle and domain lookups. Because the lookups locked the server up from time to time, this should make the service more stable and faster. If no lookup server is added to the .env, fedifinder is fully functional as a single server.

The sleepless #fediFinder update.

Authorize your Mastodon account to see which Fediverse accounts of your Twitter followings, you already follow.

Because the feature isn't finished yet and still confusing (you have to authorize, then click hide followings, then scan followings; no export yet) it's currently only available on the backup server: fedifinder-backup.glitch.me/

I am looking forward to your feedback (cc @illionas @ColinSch @botolo86) And to my bed. Good night.

First version of the new #Fedifinder. I redesigned the frontend to make it easier to use for people who are joining the #fediverse.

You can try it here: fedifinder-backup2.glitch.me/

Let me know, what you think.

100% - the web interface URL is in no way guaranteed to match the instance address. You need to check it.

Unfortunately Mastodon provides no API info for this, but once discovered you can cache it for each domain quite a while. It's unlikely to change often.