search

bluzelle / swarm-of-duty

Swarm of Duty is a series of bounties and challenges that Bluzelle has for developers to build specific projects for the Bluzelle network.
5 stars 8 forks source link

Anti-censorship Application #5

Open YingyaoX opened 4 years ago

YingyaoX commented 4 years ago

Description: Bluzelle allows leases to store data for periods of time, and charges in crypto for the length of the lease. Leases can range from seconds to minutes to hours to days to years to “forever”. 

Bluzelle is also keenly interested in free speech, and ensuring that information that gets censored by centralized authorities (governments, dictatorships, special interest groups, trolls, etc) is NOT lost. Often, it is the information that gets censored that is MOST important to the public interest. Bluzelle believes in the dissemination of true and honest information without being constrained by authorities. 

We ask the developer to build an application based on Bluzelle Testnet Database that has two parts:

A “crawler” that goes to websites (e.g. social media) and looks for posts with tags and content that are likely to get censored. Anything that matches such criteria might be a candidate. Any such “candidates” will be stored to Bluzelle with a very long lease. The lease would apply possibly based on the tags and the site in question. In some cases, a “forever” lease would make sense. A responsive (PC, mobile-friendly) website that lets the user freely view the latest content that is “cached” on Bluzelle. It is vital for anybody to view what was censored and in fact, highlight more prominently what was censored more recently, with more force, etc. It is up to the developer of this bounty to determine these metrics. Our goal here is to ensure that any content that gets censored gets highlighted as relevant and ensure that censorship is “punished” by spotlighting information that gets censorship. 

Requirements:

Rewards:

Resources:

Important points:

gitcoinbot commented 4 years ago

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

This issue now has a funding of 242400.0 BLZ (10112.93 USD @ $0.04/BLZ) attached to it.

gitcoinbot commented 4 years ago

Issue Status: 1. Open 2. Cancelled

Work has been started.

These users each claimed they can complete the work by 1 year, 9 months ago. Please review their action plans below:

1) uivlis has started work.

I will develop a full-blown solution for uncensorable speech, that will have a crawler and a website. 2) nanspro has started work.

I am working on a platform where user will be able to view tweets which are likely to be censored probably because they are anti govt or something. As we witnessed during COVID outbreak in china, the govt monitored twitter regularly and punished those who spoke against the govt https://techcrunch.com/2019/06/01/twitter-china-takedown/ I'll be working with my teammate @sounak98 and we'll come up with a good web app wihere users will be able to see all the content. We'll research a bit more into what platforms we can scrape. what tags to use etc 3) mikaellazarev has started work.

I will work on anti-censorship app using Buzelle DB. 4) cjsaveas has started work.

I'd like to give it a try, hope I can finish this job. 5) rajashree23 has started work.

I'll give it a try, hope I can finish this job.

Learn more on the Gitcoin Issue Details page.

uivlis commented 4 years ago

Just managed to build a dummy scrapper with blzjs, working towards a fully functional one, check it out here. Also, the frontend repo (empty as of now) is here.

nanspro commented 4 years ago

@YingyaoX shouldn't this bounty be cooperative? I am pretty good with backend (can't do frontend tho) and would love to work on this but i can't apply on gitcoin.

Bluzelle-Team commented 4 years ago

@YingyaoX shouldn't this bounty be cooperative? I am pretty good with backend (can't do frontend tho) and would love to work on this but i can't apply on gitcoin.

@nanspro We are trying to update the issue to "cooperative" on Gitcoin but it failed. We are contacting the Gitcoin team for help. Please continue to explore and work on this issue here. You can submit your work here in the comment manually and we will review. Thanks!

njmurarka commented 4 years ago

Just managed to build a dummy scrapper with blzjs, working towards a fully functional one, check it out here. Also, the frontend repo (empty as of now) is here.

Looking forward to seeing a running demo!

Bluzelle-Team commented 4 years ago

@YingyaoX shouldn't this bounty be cooperative? I am pretty good with backend (can't do frontend tho) and would love to work on this but i can't apply on gitcoin.

@nanspro we have updated Gitcoin to "cooperative". You can join the bounty on Gitcoin again. Thanks!

nanspro commented 4 years ago

@Bluzelle-Team will start working on it :+1:

nanspro commented 4 years ago

Also what's the bounty prize, is it $4k? The issue is funded with $10k so i was wondering.

Bluzelle-Team commented 4 years ago

Also what's the bounty prize, is it $4k? The issue is funded with $10k so i was wondering.

@nanspro it is $4k

gitcoinbot commented 4 years ago

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

Work for 242400.0 BLZ has been submitted by:

  1. @uivlis
  2. @mingderwang
  3. @nanspro
  4. @mikaellazarev

@bluzelle-team please take a look at the submitted work:

uivlis commented 4 years ago

Alright, I have a mostly prototype-like version of the app. I have just submitted work, hope you'll be as enthusiastic as I am. A few things to say, though:

  1. The submission refers to this repo. However, you must run separately the spider found here (for the spider, you will also need a VPN service and a Google Perspective API key).
  2. The way the scrapper works is it searches on DuckDuckGo for the most popular words of the day (on Google...!). Then, it passes the snippets of the results through the perspective API to compute censorability. The more toxic and less spammy, the more censorable.
  3. I could set up Heroku cron jobs to run these things once a day (no use to run more often since most popular google topics change every 24h). I guess this would be the next thing to do.
  4. Will also have to upload a video, but for now, I have put a .png demo screenshot of the app.

Can't wait your feedback, let me know your thoughts.

nanspro commented 4 years ago

@Bluzelle-Team sorry for the delay, is this bounty still open and if so for how many days? My teammate and I are done with crawlers and are can finish this in a week or so.

njmurarka commented 4 years ago

Yes. It is still open. You should have sufficient time for sure.

On Sat, May 2, 2020 at 7:21 AM Rahul Bishnoi notifications@github.com wrote:

@Bluzelle-Team https://github.com/Bluzelle-Team sorry for the delay, is this bounty still open and if so for how many days? My teammate and I are done with crawlers and are can finish this in a week or so.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/bluzelle/swarm-of-duty/issues/5#issuecomment-622960990, or unsubscribe https://github.com/notifications/unsubscribe-auth/AADTCQSGFYUFKJDDDGKDKP3RPQT6TANCNFSM4MDZQDWA .

nanspro commented 4 years ago

@njmurarka will be submitting today. Just wondering whether a deployed app is preferred or a simple local installation works?

mingderwang commented 4 years ago

the testnet is back, we are still waiting for the judgement for the winners.

mingderwang commented 4 years ago

we are still waiting for the judgement for the winners.

aahutsal commented 3 years ago

@YingyaoX shouldn't that issue be closed?

aahutsal commented 3 years ago

@Bluzelle-Team shouldn't that issue be closed?

uivlis commented 3 years ago

@aahutsal Well, technically, there's no winner selected, yet... A disgrace! I have been waiting for the adjudication for a year and a half now...

aahutsal commented 3 years ago

@uivlis shit happens, man...

aahutsal commented 3 years ago

@owocki Kevin, can you tell how does gitcoin has been architected? Do you have access to the attached monies, and have they been actually attached to blockchain? Or only reported attachment on gitcoin website?

owocki commented 3 years ago

we do not have access to the attached monies. you can email support@gitcoin.co and we can start the dispute procedure.

0xmikko commented 3 years ago

I want to join the discussion. @njmurarka asked me to redevelop many times, I worked for bluzelle like full time, and they paid me nothing. I feel myself cheated! My advise to all developers, please, stay away of Bluzzelle.

0xmikko commented 3 years ago

@uivlis @mingderwang @aahutsal Please, connect me - I think this relation to developers is not normal practice.

neeraj-bluzelle commented 3 years ago

Hello everyone.

As a reminder, some of the relevant terms of the original bounty:

We do our best to evaluate projects.

For example, in one case, our team spent considerable time testing the submission and going back and forth with the developer over the course of weeks to help get their project into a state where it was working properly. This was despite the requirement that the project be demo-able. As you can imagine, it is not practical for us to do this consistently.

We had four submissions, and while a clear winner was not found, we'd like to pay out the reward none-the-less, in this case, split evenly amongst the four submissions, $1K BLZ each.

Can each of you please confirm with us your ETH address? We will give everybody the same amount of BLZ, to be fair, in line with our general payout policies for multiple winners.

Thank you.

mingderwang commented 3 years ago

My @.***> Ethereum address is 0x9E4C996EFD1Adf643467d1a1EA51333C72a25453 (for Gitcoin)

Ming-der Wang

On Wed, Oct 27, 2021 at 4:53 AM Neeraj of Bluzelle @.***> wrote:

Hello everyone.

As a reminder, some of the relevant terms of the original bounty:

  • Be sure your submission is in a ready and demo-able state. We will not evaluate incomplete projects nor will code alone be an acceptable submission. Include all necessary details so we can try out your app.
  • The Bluzelle team will be solely responsible for choosing the winners, and if warranted, multiple winners are possible for each bounty.
  • The Bluzelle team will make the final decision, and reserves the right to not award a bounty for a challenge if no acceptable submissions are made.

We do our best to evaluate projects.

For example, in one case, our team spent considerable time testing the submission and going back and forth with the developer over the course of weeks to help get their project into a state where it was working properly. This was despite the requirement that the project be demo-able. As you can imagine, it is not practical for us to do this consistently.

We had four submissions, and while a clear winner was not found, we'd like to pay out the reward none-the-less, in this case, split evenly amongst the four submissions, $1K BLZ each.

Can each of you please confirm with us your ETH address?

Thank you.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/bluzelle/swarm-of-duty/issues/5#issuecomment-952316401, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAALRBXBDI6FSPL2XWGII23UI4IK7ANCNFSM4MDZQDWA .

mingderwang commented 3 years ago

@.*** Ming-der Wang's Ethereum Address is 0x9E4C996EFD1Adf643467d1a1EA51333C72a25453 You can send my prize to above address. Thank you.

On Wed, Nov 3, 2021 at 7:25 PM Ming-der Wang @.) < @.> wrote:

My @.***> Ethereum address is 0x9E4C996EFD1Adf643467d1a1EA51333C72a25453 (for Gitcoin)

Ming-der Wang

On Wed, Oct 27, 2021 at 4:53 AM Neeraj of Bluzelle < @.***> wrote:

Hello everyone.

As a reminder, some of the relevant terms of the original bounty:

  • Be sure your submission is in a ready and demo-able state. We will not evaluate incomplete projects nor will code alone be an acceptable submission. Include all necessary details so we can try out your app.
  • The Bluzelle team will be solely responsible for choosing the winners, and if warranted, multiple winners are possible for each bounty.
  • The Bluzelle team will make the final decision, and reserves the right to not award a bounty for a challenge if no acceptable submissions are made.

We do our best to evaluate projects.

For example, in one case, our team spent considerable time testing the submission and going back and forth with the developer over the course of weeks to help get their project into a state where it was working properly. This was despite the requirement that the project be demo-able. As you can imagine, it is not practical for us to do this consistently.

We had four submissions, and while a clear winner was not found, we'd like to pay out the reward none-the-less, in this case, split evenly amongst the four submissions, $1K BLZ each.

Can each of you please confirm with us your ETH address?

Thank you.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/bluzelle/swarm-of-duty/issues/5#issuecomment-952316401, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAALRBXBDI6FSPL2XWGII23UI4IK7ANCNFSM4MDZQDWA .

uivlis commented 3 years ago

We had four submissions, and while a clear winner was not found, we'd like to pay out the reward nonetheless

That clarity took 2 years to crystalize only by the grace of a certain developer whom your team spent considerable time going back and forth with...

Please grab my address from Gitcoin, you can do at least that. Mind the return of that developer if you don't.

0xmikko commented 3 years ago

0xd47707486d930838c30E97669a99f753af0EaB37

mingderwang commented 3 years ago

@neeraj-bluzelle when you will give us $1K BLZ each?

Ming-der Wang (mingderwang@gmail.com)

neeraj-bluzelle commented 2 years ago

@njmurarka will be submitting today. Just wondering whether a deployed app is preferred or a simple local installation works?

Please provide your ETH address, nanspro. The payment has already been made to 2 of the 3 other submissions. 3180 BLZ to each of the four submissions.

neeraj-bluzelle commented 2 years ago

@neeraj-bluzelle when you will give us $1K BLZ each?

Ming-der Wang (mingderwang@gmail.com)

Done. You should see it in your account.

neeraj-bluzelle commented 2 years ago

0xd47707486d930838c30E97669a99f753af0EaB37

Done. You should see it in your account.

sounak98 commented 2 years ago
  • Be sure your submission is in a ready and demo-able state. We will not evaluate incomplete projects nor will code alone be an acceptable submission. Include all necessary details so we can try out your app.

Our project was totally demoable, we still have the Github repository and discord chats, but I hope we won't have to get into those.

We do our best to evaluate projects.

For example, in one case, our team spent considerable time testing the submission and going back and forth with the developer over the course of weeks to help get their project into a state where it was working properly. This was despite the requirement that the project be demo-able. As you can imagine, it is not practical for us to do this consistently.

There had indeed been a lot of back and forth between our team (@nanspro and I) and the Bluzelle team, although most of it was them asking us to update our application as they had made some changes on their side. Rest of the times they were simply unresponsive. Even though we complied multiple times, we kind of lost hope after a certain point. It certainly didn't feel like the Bluezelle team did their best to evaluate the projects (at least not ours).

Being a new developer to web3 at that time, personally this experience scarred me and made me a little sceptical about picking bounties from Gitcoin (although I have done more work for other organisations after this and have never experienced such negligence ever again). I'm sure the other teams have felt something similar at the time and the comments on this thread potray that frustration very clearly.

We had four submissions, and while a clear winner was not found, we'd like to pay out the reward none-the-less, in this case, split evenly amongst the four submissions, $1K BLZ each.

The reward for the bounty at the time of submission was $4K worth of BLZ (which was 242400.0 BLZ) as mentioned here by @gitcoinbot. I think it's only fair to distribute that same amount if not more among all of the 4 submissions considering this massive delay and hassle that the developers had to face over the course of more than a year.

Let me know what you guys think @nanspro @uivlis @mingderwang @MikaelLazarev and @neeraj-bluzelle.

0xmikko commented 2 years ago

It totally shows Bluzelle relation to developers. I have 154 pages with chatting with @njmurarka , which is incredible for any hackathons. The sum of $1K looks fun for any blockchain dev now. Furthermore, during hackathon time, Bluzelle testbet works totally unstable, we spent much time just to to something there. Btw, @sounak98 , this decision and prize distribution will show us Bluzelle relation to exocsystem and devs.

njmurarka commented 2 years ago
  • Be sure your submission is in a ready and demo-able state. We will not evaluate incomplete projects nor will code alone be an acceptable submission. Include all necessary details so we can try out your app.

Our project was totally demoable, we still have the Github repository and discord chats, but I hope we won't have to get into those.

We do our best to evaluate projects. For example, in one case, our team spent considerable time testing the submission and going back and forth with the developer over the course of weeks to help get their project into a state where it was working properly. This was despite the requirement that the project be demo-able. As you can imagine, it is not practical for us to do this consistently.

There had indeed been a lot of back and forth between our team (@nanspro and I) and the Bluzelle team, although most of it was them asking us to update our application as they had made some changes on their side. Rest of the times they were simply unresponsive. Even though we complied multiple times, we kind of lost hope after a certain point. It certainly didn't feel like the Bluezelle team did their best to evaluate the projects (at least not ours).

Being a new developer to web3 at that time, personally this experience scarred me and made me a little sceptical about picking bounties from Gitcoin (although I have done more work for other organisations after this and have never experienced such negligence ever again). I'm sure the other teams have felt something similar at the time and the comments on this thread potray that frustration very clearly.

We had four submissions, and while a clear winner was not found, we'd like to pay out the reward none-the-less, in this case, split evenly amongst the four submissions, $1K BLZ each.

The reward for the bounty at the time of submission was $4K worth of BLZ (which was 242400.0 BLZ) as mentioned here by @gitcoinbot. I think it's only fair to distribute that same amount if not more among all of the 4 submissions considering this massive delay and hassle that the developers had to face over the course of more than a year.

Let me know what you guys think @nanspro @uivlis @mingderwang @MikaelLazarev and @neeraj-bluzelle.

Are you working with nanspro? I have been trying to track down one of your team members so we can pay you the 25%. We have already paid the other three submitters.