iiinova — where your digital self keeps evolving

Replies

dan @danabra.mov · 19/12/2024

the mission is to figure out how to make products with decentralized and decoupled hosting that’s controlled by the user. so we can’t be “we’ll work on product a bit and then on mission a bit”, any move on the product needs to be within the mission. or at least it needs to not move against it

2719

dan @danabra.mov · 19/12/2024

take bookmarks. they’d either have to be completely public (maybe ok? but probably not for a lot of people), completely private-as-in-centralized-product and only available to the Bluesky app (undermines the mission), or the team have to take a step back and design a private on-protocol data model

5342

EasilyDistracted @babblingfringe.bsky.social · 19/12/2024

Bookmarks being client-side doesn’t seem like that much of an undermining situation - after all some users (ie anyone using a browser) already have bookmarks, and the current non-public worksroubd is just to share the skeet, copy the link, then pop it into the notes app, etc

010

emma 🍞 @bnuuy.bsky.social · 19/12/2024

how do mutes work then? they’re private and available to the wider atmosphere, no?

110

Bill Stewart @billstewart.bsky.social · 19/12/2024

By "private-as-in-centralized-product" do you mean stored privately in the personal data server? For bookmarks, another approach would be to store them in the app's data, in some format that's easily portable between instances (e.g. JSON) so you can back it up, move it phone-to-web etc

000

dan @danabra.mov · 19/12/2024

for DMs we had to do the second option (pretty much centralized) because they’re *too* essential for the product to survive, and we can’t afford to wait to do it “properly” (third option). for bookmarks, it seems like we may be able to get away with waiting a bit more and then doing it properly

3260

francisco @franciscomrtt.bsky.social · 21/12/2024

i mean... would be very good on the long-term run: being able to have an account on a private on-protocol data model not controlled by a centralized platform? and then build on that model privacy oriented features like bookmarks, likes being private? - I think you'll all get it as a team.

010