Perhaps reputation can be adjusted by a combination of click-to-view-details events combined with like/share events. The quantity of followers of an account is another indicator of reputation.
That Mastodon link is really interesting, I didnāt think about how dangerous something as simple as āsharesā could be. There are definitely some good thoughts there.
Also, on the topic of social networks, I wrote a short blog post recently and I wonder if you guys think itās accurate in terms of the primary advantages of a decentralized social network. Thereās been a lot of talk here about content creators and reputation, but I focused more on the Facebook use case, where itās less about following content creators and more about regular user interaction.
You guys need a data model that is a) generic b) has URIs as native IDs c) has a zero-cost merge operation
Currently there is only one that fits the bill: RDF, plus Linked Data. Itās a directed graph model with mutiple serialization formats: https://www.w3.org/TR/rdf11-primer/
It would be great to benefit from a social media system between members, I am thinking it could be done through IPFS. Submitting there, in case a great tool is coming
The original idea was to use a DHT to serve(requests for a particular public key) a magnet link(and signature) to a json file containing profile information, including other magnet links which represent a users publications. I experimented with IFPS/IPNS a bit and liked the API, so I decided to make the switch. Now, instead of the DHT responding with a magnet link, Iām using IPNS to respond with an IPFS link which points to the aforementioned json file. This architecture can be used to publish arbitrary content types (videos, blogs in the form of txt/html files, etc) and the UI(electron+angular) will render the media accordingly.
Development has been going well, expect I canāt seem to get IPNS to serve the IPFS links outside of my local network. Until recently, Iāve been using the default config. Anyone have any thoughts on a more reliable way to configure? I will probably post this in an OP. So if this seems like the wrong venueā¦
Any social / sharing / logging layer above IPFS would be awesome nowā¦ @iohzrd did you have a look to Textile. It has a good documentation and functionalities can be extended to any formatā¦
What is your opinion?
I wasnāt planning on having the identity files be accessible via http/s / regular browsers(except via webtorrent). Rather, have electron acquire them directly through ipfs(which would already work if IPNS was more reliable/ i could figure out how to configure it properly) , so DNSLINK isnāt relevant. and considering What Iām going for is a publication / subscription (think youtube minus all the manipulationā¦) platform, where ones content is, well, public. Iām not sure textile is of much use TBH. I see no need to do anything more complex than serve json files containing magnet/ipfs links. One of the main design goals for this project is censorship resistanceā¦
In fact, webtorrent is so reliable at this point that Iām not even tied to using ipfs for the distribution of the actual content files, and therefore am primarily interested in using IPNS as a means to have a persistent identity pointing to mutable content (the identity file)
my approach to this, is simply to not have a reputation / rating system at all and leave all of that to good old human interaction (sharing IRL, mirroring, whatever) or at most, each identity having a āsuggestedā field (see above) so if you trust one publisher, likeliness is youāll enjoy publishers they subscribe to. Basically, word of mouthā¦
Itās easier to over engineer something than it is to get it just rightā¦ and to be frank, i donāt think there is a way to get a reputation / rating system ājust rightā.
Holy molyā¦ Iām a bit late to the party I guessā¦
I have not read this whole thread but only the intro postā¦ thanks for noticing me! I am working on a prototype implementation of my ideas using Rust and GTK for the GUI. Nothing is there yet, as Iām still figuring out the details of the protocol and how to effectively use IPLD rather than putting links in JSON and traversing āby handā.
Following is a summary of a potential method to combine social media with IPFS, based on current state of the technology, that I posted on Gab at:
Iām exploring creation of alt-tech, in the form of an open source, resilient, easy to install, peer-to-peer chat and file management system, targeted for use in oppressive societies, and looking for a group discussion on the merits of such a project.
The current concept being explored uses an open-source browser, modified to have a chat sidebar feature. The user would install the following apps:
Browser with chat feature and WebRTC built-in
IPFS Companion extension in the browser
IPFS Desktop app
IPFS would be used for the following:
Distributed chat/file system peer server
Resilient infrastructure
Distributed file management
Signaling protocol for WebRTC
When the chat feature is launched in the browser, the browser would talk to the IPFS daemon to identify available peers that also support the chat feature. The user could then try to initiate chat with one or more suitable peers, where the data streaming for the chat would occur via WebRTC
The chat UI could be designed to do some of the following to aid research/collaboration:
Allow linkage to IPFS file resources
Normal web URL hyperlinks
Establish chat groups
Identify trusted chat peers
I have a Google shared doc started for project specs development