In 1987 he wrote the following preserved article about RELAY and here is his obituary. May this early inventor rest in peace.
Well, part of it is that even a small payment can still incur a psychologically large cost. If each user post here on
Something similar happens when people have metered or capped Internet usage compared to at least nominally unlimited usage.
You really can't avoid this problem unless the micropayment is so small that it is likely not worth the cost to implement. I suppose if I knew that a year's worth of micro payments for me, for everything I use, was no more than about a dollar a year in total, it wouldn't be so much that it would feel like I was wasting money on the Internet. But because the average user doesn't want to spend a noticeable amount ever, and there really aren't that many users in comparison to sites, the resulting pie of money wouldn't be much to split up. (Especially once you reduce the amount to account for lower average incomes elsewhere in the world)
Option 2: Active editors. These forums are cultivated, maintained, and very ban-heavy. As a side-effect, the forum can be held responsible for third-party content.
Not true in the US (other than, potentially, with copyright issues and the like).
Remember, the CDA was intended to encourage providers to engage in censorship. Since the previous state of affairs was as you suggest, the way that they were encouraged to censor was to remove liability for material posted by third parties. But since many sites don't care, and the CDA protects them fully no matter what they do or don't do, it didn't really work out. Also other parts of the CDA turned out to be unconstitutional.
Among the most "oversold as a cure" methodologies introduced to business development teams today is Scrum, which is one of several agile approaches to software development and introduced as a way to streamline the process. Scrum has become something of an intractable method, complete with its own holy text, the Manifesto for Agile Software Development , and daily devotions (a.k.a., Scrum meetings).
Although Scrum may have made more sense when it was being developed in the early '90s, much has changed over the years. Startups and businesses have work forces spread over many countries and time zones, making sharing offices more difficult for employees. As our workforce world evolves, our software development methods should evolve, too.
What do you think? Is Scrum still a viable approach to software development, or is it time to make way for a different way of doing things?
Those who claim the dead never return to life haven't ever been around here at quitting time.