Thanks! Did you run it through TMUI in Brazil??
I suspect that most current Blockstack Browser users are not making it all the way to the identity management part of the UX anyway, given it’s so hard to find (particularly if you onboard directly into an app vs. discover Blockstack independently).
As such, while the feature does exist, I don’t suspect that omitting it from this release will cause a significant number of people to stop setting up profile images and names.
I think the best route forward with identity management (which I do think is important for cross-app usage with a single username) would be to find better ways to introduce profile editing to new users post-onboarding.
For example, we could provide a standard modal component via Blockstack Connect that apps trigger to set a profile photo in-app. It could have cropping, rotating, even filters! And make the whole experience a lot nicer than linking the user off-site to deal with a strange UI and then wander back to the app.
I would like to see the connect library licensed under CAL, not MIT
Interesting idea. Mind elaborating a bit on how you see CAL helping here?
Otherwise the claims in the modal dialog are false or at least misleading about what the apps are doing
We’ve brainstormed some ideas on how to enforce encryption via the platform even more tightly, so users don’t even have to trust developers to encrypt their data reliably. It gets a bit tricky, of course, since the user may want some data public and other data shared with just certain people. So the UX would be very important.
I just hope that the data won’t drive us away from Blockstack’s vision of a user-owned internet. I would like to see collections and a data explorer sooner than later!
It’s certainly our intent to seek out the best data to test our core theses, including data ownership and collections. If anyone has data of their own to share (e.g. from talking with customers, conducting surveys), we’d love to hear of it, too.
can I present my app as ꓐanter (with a different B) via the optional app details
I’m not sure how much we as a platform can or should do to prevent such impersonation if the user is already visiting from a falsified domain. If they’re visiting from such a domain, couldn’t the hacker simply fake Blockstack UI without even sending the user to the real authenticator?
app.blockstack.org as a landing page should be improved
Yep we plan to build this page out over time as we include features that drive users there.