fedifinder.glitch.me Open in urlscan Pro
34.231.87.196  Public Scan

Form analysis
0 forms found in the DOM

Text Content

Fedifinder



JOIN THE FEDIVERSE IN 5 EASY STEPS

Old version About
Old version About


1. FIND AN INSTANCE

AUTHORIZE TWITTER
TO SEE ON WHICH INSTANCES YOUR TWITTER CONTACTS ARE.




2. PUBLISH YOUR HANDLE


SIGN UP FOR A FEDIVERSE ACCOUNT AND ADD THE HANDLE TO YOUR TWITTER PROFILE
(DESCRIPTION, LOCATION, URL OR PINNED TWEET).


3. SCAN YOUR NETWORK


THE ACCOUNTS YOU FOLLOW GOT SCANNED ALREADY. OPTIONALLY, YOU CAN SCAN ACCOUNTS
ON LISTS AND FOLLOWERS FOR FEDIVERSE HANDLES.

Already scanned:

0 unique accounts scanned
0 unique handles from working fediverse domains found
0 handles from other services (eg. mail) or unresponsive servers
0 domains are still being checked


4. EXPORT YOUR NETWORK


GET ALL THE HANDLES IN ONE CSV FILE


5. IMPORT YOUR NETWORK


GO TO THE PREFERENCES OF YOUR FEDIVERSE ACCOUNT AND IMPORT YOUR WHOLE NETWORK AT
ONCE.


BONUS: BACKUP ALL ACCOUNTS


YOU CAN DOWNLOAD A CSV OR JSON WITH INFORMATION ABOUT ALL THE SCANNED ACCOUNTS.
INCLUDING THOSE THAT HAVEN'T JOINED THE FEDIVERSE YET.


ABOUT FEDIFINDER

Fedifinder helps you find the Fediverse accounts of your Twitter contacts.



HOW DOES IT WORK?

It is based on consent and does not give you handles of people who do not want
to be found. After authorizing it to access your Twitter account, Fedifinder
retreives up to 15.000 of your Followings (accounts which you follow). It then
scans the profiles and pinned Tweets of those accounts for Fediverse handles and
links. Because handles can look exactly like mail addresses it cross-checks them
with a cached list of domains. For domains it doesn't know, it tries to do a
webfinger lookup and collect information through the /.well-known/nodeinfo file.
The results of the lookup are cached on a domain level (domain x is part of the
fediverse, domain y is not).
It then shows you a list of the instances it found as well as the individual
accounts. You can export that list and import it in the preferences of the web
app of your instance.



PRIVACY AND SECURITY

This is a hobby project by @Luca@vis.social. While I try to follow best practice
and am as open about the process as possible, I can't guarantee the safety of
your data. Because Fedifinder mostly handles public data, the risk is low, but
still there.

You can run Fedifinder on your own server and look at the source code and
suggest improvements on Github.

 * The Twitter keys are stored in the client in an encrypted cookie that is
   transferred only over an secured connection.
 * The decryption key and Twitter app key is stored in an environment variable
   on the server. Access to the Twitter account is only possible with all three
   of them.
 * No information that identifies individuals is stored on the server. No
   account data either. The only thing that is cached is the information about
   domains. If they are part of the fediverse, which software they run and some
   other information, that's available through /.well-known/nodeinfo on each
   instance.
 * Some data is stored in the local storage of the client. For example the
   fediverse auth code. That isn't encrypted at the moment. The feature is still
   experimental and not available on the main server.
 * Fedifinder is hosted on Glitch which is part of fastly. They collect some
   usage data: https://glitch.com/legal/privacy. If you are concerned about
   that, please run it on your own machine.

If you have more questions, feel free to comment on this issue.


ALTERNATIVES

Debirdify works similar to Fedifinder, but has some additional options.
Twitodon needs you and the accounts to find to be signed up there.

Fedifinder by @luca@vis.social. The source code is licensed MIT. You can create
your own version by remixing it on Glitch or Github.