#RSS3_Twitter : 🎉Our project on @gitcoin has received generous donations in just a few days from over 400 people. ❤️ Thank you so much for your support. 🚢 They are what keeps us motivated to keep pursuing a better, decentralised future. ⬇️ https://t.co/krBYFgHpkb https://t.co/vGMxmwrCj6
app.buidlbox.io
Ongoing and upcoming hackathons. Every buidlers gateway into the digital frontier.
Forwarded from GitHub
💬 New comment on RSS3#3 [Protocol Design] Who owns "comment"?
by @Rorical
I think every publisher could design the access controller of their contents, inside their posts or persona files. Firstly, we should not include a signature in RSS3 files, instead, we should put it along with the broadcast of operations (modification, addition, deletion) about a file. And then, we should specify an access controller inside our files, which could determine whether the signature is valid and the operation is legal. As node broadcast their operations toward a file, every node is able to check its validity.
With such a mechanism, we could easily solve the problem of ownership at the cost of a handful of hair of our programmers (
Also, because the field '@context' is closely related to the field 'upstream', the operations of the RSS3List file in the context field could separate from the operations of the upstream field, which means that we could give everyone the right to;
1. Post their comments freely to any other items (posts) and hide their comments from the original post (exist but invisible from the post).
2. The owner of posts could choose to hide any comment but could not eliminate them from the network.
3. The owner of posts could also specify the access of displaying comments of others by checking signature or proof of work (or maybe sending tokens).
Reply to this message to post a comment on GitHub.
by @Rorical
I think every publisher could design the access controller of their contents, inside their posts or persona files. Firstly, we should not include a signature in RSS3 files, instead, we should put it along with the broadcast of operations (modification, addition, deletion) about a file. And then, we should specify an access controller inside our files, which could determine whether the signature is valid and the operation is legal. As node broadcast their operations toward a file, every node is able to check its validity.
With such a mechanism, we could easily solve the problem of ownership at the cost of a handful of hair of our programmers (
Also, because the field '@context' is closely related to the field 'upstream', the operations of the RSS3List file in the context field could separate from the operations of the upstream field, which means that we could give everyone the right to;
1. Post their comments freely to any other items (posts) and hide their comments from the original post (exist but invisible from the post).
2. The owner of posts could choose to hide any comment but could not eliminate them from the network.
3. The owner of posts could also specify the access of displaying comments of others by checking signature or proof of work (or maybe sending tokens).
Reply to this message to post a comment on GitHub.
#RSS3_Twitter : GR10 ended. A huge thanks to everyone take part in. Also thanks @gitcoin that help us a lot. Provide the stage that we can shine bright. We prepare a thanks letter for you. ⬇️ https://t.co/Yqv1tbZDMK
@tuzimoe's post on Gitcoin (+ 1 comments)
Usagi Ryuu/兔子鲜笙@tuzimoe > RSS3 - RSS with human curation : Hello, dear contributorsRSS3 Team here. Please allow us to express our sincere gratitude and highest praise to you for your generosity and selfless sponsorship in Gitcoin GR10. Thank you.We started…
#RSS3_Twitter : Second quarter just pass we started with nothing and ran all the way to this moment, and we are exploring a whole new area, making bold attempts that no one has ever tried before. Thank you for being with us on this road full of unknowns. Cheers! https://t.co/WUe1tociv0
Twitter
RSS3
Second quarter just pass we started with nothing and ran all the way to this moment, and we are exploring a whole new area, making bold attempts that no one has ever tried before. Thank you for being with us on this road full of unknowns. Cheers!
#RSS3_Twitter : This is Re: ID 🐳 The first step to own your own data. Automatically sync your posts on social medias (currently only supports Twitter, but there'll be more in the near future) to a crypto based RSS3 files that is completely controlled by YOU. https://t.co/a0hgLQtkeB https://t.co/6XPGZVI42Y
Google
Re: ID
The first step to own your own data.
#RSS3_Twitter : Today, we are very sorry to hear that all LGBT related subscription accounts on WeChat have been blocked. As you may know, here at RSS3, we believe the right to create, disseminate and distribute information is the basic right for any cyber life.
#RSS3_Twitter : And it shall never be controlled by any single centralzed agency. The team at RSS3 has been working hard to bring more decentralized social and content applications to the ecosystem.
#RSS3_Twitter : If you own such an account that has been influenced by the incident, please contact us and we would love to help you to switch to a protocol where only YOU can control your contents.
#RSS3_Twitter : 今天，我们很遗憾听到微信上所有与 LGBT 相关的订阅帐户都已被封锁。如您所知，在 RSS3，我们相信创建、传播和分发信息的权利是任何网络生活的基本权利，它永远不该由一个中心化机构控制。
#RSS3_Twitter : RSS3 的团队一直在努力为生态系统带来更多去中心化的社交和内容应用程序。如果您拥有这样一个受到事件影响的帐户，请与我们联系，我们很乐意帮助您切换到只有您可以控制您的内容的协议。