rra
/
dafr
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
doing applied fediverse research
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
16 Commits
1 Branch
0 Tags
13 MiB
 
Tree: 1512278240
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '1512278240'
${ noResults }
rra 1512278240
now based primarily on nodeinfo2, add socksproxy, filtering out weird stuff 		5 years ago
.gitignore gitignore and readme 7 years ago
README.md scraper now uses parallelism 7 years ago
fedicrawler.py now based primarily on nodeinfo2, add socksproxy, filtering out weird stuff 5 years ago
instance_scrape.json 29/4 2020 5 years ago
instances.txt first version, crawls only the announced peers 7 years ago

README.md

directorate for applied fediverse research

  • independently tries to verify fediverse statistics
  • draws conclusions from that

methodology

Currently the script starts from https://post.lurk.org and queries /api/v1/instance/peers to find servers it is peering with. For each of the peering servers it hasn't seen before it does the same and in addition it tries to query /api/v1/instance for meta data.

This method is a bit lacking because providing /api/v1/instance is voluntary and specific to later versions of mastodon/activitypub fediverse. We should study the methodology of fediverse.network for better results.

When the request fails on a given instance it just logs it as 'error' now.

Latest scrape results can be found in instance_scrape.json

TODO FIXME

  • add detailed error message to json when we get one
  • abstract the functions so we can multithread them
  • find a way to also scrape for instances that don't announce themselves