Topic: Devcoin - page 86. (Read 412952 times)

Is it just one share though?

Because jasinlee acted in bad faith proposing that bounty in my opinion.

Why is this such a big deal?

I object.   This project looks to be too trivial, and seems to have been posted by someone who already wanted this and had the means to create it, but just wanted to get a bounty for what they would make anyway.

You are right, it is a trivial site to make.  However, if what you said is true, why would you not have been the one posting it?   Feels way too much like after the fact BS.

I bet you are sorry you did not say that.  You did not say that because you did not think you would get called on it and now you are trying to CYA.    So now you will just say , oh it is not me, it is someone else,  I just happened to post a bounty proposal then the code for it soon thereafter.   

That is also another thing,  you say 'fast on the draw', but the basics of something like this are less then an hours work anyway.  What is the unit of time a bounty of the size you propose should cover in effort?

I think it can be said jasinlee posted the bounty in bad faith. That would be reason to prevent him from claiming the bounty.

ok, snipped for brevity then...

The nodes in one are simply a subset of  two.

Right now there is no DNS seeding done by devcoin let alone DDNS seeding.

The real question to ask right now is if there a desire and will to create and maintain some DNS servers for this type of use.  If the answer is yes, then work on it can commence.  It really should not take too much if is it desired and committed to be maintained.

As for a review of where we are,  the dns seed code has not been used yet.   The first step would be to start to use it.  This may be done as simply as a few dedicated servers that do nothing more then serve a few known good peers.

As for 3, there would be no need to make this easier for the end user unless you simple mean, make this work automatically more reliably.

Tellings users to addnode is actually not making it easier for them.

As for your caution with DDNS,  the risk seems to be no more then the risk with IRC, and since these should be custom DNS servers, logic to reduce this risk can then be considered unlike the existing irc set up.

Where to spend your Devcoins!!!!!
https://bitcointalksearch.org/topic/m.1963632

Post things for sale is ^this^ thread!

You can address your complaints to me, but I didnt write up the script. Gweedo is fast on the draw, sorry he got it done fast and let me know, sorry if I didnt say OH hey gweedo wrote it up in that time in public. I did however let unthinkingbit know ahead of time.

I just started working on a DVC ticker image app after I saw the proposal, and I agree, it is a little disappointing to have started working on this and see you post it so soon after recommending the bounty. I will still try to finish my app and claim the second bounty, and I don't think jasinlee should be prevented from claiming the bounty, but I agree with twobits recommendation - in the future there should be a reasonable amount of time before the person who proposed a bounty can claim said bounty.

http://devtome.com/doku.php?id=wiki:devcoin_price_image

There we go.

Yes, I am very cynical now.   I propose that a reasonably period of time must elapse before such small work bounties may be claimed by the person originally asking for said bounty.  This is assuming the bounties are meant to motivate people to work on things they would not have done anyway.


There is no feature to consolidate posts using the skin I am using at least. And it is irrelvent, smaller replies to the exact post are better.  Post counts are also meaninless and have no value, so there is no incentive to increase such.
I I wanted to increase my post count as a goal, I would have far more then I do, especially given the time I have been on the forum, mr newbie with over 1000 posts.... 

Devcoin Lottery!!

https://bitcointalksearch.org/topic/m.1963466

There's a few things going on - hence trying to clear up things.

1) Nodes
What:
Long standing dvc nodes - ideally placed on fast connections & configured with a large number of connections.

Why:
To allow new & existing clients to bootstrap quickly.  To allow a complete fall-back when other systems aren't functioning.

How:
Coded dns names in the code - that allow cname & a lookups.

2) Locators - client discovery
What:
Review the current infrastructure to ensure it's suitable for scalable growth.  
IRC, DDNS (DNS Seeding), Client cache

Why:
It's good to review where you are and where you're going.
DNS Seeding should be reviewed and checked to see if the current setup is optimal.  DNS Seed names (DNS entries) should be checked & updated - are we using the most appropriate record types, what's the change control process.  As you mention - does it fallback properly should those DNS Seeds be taken out? Can geoDNS be leveraged to help users download the blockchain from their closest neighbours.  Tech has moved on - DNS has improved a lot - with ipv6 more prevalent now - srv & locator records can be used and you have more granular control over the how & what.
geoDNS is now pretty affordable and no longer limited to the big-boys - it can make a huge difference to the blockchain startup/catchup time for end-users.
The existing locators aren't setup to gather & supply metrics - each DNS query, irc join is a statistic that's useful in gauging adoption, growth & measuring scale.

How:
Test, metrics, target goals for how this works.

3) DNS
What:
Using existing DNS names to make config & setup easier & simpler for end users.  

Why:
Long term success in pretty much all things comes down to making something accessible to end users.

How:
Update the way a handful of (1) are recorded in DNS, update the documentation for users telling them they can addnode=dvc.devcoin.me and you'll be up & running in no time.
Using something like dvc.devcoin.me is way easier than 15 addnode=abc.def.ijk.lmn entries when a user is complaining that its taken 20h for their blockchain to be downloaded.


I'm overly cautious when it comes to DDNS because there's risk - it's easy to pollute and as it's a centralised public resource it's an address book of hosts.

I am not the only person that works on the site, unthinkingbit is aware of this also, he handled the coding, but I manage the bounties for that particular person. Cynical much?


Are you trying to increase your post count by creating a new reply to every single post instead of consolidating it into a single post? (/cynicism)

I oppose this bounty,  bitcoin 0.8.1 is the most flakey version of bitcoin I have yet had to deal with.  It is the wrong time to try and make a new base. Perhaps instead say what is missing, it may be simpler and quicker to just add it.

Also it has been said earlier they do not want a dice service running on devcoin... if this is what is keeping those off of it so much the better.

Lol, so you propose a bounty to get someone interested in doing something, then magically post code for the same bounty hours later?

Hello, after struggling with various bitcoin related services, e.g. I've tried to port electrum server or auto dice system from bitcoin to devcoin, at last they all point to the single failure, the too old devcoin code that could not provide needed api or functions.

So here I suggest (if I have this right?) a bounty to port devcoin to newest bitcoin code (says, 0.8.1 or later) for 5 shares (or more),  besides I'd like to add 1share of my own, that is, to donate 1of my share that I will reveive (no matter how many dvcs) at round 23 to the one who win this bounty.

http://devtome.com/DVCImage/

It is not complete yet, but devtome.com will have one of the image dvc tickers on the site now. Tomorrow a generator or something simpler should be available. Examples below:

How to Use DVC price image

It is very easily use the url http://devtome.com/DVCImage////.png

So: http://devtome.com/DVCImage/VIRCUREX/DVC/1/USD.png =

The source will be posted soon too then I will update the thread.