You think writers would make multiple accounts to get around limits but that they won't make clever use of curl and, for example, Tor or open proxies or whatever means they can find to cause pageviews artificially?

Come to think of it, generating pageviews is exatly what auto, as distinct from manual, page-surfing sites are for. I could fire up autosurf.com or whatever it or its hundreds of similar sites are, and sit my browser(s) all night auto-visiting pages one page every five or six seconds, generating pageview credits at 1:2 ratio so for each page any of my browsers (including ones I run in dummy, headless Xwindows on various third party hosting) visits nets half a pageview-credit, those credits being automatically spent to buy pageviews for my devtome pages.

This would have the benefit of increasing the Alexa rating of the devtome, which is the main reason such pageviews are valued, because even though my browsers don't report to Alexa the browsers of a whole lot of people whose browsers my credits pay to have visit devtome will be using Windows, and Windows browsers apparently do report the user's pageviews to Alexa automatically by default.

(Yes, windows browsers are a form of spyware! Surprised, anyone?)

So hmmmm y'know, maybe using autosurfs to up my pageviews wouldn't be the worst way I could do it, Clever use of curl would avoid giving devtome any Alexa-rating boost and still give me lots of pageviews...

I suspect we'd be best off sticking to using advertising, so that the whole problem of figuring out whether the visitors are genuine/valid or not is foisted off to a third party advertising-agency that has staff and routines etc for figuring that stuff out.

If we could get pay per impression ads instead of (or as well as) pay per clickthrough ads we'd still end up getting paid based on pageviews but the work of figuring out if the views are good would be done by a third party. (Or, we'd simply get our adsense account cancelled for having too many fake visitors... Hopefully adsense though would simply only give us pay per clickthrough ads and no pay per impression ones if it only thought our visitors were bogus not our actual clickthroughs...)

This Alexa thing though... Apparently it was valuable once upon a time and might still be valuable. Having a bunch of people run autosurf programs all day and night could get us a ton of autosurf credits we could use to drive Alexa-reporting browsers to devtome pages. Even if no one actually sees the pages, Alexa apparently didn't used to know that and maybe still won't know that.

(I am not up on current state of the art. Autosurfs when last I used them deliberately did not care whether you were actually watching, even though some manual-surf programs that give you credits for spending X number of seconds on a page actually stop the counter while you are switched to another desktop and restart it when you return to looking at your browser. Maybe by now Alexa (maybe with Microsfot's help) has found a way to detect traffic that is driven by autosurfs. Seems not all that likely though else SEO people would not still be using autosurfs to increase their google pagerank by means of increasing their Alexa ratings...)

-MarkM-

That's fine, I just thought it kind of important knowledge. Perhaps there should be a section to put things that are completely excluded from the word count?? I can't change a legal article at all, or it is not the same. As I believe it was you said before, it would be like changing a diary.

But that still leaves my second question.

Why did my name not show up on the script run?

Okay. That sounds good too.

My biggest concern though is why my name is excluded from the count.

Here is a start toward a plan or proposal to drive Alexa ratings.

We make for a few good reliable autosurf programs user-accounts for devtome.

These have multi-level, or at least one level anyway, of "referral credits" systems, so that if these devtome accounts on the autosurfs refer people to the autosurfs, they get a fraction of the credits earned by the people they refer (possibly even multiple levels down the downlines.)

A criteria for which autosurf(s) to use would that they must be ones whose reporting about your referrals reports how many credits each referral earns for you.

We then reward people in proportion to how many pageviews they cause these devtome accounts to earn.

Unfortunately we cannot know what sites or pages they themselves are spending their own credits on, so really this whole plan would be most useful to people who do have some use themselves for Alexa-reporting browser visits.

-MarkM-

 

Thoughts for the use of DNS in dvc.

Suggestion:
(1) Pick a DNS name that will be the root name used by users & the dvc client for resolving seed nodes (long standing core dvc nodes that can help bootstrap new dvc nodes).
(2) Use a DNS provides that's dev friendly, supports round-robin (RR) DNS entries and ideally already has (or plans to implement geoDNS) and under dvc "admin" control.  You don't want to use DDNS (Dynamic DNS) for security reasons and getting into the whole IPSEC DNS is a can of worms.

Why:
Simpler bootstrapping for new & existing users.
Simpler management - host IP addresses will change over time (hosts go down, get moved, etc) - currently this requires a code change.
(2) allows for the load to be distributed & using geoDNS allows for locally served updates - providing a quicker catchup & bootstrap time.

How:
RR DNS entries are DNS A records that map from a hostname to an IP address.
The existing dvc config file can be used with the DNS entries - using addnode one or more times using the dns name from (1)

The dvc client code can be updated to take advantage of the new scheme in a more intelligent way.
In this case - the code does a DNS lookup for all records using (1) - resulting in a number of DNS A records.  Each of these is then used the same way addnode currently works. You can see an example of this using nslookup & using "dvc.public.txn.co.in" where you'll see 2 records returned.

In addition - as it goes through each returned DNS A record:
(a) it checks you have an IP from the lookup (making sure you have an A record & node something else like a cname)
(b) the IP is valid & the host is responding - it records the lookup & the time the lookup happened
(c) every n minutes (driven by the config file or the cli - ala devcoind dns-refresh) it repeats the cycle.  This allows long standing nodes to refresh & reload these addresses without restarting the daemon.

Anything in the original section of the invoice is totalled by the devtome.py script. It does not analyze the source text at all, it only counts the words.


After it was pointed out that there were unoriginal texts, I sent a message to you and WildElf asking who wrote the texts. In the meantime, in order to not accidentally send out shares for unoriginal texts, I removed both of you from the bounty list and the devtome list. Since you removed the article from your original section and posted an explanation, I added you back:
https://github.com/Unthinkingbit/charity/blob/master/bounty_23.csv
https://github.com/Unthinkingbit/charity/blob/master/devtome_22.csv
 

What is the copyright of the original article?


In that case, you could write an opinion about the article.

Not really - we're talking about 2 different things.
I'm talking about replacing the existing hard coded IP addresses with DNS based lookups - these authoritative nodes help bootstrap the rest of the network.
You're talking about the ddns DNS boostrap - which ultimately is a subdomain of the first.  It's a worthwhile pursuit - but requires infrastructure and a balanced distribution to be effective.  One of the reasons for IRC is that there already exists a well distributed network that can be used to leverage bootstrapping.

After I get my shares (or once I know they are for sure coming) I am going to launch a massive campaign for online recognition of Devcoin. I will be posting TONS of ideas here for everyone to use, share and expand on. But I am wondering now if anyone would like to team up as like a "campaign team", once I get my shares

Article from Devtome, LET THE MACHINES DO THE WORK: http://www.devtome.com/doku.php?id=let_the_machines_do_the_work
BTC & DVC for a free society

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/<exchange>/<Base Currency>/<Amount>/<Currency to be converted from>.png

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

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