Sounds like a good idea but all i keep hearing lately is that twitter is close to dead. I don't use twitter so don't know how true this statement is but apparently twitter is not "cool" among the kids nowadays.
You know your getting old when you no longer know what is "cool"
In the previous system, people were paying for tweets, not re-tweets.For Feedzebirds, how does this look like:
* User adds tweet on the webpage. Sets a price per retweet.
* Webpage generates a Bitcoin address from BIP32 pubkey, shows QR code to user.
* When bitcoin balance for that Tweet is >0, start checking retweets.
* Query Twitter API for retweets
- Get all retweets (https://api.twitter.com/1.1/statuses/retweets/:id.json)
- Check if user is not a bot.
- User can claim bitcoins by tweeting a bitcoin address to @FeedTheBirdsClaim.
- If retweeter has a bitcoin address in his description, send it there automatically.
Is there anything I missed?
Just get it up so I can try it outIn the previous system, people were paying for tweets, not re-tweets.For Feedzebirds, how does this look like:
* User adds tweet on the webpage. Sets a price per retweet.
* Webpage generates a Bitcoin address from BIP32 pubkey, shows QR code to user.
* When bitcoin balance for that Tweet is >0, start checking retweets.
* Query Twitter API for retweets
- Get all retweets (https://api.twitter.com/1.1/statuses/retweets/:id.json)
- Check if user is not a bot.
- User can claim bitcoins by tweeting a bitcoin address to @FeedTheBirdsClaim.
- If retweeter has a bitcoin address in his description, send it there automatically.
Is there anything I missed?
A unique identifier was included with each proposed tweet so that the system could recognize relevant tweets.
The end result was that people were tweeting the message from their own twitter account, not just retweeting someone else's.
Do people have a preference on tweets vs re-tweets?
Any other suggestions on what should be implemented?
I think a correctly marketed tweet would be better served by being retweeted versus someone else tweeting out some random link. Retweeting many times a single tweet gives that tweet more weight in the Twitter algo and therefor it will rise to the top of people's feed. In addition it will give that person who tweeted it some more visibility. You want to stay away from just random people or even bots just tweeting out junk when their entire followers may be bots too. Their tweets could have no weight at all. Someone who is legit getting lots of retweets would hold more weight.In the previous system, people were paying for tweets, not re-tweets.For Feedzebirds, how does this look like:
* User adds tweet on the webpage. Sets a price per retweet.
* Webpage generates a Bitcoin address from BIP32 pubkey, shows QR code to user.
* When bitcoin balance for that Tweet is >0, start checking retweets.
* Query Twitter API for retweets
- Get all retweets (https://api.twitter.com/1.1/statuses/retweets/:id.json)
- Check if user is not a bot.
- User can claim bitcoins by tweeting a bitcoin address to @FeedTheBirdsClaim.
- If retweeter has a bitcoin address in his description, send it there automatically.
Is there anything I missed?
A unique identifier was included with each proposed tweet so that the system could recognize relevant tweets.
The end result was that people were tweeting the message from their own twitter account, not just retweeting someone else's.
Do people have a preference on tweets vs re-tweets?
Any other suggestions on what should be implemented?
Great points.I think a correctly marketed tweet would be better served by being retweeted versus someone else tweeting out some random link. Retweeting many times a single tweet gives that tweet more weight in the Twitter algo and therefor it will rise to the top of people's feed. In addition it will give that person who tweeted it some more visibility. You want to stay away from just random people or even bots just tweeting out junk when their entire followers may be bots too. Their tweets could have no weight at all. Someone who is legit getting lots of retweets would hold more weight.
Code: Select all
$insert = "INSERT INTO bitcoin_address (cid, uid, address, received, is_public, server) VALUES(0".
", 0, '".$value."', 0, 0, 2)";
db_query($insert);
@arnoudkLooks quite doable. It is just PHP and MySQL. I'm sure many things are broken as it has not been maintained.
I could not find any license agreement. Does this mean that we need to get permission from the author(s) first?
Also, there will be some security related work. I just opened a few php files, and the code is written in such a way that it is potentially vulnerable to MySQL injection attacks.
[code] $insert = "INSERT INTO bitcoin_address (cid, uid, address, received, is_public, server) VALUES(0".
", 0, '".$value."', 0, 0, 2)";
db_query($insert);[/code]
I am not sure if there are any other checks to ensure that no 'garbage' gets placed in $value - I have not checked. But this code is not written with the defense in depth mentality. Or, as Gavin Andresen likes to call it, with the belt AND suspenders approach.
@roger - if you are willing to take the risk on the license front, I'm willing to have a go!
Code: Select all
$q = "INSERT INTO bitcoin_address (cid, uid, address, received, is_public, server)
VALUES (:cid, :uid, :address, :received, :is_public, :server);";
$query = $dbh->prepare($q);
$results = $query->execute(array(
":cid" => $cid,
":uid" => $uid,
":address" => $address,
":received" => $received,
":is_public" => $is_public,
":server" => $server
));
Something that rhymes and comes easy off your mouth and gets easily imprinted in your brain. Hmmm.. bittweet? tweetbits?I'm actually hoping to rebrand it into Bitcoin.com somehow. Any ideas for the new branding?
Sent from my iPhone using Tapatalk
Looks great IMO!How's this look -
If you look at the 2nd and 3rd pages of the bitcointalk.org thread which you've cited you'll see comments indicating that they solved the problem just one week later.Unfortunately it seems like Twitter shut them down (by revoking their OAuth access to their application, which limits ability to get access to tweet information).
Anyone have any ideas on how a new version could get around this, or maybe have a better chance at fitting into twitters rules somehow?
https://bitcointalk.org/index.php?topic=60007.0
Lesson learned - pay the $50K fine and file registration statements. Depending on the type of securities for sale, you can circumvent this registration requirement in some cases.It seems that what may have finally and officially brought down FeedZeBirds.com was the SEC (U.S. Securities and Exchange Commission) in 2014.
It appears (view PDF) that the SEC alleged that in or around May 2012 that purported co-owner Erik Voorhees allegedly began selling 'shares' of FeedZeBirds -
...
7. Also on May 21, 2012, the website FreedomsPhoenix.com posted the following announcement titled “FeedZeBirds IPO”: FeedZeBirds is proud to announce that you can now own a piece of feedzebirds.com. On Thursday, May 24, at 15:30 EST FeedZeBirds will release 30% of the company as 30,000 shares on GLBSE, the Bitcoin stock exchange …. A share will be sold at 0.08667 BTC each.”
...
20. As a result of the conduct described above, Voorhees violated Sections 5(a) and 5(c) of the Securities Act, which prohibit the direct or indirect sale of securities, offer to sell or offer to buy securities through the mails or interstate commerce unless a registration statement has been filed or is in effect.
...
Exactly, nothing was wrong with the project itself besides a "rule" not being followed. Other than that, it was quite a successful campaign!I advocate and support development of a new version of FeedZeBirds
It seems that the only 'unlawful' (if that's an accurate term) aspect of the site was the alleged addition (May 2012) to the site of unregulated selling of shares.
From what I've read on the forum here the objective for the new version is really and truly the original purpose of site which was paying/earning for retweets.
Moreover, I wanted to help with development of the new version. However:
(1) I'm not familiar with Drupal
(2) So I started writing some code (php, pdo) based on the original but I soon realized that I should leave this project to more adept coders. I don't want some chance of security vulnerabilities in my code to cost someone (or many persons) their bitcoins.
Regarding managing bitcoins: the best way is to use 2/3 multisig, so that the server cannot possibly spend the bitcoins all by itself. Then, before payment, someone manually checks the transactions that the server creates. Only if these transactions make sense, will payment be done.I advocate and support development of a new version of FeedZeBirds
It seems that the only 'unlawful' (if that's an accurate term) aspect of the site was the alleged addition (May 2012) to the site of unregulated selling of shares.
From what I've read on the forum here the objective for the new version is really and truly the original purpose of site which was paying/earning for retweets.
Moreover, I wanted to help with development of the new version. However:
(1) I'm not familiar with Drupal
(2) So I started writing some code (php, pdo) based on the original but I soon realized that I should leave this project to more adept coders. I don't want some chance of security vulnerabilities in my code to cost someone (or many persons) their bitcoins.
Return to “Bitcoin Discussion”
Users browsing this forum: No registered users and 20 guests