Re:Bluesky migrates from pg to single-tenant SQLite
by arthurcolle on Tuesday November 07, 2023 @12:58AM
(#38173716)
Any more?
[ Parent
| on HN ]
Re:Bluesky migrates from pg to single-tenant SQLite
by tymofiy on Tuesday November 07, 2023 @01:08AM
(#38173767)
bsky-social-lbjkg-gcxs4
bsky-social-zigwm-f3qpq
bsky-social-2jlu7-apy5a
bsky-social-6ct52-4egmz
bsky-social-cy64m-53sqn
Re:Bluesky migrates from pg to single-tenant SQLite
by da25 on Tuesday November 07, 2023 @01:37AM
(#38173895)
Ya'll got anymore of that.
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.
Re:Bluesky migrates from pg to single-tenant SQLite
by pests on Tuesday November 07, 2023 @03:28AM
(#38174503)
grep "bsky-" internet.txt
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
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?