jalfresi

I find it's mostly that posting a comment is very different from entering into discussion. There is a surprising amount of friction attached to entering into a discussion on the web, compared to just lobbing a comment onto a page (like I'm doing right now). Throw in point scoring to comments, and you've created a system that just doesn't appeal to the majority of people.

You get publicly scored on your contributions to the discussion. Most people are turned off by the idea of discussions being adversarial, point scoring, confrontational.

And in that respect, I consider the barriers to comment contribution to be very high indeed.

Yes, and we should all do our part to hold each other up to the standards we expect from this community

"The problem is, you are talking about art. And art is in the eye of the beholder."

Typography is Graphic Design, not art. The goal is usually to impart knowledge to the viewer. A legible message objectively aids in this.

However, typography can tap the viewers knowledge for additional tone, for example, choosing era appropriate typefaces for 100 year old stories.

If you are trying impart an emotion, then post-modernist graphic design may eschew legibility for emotive punch, in which I would agree that it is very much a subjective response, however, I would still argue that it is design, not art.

Totally agree. From the angle of UX and usability, the more closely the interface reflects the internal model of the system, the more accurate the users mental model of the software will be.

>Before regulation locked out any possibility of long term successful competition

from companies willing to exploit loopholes in hard won labour laws whilst putting the health of the general public in danger by exploiting the slow moving mechanism of governance for profit

Transparent plastic?

"I think this is a cowardly and inaccurate belief"

Throughout history you find the people who believe this are not the ones who's safety is sacrificed in pursuit of some grand project...

Agreed this is out of control now! And yet still, 20 years later, I can’t scroll the body of a table whilst keeping the header and columns aligned.

Surely things like that, or a src attribute for csv files, or even rudimentary charts and graphs for tables don’t even get considered.

Suppose fixing 20year old issues just aren’t as sexy as usb access from the browser...

As time goes on I connect less and less with browser developers.

It would be interesting to see some kind map (like the civ tech tree) of which domains share skills

Scraping is how the web works. After all, retweets are essentially manual scrapes

All big problems are composed of smaller problems

You missed the part where the definition of the problem was being percolated during this process. Agile won't save you from not understanding the problem you are trying to solve.

So much this! Some developers don't realise that informing the user of state provides invaluable information in correcting their mental model of the application.

By publishing on the public web?

This my experience too - agile seems to exist because clients and middle management refused to determine and plan exactly what the want developed, preferring to "know it when I see it". Agile encourages this attitude.

There exists an entire industry that provide rotating IPs across fleets of proxies for very cheap prices. Proxy services like this make it pretty much impossible to prevent scraping.

The publisher of the information is ultimately responsible for the disclosure of the information. How it is read is of no consequence, as the information has been provided to be read. Certainly, there are issues about resource usage i.e. heavy readers, such as scrapers, but throttling is a perfectly acceptable approach to overuse of resources for both parties, as access is still available over managed resources.

The nature of the original complaint is authorised access to publicly published information. Again, if you do not want people to read publicly published information, do not publish it publicly.

And as a side note - we don't need inappropriate analogies; the web is real, we can discuss the real issue.

See the first line.

If there is a problem with that, see the second line

So? How does this impact the bike owner in anyway?

Providing the information on a publicly accessible page provides permission. It's like posting a letter on a public noticeboard and demanding that certain people not read it.

If you don't want it read, take it down.

If you post it on a public network, it is defacto, public.

If you don't want it scraped, take it down, or put it behind a login.

If the user provides the login to a scraper, then the scraper has permission.

In my opinion and experience, that is exactly what programs are

"Public Relations" is the rebranding of propaganda

Out of curiosity, does any one know of any research or articles into reputation systems in general?

Sell better tools?

I always thought slashdot had a pretty good moderation system. Would in most cases separate the wheat from the chaff leading to excellent comment threads

You don't see a problem with installing nodes for assets compilation? What is the tech world coming to...

Yup, noped the hell out of there.

Agreed! That actually makes it much more feasible to insert into my current workflow!

Theres a whole section on stored procedures - it was my understanding that the database/sql package in the sodlib didn't support stored procedures (something to do with multiple rows or output var support)