known
known copied to clipboard
Explicit social networking functionality
Known is at it's core a distributed, and platform agnostic, social network, it'd be cool if this was more explicit.
Some things wot is needed:
- [ ] Friend / follow: functionally done but needs
- [ ] Friend management UX (#343)
- [ ] Subscription feeds / reader (engine mostly there it seems, but needs to be exposed)
- [x] Friend add discovery (implemented through MF2 mining)
- [ ] Third party use authentication mechanism, e.g. like https://github.com/mapkyca/IdnoOpenPGPSignin with key exchange on friending, or some other mechanism
- [ ] Event notification (#7), engine and UI for notifying disparate users of events (e.g. new followers, new messages, etc)
- [ ] Notification with @mention and cross site @mention using friends (perhaps implemented via webmention, at least for public stuff)
Once this base is there (basically the idea of remote users, with auth), we can start building things like
- [ ] Private messages (#304)
- [ ] End to end encrypted chat
- [x] Run the whole enchilada as a Tor hidden service (https://www.marcus-povey.co.uk/2015/04/29/running-known-as-a-tor-hidden-service/)
But these are beyond the scope of this ticket.
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
WRT checkbox #5, support for WebID-RSA would be really lovely.
Bumping this in ref #2615 bringing in Activity Pub to known will automatically bring in support for friends/follower 1-1 messaging (via ActivityPub Inbox) and other social network feature not only within known - known instance but between all projects that support Activity pub like mastodon etc
@mapkyca also see #3028 that's the basic starting point for social networking like functionality and a mandatory Entity Type that would be required to support ActivityPub
Is this still a thing as far as everybody can tell? Or did others issues in this sequence get closed due to inactivity?