Bluesky migrates from pg to single-tenant SQLite

Re:Bluesky migrates from pg to single-tenant SQLite by hoseja on Tuesday November 07, 2023 @02:17AM (#38174084)

Maybe if you stop posting them with the easily-greppable first part they won't be so easy to scrape.

[ Parent | on HN ]

Re:Bluesky migrates from pg to single-tenant SQLite by pests on Tuesday November 07, 2023 @03:28AM (#38174503)

grep "bsky-" internet.txt

[ Parent | on HN ]

Re:Bluesky migrates from pg to single-tenant SQLite by numpad0 on Tuesday November 07, 2023 @03:55AM (#38174662)

No one seems to be taking two codes I'm putting up without the prefix for ~hour, this is likely the case

e: second one now used, first still up

[ Parent | on HN ]

Re:Bluesky migrates from pg to single-tenant SQLite by greyface- on Tuesday November 07, 2023 @04:25AM (#38174855)

I wonder what they're being used for. The UI doesn't expose it, but the Bluesky API will tell you who redeemed your invites. Open the site, watch for a "com.atproto.server.getAccountInviteCodes" request in your browser's network inspector, look in the "usedBy" field in the response JSON, and append the DID value there onto "https://bsky.app/profile/". Any commenters in the parent chain who got scraped want to take a look?

[ Parent | on HN ]

Re:Bluesky migrates from pg to single-tenant SQLite by numpad0 on Tuesday November 07, 2023 @04:38AM (#38174931)

I get "$username joined using your invite code!" in notification tab that leads to the user profile. So far the user hasn't done anything.

[ Parent | on HN ]