isabelroses.com / amifamousyet
scraping atproto for the most followed accounts
fork atom

fix: duplicate accounts

this however does introduce the `pds` issue. where we don't know a true
pds of a given user

isabelroses.com 6a9b85d2 a6ae444f

+13 -2
unified split
+5
.github/workflows/website.yml
··· 4 4 workflow_dispatch: 5 5 schedule: 6 6 - cron: "0 3 * * *" # run daily at 03:00 UTC 7 + push: 8 + branches: 9 + - main 10 + paths: 11 + - dist/* 7 12 8 13 jobs: 9 14 build:
+1 -1
site/template.html
··· 3 3 <head> 4 4 <meta charset="UTF-8" /> 5 5 <meta name="viewport" content="width=device-width, initial-scale=1.0" /> 6 - <title>Data Table</title> 6 + <title>Am I Famous Yet?</title> 7 7 <style> 8 8 :root { 9 9 color-scheme: light dark;
+7 -1
src/index.js
··· 27 27 const data = await response.json(); 28 28 29 29 // only get at did's from the accounts, and propigate the pds 30 - accounts.push(...data.repos.map((acc) => ({ did: acc.did, pds }))); 30 + // and also filter out inactive accounts 31 + const accs = data.repos.map(acc => { 32 + if (!acc.active) return null; 33 + return { did: acc.did, pds }; 34 + }).filter(x => x); 35 + 36 + accounts.push(...accs); 31 37 32 38 if (data.cursor) { 33 39 return await getAccountsOnPds(pds, data.cursor, accounts);