Okay, that's interesting. I just assumed that it searched the whole browser database for comments of a user in all subs but what it actually does is, when somebody posts they attach the cid of their previous comment. I guess the main issue with that is, as soon as a sub in that chain is offline, the link breaks.
Thinking about that, a user profile might be similar to a community but it's actually a bit different in that only the owner can post to it so there's no need to have captchas but only a private key that can update a IPNS record (from what I understand about IPFS) which every user has in their browser. So that means it should be possible for a user to publish their profile on IPFS (if its possible to do that in the browser, otherwise we would need something like a reverse gateway to publish stuff) and everybody who wants to seed it can (for example a Plebbit node could query and seed it once a user posts in their community), without the user actually having to stay online 24/7 and if nobody seeds it, the user can come back online and republish it since they keep the data in their browser. Maybe we're describing the same thing and it's probably not easy to implement either, just wanted to get this out there.
>as soon as a sub in that chain is offline, the link breaks.
anyone can seed comment.author.previousCid, so the author can seed his own profile cids, or people who recently downloaded that specific cid would also seed it. since most people are just using the web version at the moment, then if the sub is down, the cid would probably also be down, but in the future it will be less of an issue.
also in the future the user will probably include more links in each comment so that it's more reliable.
also in the future the users will probably have an option to publish IPNS records using their plebbit public key, so a cid will not be needed to view a user's profile, and also they'll be able to reorganize the linked list differently, maybe using pages similar to subplebbits.
once P2P in the browser is done implementing and public RPCs are implemented, this will even be possible by web peers. A user can seed his IPNS record in the browser while he's online, and when he's not online, his IPNS record can be cached by gateways and/or seeded by public RPCs.
>as soon as a sub in that chain is offline, the link breaks.
anyone can seed comment.author.previousCid, so the author can seed his own profile cids, or people who recently downloaded that specific cid would also seed it. since most people are just using the web version at the moment, then if the sub is down, the cid would probably also be down, but in the future it will be less of an issue.
also in the future the user will probably include more links in each comment so that it's more reliable.
also in the future the users will probably have an option to publish IPNS records using their plebbit public key, so a cid will not be needed to view a user's profile, and also they'll be able to reorganize the linked list differently, maybe using pages similar to subplebbits.
once P2P in the browser is done implementing and public RPCs are implemented, this will even be possible by web peers. A user can seed his IPNS record in the browser while he's online, and when he's not online, his IPNS record can be cached by gateways and/or seeded by public RPCs.
>as soon as a sub in that chain is offline, the link breaks.
anyone can seed comment.author.previousCid, so the author can seed his own profile cids, or people who recently downloaded that specific cid would also seed it. since most people are just using the web version at the moment, then if the sub is down, the cid would probably also be down, but in the future it will be less of an issue.
also in the future the user will probably include more links in each comment so that it's more reliable.
also in the future the users will probably have an option to publish IPNS records using their plebbit public key, so a cid will not be needed to view a user's profile, and also they'll be able to reorganize the linked list differently, maybe using pages similar to subplebbits.
once P2P in the browser is done implementing and public RPCs are implemented, this will even be possible by web peers. A user can seed his IPNS record in the browser while he's online, and when he's not online, his IPNS record can be cached by gateways and/or seeded by public RPCs.
Plebscan