#RSS3_Twitter : Checkout our RSS3 Anime Figures sketch https://t.co/ft1QiKGYPg https://t.co/r1kkWSoTy8
Twitter
RSS3
#RSS3 Anime Figures Naming Contest! #RSS3 动漫形象征名活动上线啦！ forms.gle/qngP18vRKbcPsW…
#RSS3_Twitter : GR10 End soon. Come and support us @gitcoin Grants! #RSS3 #RSS #Dapp #GitCoin https://t.co/krBYFgHpkb https://t.co/ZW5yGmBqJE
app.buidlbox.io
Ongoing and upcoming hackathons. Every buidlers gateway into the digital frontier.
#RSS3_Twitter : Today is the day! We are excited to share our #RSS3 Lightpaper with the community and beyond. Get a sneak peek at our new technologies and future plans now at ⬇️ 就是今天！ 我们很激动的和社区、项目关注者发布 #RSS3 轻皮书。阐述我们的新技术和未来计划 ⬇️ https://t.co/NWiUPwPwoh 🎉
#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.