Needs NIP-05 integrated verification based off the source profile data before unlocking the ability for someone to impersonate or clone a profile without validating custody.
Otherwise this looks pretty bitchin' - I even have a profile I can try this on that might be fun.
Nah, it's flat out Napster 2.0.
Instagram owns the data, as per their terms. It's up to Meta not the user.
Better to encourage people to just start again.
True true true. That is one thing about the pubkey is it is binding and traceable.
Sure, but if it ends up on Primal's relay then Meta can sue Primal and will easily win. Especially if a Primal employee is behind it. No fair use defence there. Or just tell Apple and Apple will remove Primal for not having the appropriate systemic moderation tools.
This will not happen because all of Nostr is far too small for most on the Meta legal team to have even heard of what Nostr is, let alone Primal.
Still though, not a good idea. People need to start again.
Something failed here, so close!
Lmk if you try again! Sometimes you literally have to press twice lol.
Gonna go check in on it.
Realizing that this is working on mobile and am getting further already likely some filtering on my end - disregard and thanks for building this!
Failed to create migration still on mobile perhaps not meant to be?
Are you trying just twitter? Will try to repro.
Ya twitter didn’t work for me. Will ping you when it’s fixed.
Yes this was with twitter that's my main test for now.. Thanks! There are a few profiles where I wonder how good they would do in a low-algo zone like this. It is becoming pretty clear how much of a walled garden X has become...
Is there any way to confirm only the account holder is able to unlock the data? Seems like that would help with end user confidence.
https://github.com/primalpaul1/instagram-to-nostr-v2/ can see for yourself.
nostr:nprofile1qyxhwumn8ghj7mn0wvhxcmmvqyfhwumn8ghj7mn0wd68yt3cxumnwtnrdqqzqaf4zg3xgl9xyn8pvjch5gjkd2nhf53ldqzd2kla9a3ssug0mhx5xwa65j it's working smooth at the moment now if you're doing a standard migration. figuring out an issue with logging in with nostr now. Lmk if it works!
its alive! nice
