|
|
Log in / Subscribe / Register

Villa: Why feed reading is an open web problem, and what browsers could do about it

At his blog, Luis Villa muses on the topic of RSS and what can be learned from Google's decision to kill Google Reader. Villa contends that "the widely perceived failure of RSS is not really a failure of RSS, but rather a failure of the user experience of discovering and subscribing to RSS." In other words, Mozilla and other browser vendors have dropped the ball by not treating feeds as "a first-class web citizen", which helps walled-in, proprietary solutions like Facebook and Twitter. Solving the problem is not simple, he admits, but he does float the idea that browsers "provide a minimum viable product for light web users – possibly by supplementing the current 'here are your favorite sites' links with a clean, light reader focused on only the current top headlines".

to post comments

Villa: Why feed reading is an open web problem, and what browsers could do about it

Posted Apr 23, 2013 16:01 UTC (Tue) by theophrastus (guest, #80847) [Link] (45 responses)

"the widely perceived failure of RSS..." will some wise person explain how RSS has failed? the fact that i found this very article via RSS strikes me as notably ironic. (next they'll be saying that lynx "failed"; superseded, to a large degree, sure, but...)

Villa: Why feed reading is an open web problem, and what browsers could do about it

Posted Apr 23, 2013 16:28 UTC (Tue) by dberkholz (guest, #23346) [Link] (3 responses)

This is a good read in that respect.

Villa: Why feed reading is an open web problem, and what browsers could do about it

Posted Apr 23, 2013 17:21 UTC (Tue) by theophrastus (guest, #80847) [Link] (2 responses)

That explains the situation nicely. Thank you! So i'd replace "failed" with something more akin to: "actively neglected", or, "deemed unprofitable". For if it had passively 'failed' then there would be no issue.

By the bye, for those who sensibly judge an aging net denizen as beneath consideration; hoary old NNTP seems to be still be actively with us, and not -entirely- as a means to transmit contraband.

Villa: Why feed reading is an open web problem, and what browsers could do about it

Posted Apr 23, 2013 18:52 UTC (Tue) by khim (subscriber, #9252) [Link]

By the bye, for those who sensibly judge an aging net denizen as beneath consideration; hoary old NNTP seems to be still be actively with us, and not -entirely- as a means to transmit contraband.

That's how software is failing: it does not disappear overnight. I know many places where people still use old Turbo Pascal 3.01A-based programs. And PDP-11 (emulated in Itanium which soon will be emulated on something else, I guess). But as far as "Joe Average" is considered RSS is as relevant as Gopher (slightly more relevant then Multics in 2000, but not by much).

Villa: Why feed reading is an open web problem, and what browsers could do about it

Posted Apr 23, 2013 20:35 UTC (Tue) by tsmithe (guest, #57598) [Link]

I actually use NNTP all the time to read RSS feeds, via gwene.org (as well as mailing lists via gmane.org), so I must be amongst a very select group of dinosaurs. But it's hard to deny the power of Emacs (and Gnus, etc) once you've really tried it.

Relative failure

Posted Apr 23, 2013 16:38 UTC (Tue) by pboddie (guest, #50784) [Link] (2 responses)

I think he means failure as in not hugely succeeding like social networking technologies, where adoption of those services in terms of authors/producers and readers/consumers is significantly higher than for RSS.

He has a point about it being more awkward for people to use RSS, although Firefox did at one point support "live bookmarks" for RSS, and so there was some thought put into supporting RSS, even though it then suffers from all of the problems that the bookmarks paradigm suffers from inherently (like the incredibly poor management tools for bookmarks in browsers).

For authors, producing RSS-accessible content is also not as straightforward as the social networking services make it, but that's just a manifestation of the general hosting problem: most people will just choose the brand name service that everyone else they know has chosen, especially if that service makes it very easy to share content.

Having to make a conscious decision to find a content hosting provider, sign up for it, learn how to use it, and then find out that it doesn't automatically integrate with the output of the people you want to follow yourself makes for a more complicated and less attractive experience for most people.

None of this is really a problem with RSS, but it shows that people have to build "Open Web" services and not just point at the existence of technologies as proof that everyone's needs are already covered.

Relative failure

Posted Apr 23, 2013 18:50 UTC (Tue) by oever (guest, #987) [Link] (1 responses)

The Firefox extension 'Brief' which is a very nice RSS reader.
http://brief.mozdev.org/

Brief is great

Posted Apr 27, 2013 13:36 UTC (Sat) by CChittleborough (subscriber, #60775) [Link]

Brief is a very good feed reader. It does not have all the bells and whistles of some standalone readers, but it does everything that I want, and does it well.

Villa: Why feed reading is an open web problem, and what browsers could do about it

Posted Apr 23, 2013 16:43 UTC (Tue) by davide.del.vento (guest, #59196) [Link] (4 responses)

If you read the original article, you should understand. And if you don't understand, then you might be living in a happy, parallel universe. Don't take me wrong. I've found this very article via RSS (in the soon-to-be-decommisioned Google Reader, by the way). But let me summarize this for you and for the happy people living in that happy parallel universe.

RSS (in the broad sense of "open web technologies such as RSS, Atom and others") has been designed to create a stream of updates for us, the reader, to subscribe things and make it easier to read the updates. It works like a charm.

However, it has been not superseded, but neglected and killed by internet giants such as Facebook, twitter, and now even Google. Why? Simple: it's better for them to lock you in their social networks and treat you as "their lunch". Everything you can do in FB, tw, g+ you could have been done in RSS (yes even circles and private posts). However in that way you would not have been locked in any single vendor. Most of these feature (especially the private ones) are hardly supported in feed readers. Villa claims that part of the reason is browser inaction on the field. I agree.

Look how even big brands nowadays dilute their brands on FB (and to lesser degree on g+). It's very sad. I don't use FB nor twitter, and I am contemplating to unsubscribe from g+. Every day I stumble in things that I have to read on FB or twitter or g+. And that is increasing. Maybe you don't care, but that's very bad for the open web.

I see the same fate for email. Google redefined email with gmail. It's arguably much better than any other email client I tried (open or closed, local or hosted). See http://blog.bytemark.co.uk/2013/04/17/geary for the tip of the iceberg of this related discussion.

Independent hosting

Posted Apr 23, 2013 16:53 UTC (Tue) by pboddie (guest, #50784) [Link]

It's interesting to see independent hosting providers wake up to their own decline and potential demise, although I can easily imagine that many of them would rather cut a lucrative deal with a big name and get out of the business than do the right thing and support open standards and services.

Similarly, a significant threat to the big names of social networking actually comes from the proliferation of mobile devices, but instead of positioning themselves to offer services supporting open communications standards, it's almost a certainty that mobile operators will refuse to invest in such things and instead make themselves a mere pipeline for big name services, with a nice retainer fee making its way back to the operator as thanks for herding the masses.

Why bother doing the right (and potentially more rewarding) thing when the low-risk option keeps the revenue coming in indefinitely?

I don't use gmail

Posted Apr 23, 2013 19:15 UTC (Tue) by dps (guest, #5725) [Link] (2 responses)

As a user of gpg I definitely don't think gmail sounds like a good idea and given my not-very-broad band connection I suspect the performance would be awful. Telling google my private key and pass phrase would be a really bad idea.

I currently use thunderbird, with the enigmail plugin, and can't find huge amounts missing modulo some difficulties using the search to find that email I received some time ago.

I don't use twitter and sites like FB, linked-in, etc ask for personal information I don't want to share. IMHO just not putting that information on the internet is far more secure than using FB privacy settings. Is this approach just out of date?

I also don't feel the need for what RSS provides. I am aware that some streams of updates which might cost you money are atom feeds.

I don't use gmail

Posted Apr 23, 2013 22:59 UTC (Tue) by b7j0c (guest, #27559) [Link] (1 responses)

what does gpg have to do with gmail? do you actually think email can be secured?

I don't use gmail

Posted Apr 23, 2013 23:12 UTC (Tue) by Wol (subscriber, #4433) [Link]

It's not necessarily *securing* email. It's also *signing* email.

There are occasions when I want people to KNOW FOR CERTAIN that it's me that sent that email. It's plain text, it can be snooped, it's not secure. BUT. It can only have come from me, because only I know the pass-phrase for the signature.

Cheers,
Wol

Villa: Why feed reading is an open web problem, and what browsers could do about it

Posted Apr 23, 2013 18:40 UTC (Tue) by tpo (subscriber, #25713) [Link] (32 responses)

> ... the fact that i found this very article via RSS ...

Woah, thank you theophrastus bombastus, I did not know! Now I am happily subscribed to LWN via RSS. And, through reading the other comments and links here I discovered that I actually *can* have Firefox display the RSS icon when there's a feed. And indeed most pages I look at *do* have a feed!

What a happy RSS day! Long live RSS!
*t

PS: Lately I am getting the impression, that even though Google is innovating hard, whenever it puts down its foot somewhere, it immediately kills the whole ecosystem there (oh, how similar to ex-Microsoft). And as soon as Google moves on, judging the $$$$ extraction ratio from the surviving/remaining inhabitants not high enough, the niche is quickly repopulated by many a new, colorful, alternative creatures.

Villa: Why feed reading is an open web problem, and what browsers could do about it

Posted Apr 23, 2013 19:14 UTC (Tue) by khim (subscriber, #9252) [Link] (31 responses)

Lately I am getting the impression, that even though Google is innovating hard, whenever it puts down its foot somewhere, it immediately kills the whole ecosystem there (oh, how similar to ex-Microsoft).

The depressing thing here is the fact that Google usually does not try to actively kill an existing habitats. Usually it tries to be quite friendly to its competitors (unless these are titans like Facebook or Microsoft), but this just means that where Microsoft destroys competitors in hurry with a lot of racket and ill-will Google destroys them slowly but silently yet just as surely (usually when victim finally declares "kaput" the general public reaction is "huh? ___ was still around all that time?).

This is depressing because for Microsoft's behavior there is an answer: "stop using illegal means and everything will be fine!", but what can Google do? Purposefully make it's own product worse? Stop innovating and trying to expand into a new niches? Makes no sense whatsoever.

Villa: Why feed reading is an open web problem, and what browsers could do about it

Posted Apr 23, 2013 19:56 UTC (Tue) by davide.del.vento (guest, #59196) [Link] (20 responses)

What can Google do? Well, for example (to stay on the topic of feed reading) donate the code of Google Reader to Apache (or other entity of their choice) as they did with Google Wave.
Google Reader is (was) by far the best feed reader ever. By far. That killed competition. Then, as articles linked in this comment thread mention, Google slowly nudged users from using Reader to use Google Plus. Now they are killing Reader completely. I don't believe they are doing just to save the few bucks of the infrastructure costs and software maintenance. I believe they are doing it to fully kill RSS and not give users any other option than using Plus.

Take gmail as another example. Google innovated email greatly. The idea of labels instead of folders is great and a serious game changer. Ditto for conversations (not the fakey conversations that thunderbird has). What should they do? Push to standardize their innovations when appropriate, for example in IMAP. If I access gmail via thunderbird I end up having duplicate messages (if they have several different labels, they end up being several copies in each different folder), and a reply does not automatically "resurrect" the whole thread of conversation, but I'm stuck with searching it manually (and good luck with the awful searching capabilities of thunderbird). They can still keep the edge in (say) better user interface, faster search response because of their large server farm, more relevant search because of their autocomplete and spelling corrections and so on. But they should foster interoperability, which they don't.

Villa: Why feed reading is an open web problem, and what browsers could do about it

Posted Apr 23, 2013 23:20 UTC (Tue) by b7j0c (guest, #27559) [Link] (10 responses)

if the internet community truly embraced rss, google would not be able to kill it. no one forced the community to see google reader as an entitlement. nor gmail. i'm also puzzled by your suggestion that gmail needs to be part of a standard. it already is. imap. show me where in the imap standard it say you can't abstract the storage model (tags etc) in the interface if users derive value from it. the fact that users have embraced imap+proprietary-features clearly tells us no one really cares about vanilla imap compliance as a selling point in the grand scheme of things.

Villa: Why feed reading is an open web problem, and what browsers could do about it

Posted Apr 24, 2013 3:47 UTC (Wed) by dlang (guest, #313) [Link]

users have hardly embraced IMAP by itself, let alone with proprietary features added.

Villa: Why feed reading is an open web problem, and what browsers could do about it

Posted Apr 24, 2013 4:27 UTC (Wed) by raven667 (subscriber, #5198) [Link] (8 responses)

You are touching on related issues but the fact that you can access Gmail via IMAP is not relevant to the point which was being made because you can't modify tags or control it's unique and proprietary features through IMAP or other standards based protocols. The web interface may be made out of standards compliant components but a web interface is not a protocol or API that can be standardized. Other attempts to build a similar feature set are likely to be equally proprietary and unsuitable for standardization.

Villa: Why feed reading is an open web problem, and what browsers could do about it

Posted Apr 24, 2013 6:18 UTC (Wed) by jrn (subscriber, #64214) [Link] (7 responses)

You can modify a gmail message's tags (labels) through IMAP, actually. To add a label, save a message to a folder of that name. To remove a label, delete it from that folder.

Villa: Why feed reading is an open web problem, and what browsers could do about it

Posted Apr 24, 2013 16:09 UTC (Wed) by davide.del.vento (guest, #59196) [Link] (6 responses)

That wasn't the point. The point is that:

1) via IMAP messages with multiple tags (label) appear as copies, which is a pain for storage, for searching, for sorting etc.

2) via IMAP an incoming message which is reply to an existing one does not "bring" the whole conversation back to inbox and therefore the context must be manually searched and because of 1) that search is a big PITA

Villa: Why feed reading is an open web problem, and what browsers could do about it

Posted Apr 24, 2013 17:15 UTC (Wed) by paulj (subscriber, #341) [Link] (5 responses)

I don't know if you mean IMAP generally, or just "Gmail via IMAP", but IMAP generally you can easily have 1 view of both sides of the conversation - just configure your IMAP client to put the sent mails in the Inbox. This is how I have my mail configured (one hosted on an Exchange server, no less).

Villa: Why feed reading is an open web problem, and what browsers could do about it

Posted Apr 24, 2013 18:36 UTC (Wed) by davide.del.vento (guest, #59196) [Link] (4 responses)

Ok, let's be concrete with an example.

You send me what you've just written here as an email, to my gmail account.

I put it under 3 different labels, say "lwn", "gmail", and "discussion". I reply "thanks" and archive it, since I try to keep in inbox only stuff that require my action. Three months from now you reply to that message again and tell me something new you've discovered about the topic. If I use gmail's web interface, the whole conversation pops out in my inbox, with all the three different labels attached to it, giving me the full context of what has been discussed previously and the full categorization ("lwn", "gmail", and "discussion") in which I archived it. Of course 3 labels for this simple message is overkill, but often time it's very useful.

Now try to replicate this in an IMAP server of your choice with an IMAP client of your choice other than gmail web interface. The best I've been able to achieve is:
a) categorize the message with COPIES, having 3 different copies of the message in 3 different folders
b) when your reply arrives, I search, wait *an extremely long time* (each of my personal and professional email contains several GB of data and several tens of thousands of messages), and if I'm lucky I find the 3 copies, and I'm able to remember the context and categorization, but not automatically and not in place (I have to open other 3 or 4 windows to achieve what is right in front of me in one line in the gmail web interface)
c) I have to continue to copy your new messages three time. Plus, sometimes I'm in a hurry and forget one of the copy so in the future some context may be lost

I would be extremely happy to be proved wrong and have an IMAP server and/or IMAP client which is able to solve this extremely painful workflow which I am inflicted several dozens of times a day for my non-gmail correspondence. Even solving just "half" of the problem (the automatic conversation popping or the duplication avoidance) would be extremely useful. Thanks!

Villa: Why feed reading is an open web problem, and what browsers could do about it

Posted Apr 24, 2013 20:06 UTC (Wed) by mathstuf (subscriber, #69389) [Link] (2 responses)

> Now try to replicate this in an IMAP server of your choice with an IMAP client of your choice

As long as the Message-Id headers align (which, IME, pretty much everything except some phone clients do properly), notmuch can do this. As a mutt macro from my config:

> macro index <F9> \
> "<enter-command>unset wait_key<enter><pipe-message>notmuch-mutt thread<enter><change-folder-readonly>~/.cache/notmuch/mutt/results<enter><enter-command>set wait_key<enter>" \
> "search and reconstruct owning thread (using notmuch)"

notmuch is supposed to be able to handle GB's of email as well. Of course, this loses which labels the original messages had, but an RFE for notmuch to add headers for X-Original-Directory to the messages it finds wouldn't be bad.

Villa: Why feed reading is an open web problem, and what browsers could do about it

Posted Apr 24, 2013 20:35 UTC (Wed) by davide.del.vento (guest, #59196) [Link] (1 responses)

Thanks for the suggestion. I did not know about notmuch [1]. I'll see if I can achieve what you said in thunderbird using notmuch and I might become very happy.

However, it's very sad that I cannot suggest this geekly and convoluted setup to my mother, whereas she's happily using gmail.

[1]: if anyone else reading is wondering and does not have time to learn more: from http://notmuchmail.org/
Notmuch is not much of an email program. It doesn't receive messages (no POP or IMAP support). It doesn't send messages (no mail composer, no network code at all).

It just does email search (from local files, I guess).

Notmuch

Posted Apr 24, 2013 23:22 UTC (Wed) by corbet (editor, #1) [Link]

I played with notmuch a few years ago. Things have evolved considerably since then, though; getting back to it has been on my list of things to do. If only I didn't have to buy another 1TB disk just to store the to-do list...

Villa: Why feed reading is an open web problem, and what browsers could do about it

Posted Apr 28, 2013 22:19 UTC (Sun) by foom (subscriber, #14868) [Link]

Apple Mail can display all messages of a thread, even across folders, via a preference "Include related messages", which is what I think you mean by "conversation popping".

That should be a trivial feature for any client with a local mail database to implement.

Villa: Why feed reading is an open web problem, and what browsers could do about it

Posted Apr 24, 2013 8:44 UTC (Wed) by khim (subscriber, #9252) [Link] (2 responses)

What can Google do? Well, for example (to stay on the topic of feed reading) donate the code of Google Reader to Apache (or other entity of their choice) as they did with Google Wave.

You are overestimating amount of code in Google Reader by far. Most of the code resides in BigTable, Colossus, Mustang and other proprietary infrastructure. That was greatest strength of Google Reader (not much code exist solely for the benefit of Reader) and this is also what made it so vulnerable (you can not leave service based on GFS running if GFS itself is scheduled to be killed). The glue code on top is not of much interest for Apache or anyone else: these are some [relatively simple] scripts, not much more then that. It's all highlighted in Google Reader's creator article.

And this is not a solution for the initial problem, anyway: the question is not "how to live in the wasteland where Google Reader decimated the competition", but "how the read-headed stepchild of Google which was never loved by it's parent (if we'll believe Chris) decimated the competition in the first place?". That is the problem. You can be sure that projects which Google perceives as "core" (like, ugh, Google+) will not be abandoned on a whim, but projects which they only reluctantly provide can be discarded easily - but disbandment of such projects should not have such a huge impact! That is the problem!

IOW: how come we even miss Google Reader in the first place? It was not something Google pushed aggressively at the expense of competitors (truth being said it was really hard to discover it on Google's properties) yet somehow it managed to wreak the whole "ecosystem" thoroughly anyway...

Ditto with GMail: it's just a mail client for the god's sake! If people want/need some additional extensions to IMAP to better interoperate with GMail servers, then they can propose an interface and Google will then adopt it. Google does not have any offline readers so how can they know which way to extend IMAP to better serve Thunderbird?

Villa: Why feed reading is an open web problem, and what browsers could do about it

Posted Apr 24, 2013 14:03 UTC (Wed) by Cyberax (✭ supporter ✭, #52523) [Link]

Except we are now left to wonder what projects are considered 'core'. Google Wave got canceled, Postini (a paid service!) got canceled and so on.

In future, I'm going to avoid most of Google stuff not related to the Google or Google Docs.

Google is just not trustworthy enough.

Villa: Why feed reading is an open web problem, and what browsers could do about it

Posted Apr 24, 2013 16:06 UTC (Wed) by davide.del.vento (guest, #59196) [Link]

Thanks for the links. These helped and were interesting.
However the bottom line is what Cyberax said above: I don't trust Google anymore and I'm actively flying all its services as much as I can.

Now, about your questions about "why that happened in the first place", the answer is very simple to me. Google products are extremely well done, extremely available, reliable and user friendly. And free (ok, as in beer, but the free as in speech is losing momentum and I say that as FSF member), and available to Linux users (just to stay on topic on LWN), and the list could go on...

Take GMail: it's not just a mail client: it's client and server. I've been using it daily since January 2005, for an average of 8 hours a day (granted, not staring at it for 8 hours a day, but keeping it open and using it). My account has been down only once, for only 20 minutes and it was the day and the time of the terrorist attack in London (July 2005) and of course I was in Europe.
Conversations and Labels are also big innovations simply unavailable in other clients or servers.

Sure, some people might not like (or might not care about) some Google products and/or features, but the vast majority does. And that is how *that* happened: by offering great products that the vast majority liked, available in the browser with technologies open to Linux users, for free. Really, how could have a decent competition survived?

Villa: Why feed reading is an open web problem, and what browsers could do about it

Posted Apr 24, 2013 13:46 UTC (Wed) by mathstuf (subscriber, #69389) [Link] (3 responses)

> Ditto for conversations

Really? People who know what proper threading is (I'm presuming here, but it's LWN) like that? I have a bunch of emails where one person kept using the same subject for everything and GMail collapsed all of them together. Not to mention Bugzilla threads being split because the first message has "New: " in the subject that replies don't. That's not really helpful. I actually have conversation view off because it's better than dealing with GMail when it is wrong. Granted, I use mutt 99% of the time where people breaking threads is annoying (usually broken phone clients), but at least this is fixable by adding some headers and informing the offender that their email client has a bug (that might actually get fixed).

Basically, I believe that GMail and Google Groups have been weaning people off of good email etiquette (top posting, not trimming replies, replying to the most recent message rather than the most appropriate one, etc.) and other clients are just following suit.

Villa: Why feed reading is an open web problem, and what browsers could do about it

Posted Apr 24, 2013 16:26 UTC (Wed) by davide.del.vento (guest, #59196) [Link] (2 responses)

Sure, I love the conversation view and the labels in gmail. The fact that conversations sometimes don't work is a pain, but that's not a reason not to use it. To me your argument sounds like: I'd like to use the car, but sometimes I got a flat tire and therefore I'm not gonna use it. Well, at least for me, since my roads are paved and clean, so I get a flat only occasionally. If your roads are unpaved and full of spike strips, well, I understand, but that doesn't automatically make cars useless to the rest of the world.

On etiquette, that is pretty dependent on the social context: in some countries it is considered rude to shake the hand of your aunt instead of kissing her on both cheeks. In the same countries it is considered rude to kiss your boss on both cheeks instead of shaking her hand.

In fact in business top posting and not trimmed replies are the *right* and *polite* way to reply, see http://en.wikipedia.org/wiki/Top_posting#Top-posting
GMail has no fault for that: they had to pick one default and they picked it according to the "being rude with your boss is more serious than being rude with your aunt" which seems a pretty sensible way to do it.

Villa: Why feed reading is an open web problem, and what browsers could do about it

Posted Apr 24, 2013 19:54 UTC (Wed) by mathstuf (subscriber, #69389) [Link] (1 responses)

> The fact that conversations sometimes don't work is a pain, but that's not a reason not to use it.

In general, this is true, but for me it's wrong enough that the pain is a strong enough reason to not use it.

> To me your argument sounds like: I'd like to use the car, but sometimes I got a flat tire and therefore I'm not gonna use it. Well, at least for me, since my roads are paved and clean, so I get a flat only occasionally. If your roads are unpaved and full of spike strips, well, I understand, but that doesn't automatically make cars useless to the rest of the world.

I didn't say that *no one* should use the web UI. It doesn't work for me because I don't "live" in my browser, but rather tmux[1], so using a web UI is pretty much a really big negative to start there. I do, however, set the web UI up to be as minimally annoying for when I do have to use it (someone else's system, phone for $DAYJOB email, etc.). It does take something pretty urgent/special to get me to not go to mutt rather than the web UI though (especially now that offlineimap can create remote directories).

> On etiquette, that is pretty dependent on the social context

That's true, so let me then set which to use based on the recipient(s). Mailing list? Bottom post non-HTML. Boss? Top-post non-HTML. Arch enemy? HTML without plain text and no In-Reply-To headers and a different subject while I'm at it.

> In fact in business top posting and not trimmed replies are the *right* and *polite* way to reply

Not everyone is using GMail in that context. In any case, I haven't seen anyone take issue at $DAYJOB with me trimming and replying interleaved to date.

[1]I have some long-lived browser windows, but they're usually just "haven't gotten to it yet" rather than semi-permanent bookmarks as I see a lot of people (ab)use tabs. Other than that, I have at most 1 browser windows open.

Villa: Why feed reading is an open web problem, and what browsers could do about it

Posted Apr 25, 2013 7:43 UTC (Thu) by dlang (guest, #313) [Link]

> In any case, I haven't seen anyone take issue at $DAYJOB with me trimming and replying interleaved to date.

I have, repeatedly, by multiple managers at multiple levels.

There is even some sense to it.
Top posting with no trimming gives the most recent (and hopefully most relavent and correct) information immediatly with no scrolling, but the rest of the thread is available if they want/need more information.

For management that gets far too much e-mail and has far too many things to try and get done, this is valuable.

However, when having a technical conversation with someone, trimming irrelevant (or incorrect) sections out, and replying point to point, interspersed so that the context of the reply is clear, can be incredibly valuable.

The key is figuring out what audience you are dealing with and formatting the message appropriately.

Villa: Why feed reading is an open web problem, and what browsers could do about it

Posted Apr 25, 2013 6:02 UTC (Thu) by AndreE (guest, #60148) [Link] (1 responses)

I guess you have never looked at the Gmail APIs and IMAP extensions.

https://developers.google.com/google-apps/gmail/imap_exte...

Labels are implemented in a way compliant with official IMAP functionality, and this documentation has been available for over 2 years. That your mail client doesn't utilise these extensions properly is not the fault of Google. Have you even raised a feature request with Thunderbird to implement labeling properly?

Villa: Why feed reading is an open web problem, and what browsers could do about it

Posted Apr 25, 2013 8:22 UTC (Thu) by bosyber (guest, #84963) [Link]

Thanks, I have added looking into that to my todo-list ;)

Villa: Why feed reading is an open web problem, and what browsers could do about it

Posted Apr 24, 2013 23:45 UTC (Wed) by tpo (subscriber, #25713) [Link] (9 responses)

khim wrote:
tpo wrote:
Lately I am getting the impression, that even though Google is innovating hard, whenever it puts down its foot somewhere, it immediately kills the whole ecosystem there (oh, how similar to ex-Microsoft).
The depressing thing here is the fact that Google usually does not try to actively kill an existing habitats. Usually it tries to be quite friendly to its competitors (unless these are titans like Facebook or Microsoft), but this just means that where Microsoft destroys competitors in hurry with a lot of racket and ill-will Google destroys them slowly but silently yet just as surely (usually when victim finally declares "kaput" the general public reaction is "huh? ___ was still around all that time?).

This is depressing because for Microsoft's behavior there is an answer: "stop using illegal means and everything will be fine!", but what can Google do? Purposefully make it's own product worse? Stop innovating and trying to expand into a new niches? Makes no sense whatsoever.

Even though I had thrown down the gauntlet, and you picked it up, I had hoped somebody else would take it up to reply in depth. I'll try now but I'm hardly apt to give you a thorough analysis. In the following whenever I say Google I'll also mean the people that work there.

First: "with great power comes great responsibility". This has many aspects:

For one, once you get to be a monopoly, as Google is in many respects (or maybe rather is the hub), legal free market rules stop to apply to you and the law will (should) be looking at you with extra scrutiny. Rightfully so.

The way that Google or Googlers talk - your post above is a good example - is as if they were not a monopoly. But Google is not naive. They own the most brilliant tech minds so it's out of question, that Google wouldn't know this absolutely well. So why do they talk as if they wouldn't be one with all the consequences that has?

I am stricken by the fact that in many a bright mind's public critical thinking, once she would start working for Google, Google would suddenly be excluded from being critically looked upon.

Take Tim Bray. Before starting to work for Google, I had the impression, that he had quite clear open source principles. The moment he was with Google, any critical mention of Google or its extremely ambiguous relation with open source had completely disappeared.

Take Steve Yegge. His tongue is extremely sharp. But Google is never his target directly. His meant to be internal only posting on Google seemed to cause him a lot of distress.

Why is that? Is the land of the 72 virgins you get to once you are accepted into Google that alluring that you instantly selfcensor out of fear of withdrawal of that drug?

Or is Google so afraid of any self criticism that it all but draconically prohibits any such open utterance? Your own generous but mercyles big brother with his firm hand on your shoulder?

Or is there some rules that says criticism is OK, but it has to remain inside the Famiglia? At which point you are part of the Famiglia and anybody outside isn't (that must be producing very powerful dilemmas of loyality).

Certainly the most powerful usage of critique is to take it as a source for improvements. So it would be absurd if Google would not encourage critique?

I am aware that human nature and by extension corporate nature doesn't take critique easily and thus, its dosage has to be well adjusted in order to be constructive. Nevertheless, it feels like some psychological blocking mechanism is active at Google.

Is maybe Google's schizophrenic relation to the world the cause for that (alleged) cognitive dysfunction (it's own misperception of being a good, non-monopolistic, non-evil company)?

I am under the impression that in its beginning Google was actually saying that it would not be collecting personal information but instead exclusively statistical ones. That is not so today. Google's greed for data correlation seems to be insatiable. It's clear as the sun to every hacker, that this huge collection of personal data is a ticking, distressing timebomb that will explode with statistically 100% probability. In the end it's the worth of the data that determines the effort for the attack and the data only keeps growing. There have allready been casualities but those we know of were "only somewhere remote in China".

As the Safary incident and the WLAN sniffing showed, Google's lust for data is so big, that it will even break your system and collect data even if is very clearly illegal.

My whole defence system - RefControl, RequestPolicy, Cookie Monster, NoScript, blackholing via /etc/hosts - is 99% in defense against Google. There's hardly any web site on earth any more that doesn't dutifully funnel all your movements on the web back to Google.

To me this is a schizophrenic situation: Big Brother is watching you everwhere on the web and it says it is your friend.

I slow down here and pick up from where I started. You said:

The depressing thing here is the fact that Google usually does not try to actively kill an existing habitats.
You are right. That's not Google's goal. Google's goal is to know every one of your moves. So if Google sees a fresh field of data, grazed by amateurs, then that's an opportunity. Sure it will not be evil for the sake of it. On the contrary, Google will not be rude (except sometimes - WLAN, Safary...). And the strategy to enter and take over a field that is allready established is evident: embrace and extend. That's what Google did with Gmail. That's what Google did with Google Reader.

I note that this does not have to necessarily be a conscious "takeover" strategy, but again, I doubt that Googlers can really be this naive not to be aware of the mechanism in action:

If even a small group of Googlers decides to dedicate their 20% of hobby time to some pet project, then allready their combined resources might be higher, than most but the very largest of the existing open source projects. So how are those smaller projects supposed to be "competing" with Google? Why should those smaller projects be competing with Google if it has way better infrastructure, more dev ressources, a product that extends and improves on the existing, can integrate the product with its other offerings, has the brightest minds and the cost is zero? Why should the community except for the stubborn ones and the fundamentalist idealists not leave the field?

The fact that it's a fun or a hobby project does not exclude you from the "with great power..." context.

But that's still not everything. Those pet projects might ascend to higher levels and of course Google has people that are thinking about strategy and induce from those strategic products. So when some pet projects gets promoted or when decisions are made about which projects to keep and which to abandon, ways of moving the userbase off to those strategic products are being thought out.

Now if you go back and compare all this with that article dberkholz had linked to it's exhilarating how it matches my fantasizing here down to the "But I'm now a Google employee and won't comment further".

At this point I'll cut my argumentation and say that I actually do not doubt the Googlers' good intentions to make the internet and the world a nicer place to be. Theirs is certainly not a cynic approach. But the schizophrenic reality fade out needs to be dealt with somehow. I don't know how. Being a monopoly means that the company and its products are in a way a "public infrastructure". The huge looming data breach and potential of corruption and total control and the secret data hustling screams for democratic oversight. In the end giving the user something and not openly telling him about what he'll have to pay in exchange is a lie. I think that is the root of all the resulting evil. People need to be fully aware of what they are getting into. Any way of exploiting this unawareness for your own goals and profit is in the end a deceit.

That's it. It's way too long, but I think it needed a couple of arguments to do justice to the breadth of the problem. Now you can with pleasure rip all my arguments to shreds.

Villa: Why feed reading is an open web problem, and what browsers could do about it

Posted Apr 25, 2013 7:49 UTC (Thu) by dlang (guest, #313) [Link] (8 responses)

> and the WLAN sniffing showed, Google's lust for data is so big, that it will even break your system and collect data even if is very clearly illegal

Just picking on one obvious thing. If you broadcast something over the radio in cleartext, it should not be (and almost never is) illegal to listen in to the radio signal.

Doing so is not "breaking your system", it's just passive listening

The idea that you can get security by outlawing listening is just silly.

Villa: Why feed reading is an open web problem, and what browsers could do about it

Posted Apr 25, 2013 20:52 UTC (Thu) by bronson (subscriber, #4806) [Link] (3 responses)

If only that were true. Dish Network offers heavy precedent that you actually can not do whatever you want with the electromagnetism that's beamed freely through your property and your body.

There are other examples (like cell phone monitoring) but that's even more complex.

Villa: Why feed reading is an open web problem, and what browsers could do about it

Posted Apr 25, 2013 22:46 UTC (Thu) by dlang (guest, #313) [Link] (2 responses)

cell phone monitoring is an example of silly laws making people feel safe while actually adding next to zero security

Dish and Direct TV have encryption on their broadcasts, you can't do anything with them without breaking the encryption (which is illegal due to the DMCA)

But, with the exception of the special cell phone law, what other law makes it illegal to receive something that's broadcast without encryption?

Villa: Why feed reading is an open web problem, and what browsers could do about it

Posted Apr 25, 2013 23:18 UTC (Thu) by jimparis (guest, #38647) [Link] (1 responses)

> But, with the exception of the special cell phone law, what other law makes it illegal to receive something that's broadcast without encryption?

I don't think there's a "special cell phone law". But FCC has a blanket regulation against eavesdropping: (47 CFR 15.9)

§ 15.9 Prohibition against eavesdropping.
Except for the operations of law enforcement officers conducted under lawful authority, no person shall use, either directly or indirectly, a device operated pursuant to the provisions of this part for the purpose of overhearing or recording the private conversations of others unless such use is authorized by all of the parties engaging in the conversation.

I'm sure some clever lawyer could argue what "conversations" means. But if that doesn't cover it, there's always the Electronic Communications Privacy Act (18 USC § 2511), which is long and complex, and prohibits listening in on all sorts of radio and other transmissions, but also has long lists of exceptions, so you'd have to consider specifics I suppose.

Villa: Why feed reading is an open web problem, and what browsers could do about it

Posted Apr 26, 2013 0:14 UTC (Fri) by dlang (guest, #313) [Link]

scanners have been legal for decades. The laws changed around 20 years ago to make it illegal to sell a scanner that could receive the 800MHz cell phone range (I was working at Radio Shack at the time, so we saw the changes come through, and the rush for old scanners that weren't limited, the stupid thing is that since this limitation only affects scanners sold in the US, every manufacturer designed this as an optional feature, with a jumper on the circuit board to impost this restriction, so just cutting a jumper re-enables it on just about every scanner manufactured)

Villa: Why feed reading is an open web problem, and what browsers could do about it

Posted Apr 25, 2013 21:04 UTC (Thu) by bronson (subscriber, #4806) [Link]

Oh, maybe you're only taking issue with "breaking your system". I suppose Khim is referring to the Safari incident which I think matches that description pretty well. See http://techatftc.wordpress.com/2012/08/09/google/ on overriding Safari’s cookie controls.

Villa: Why feed reading is an open web problem, and what browsers could do about it

Posted Apr 27, 2013 20:07 UTC (Sat) by khim (subscriber, #9252) [Link] (2 responses)

It's really funny how you've answered your own questions and never even noticed that. It's try to show you.

In the following whenever I say Google I'll also mean the people that work there.

First: you implicitly equate "Google's position" and "Googler's position".

My whole defence system - RefControl, RequestPolicy, Cookie Monster, NoScript, blackholing via /etc/hosts - is 99% in defense against Google.

Then: you explain how much you don't like to air your dirty laundry.

I am stricken by the fact that in many a bright mind's public critical thinking, once she would start working for Google, Google would suddenly be excluded from being critically looked upon.

And after that: you they you are shocked to find out that Google does the same?

I am aware that human nature and by extension corporate nature doesn't take critique easily and thus, its dosage has to be well adjusted in order to be constructive. Nevertheless, it feels like some psychological blocking mechanism is active at Google.

Nope. The very fact that anything you say may be perceived (and often will be perceived) as Google's position, not your own position means that it's not a good idea to share your opinions publicly. Add the fact that internally Google is extremely transparent (which means that Joe Average Googler knows significantly more about Google then Joe Average IBMer knows about IBM or Joe Average Microsofter knows about Intel) and it's easy to see why Googlers tend to avoid talking about Google as precaution. It's analogue of your blackholing via /etc/hosts, really.

I am under the impression that in its beginning Google was actually saying that it would not be collecting personal information but instead exclusively statistical ones.

Where this strange idea comes from? Google's mission was, is and for the foreseeable future will be the same: to organize the world's information, making it universally accessible and useful. And you can only organize information if you have access to it. Personal or otherwise.

Now if you go back and compare all this with that article dberkholz had linked to it's exhilarating how it matches my fantasizing here down to the "But I'm now a Google employee and won't comment further".

How often you see public discussions about future of Boeing aircraft or Intel's CPU by random engineers of Boeing or Intel? While they are with Boeing or Intel, that is? Why should Google be any different? "Don't air your dirty laundry in public" principle is ages old one!

Being a monopoly means that the company and its products are in a way a "public infrastructure".

Nope. Being monopoly means you if you try to actively hurt your competition you'll be prosecuted. Nothing more, nothing less. If government wants to declare Google, Microsoft, or a "public infrastructure" it must be nationalized first. Any other position is schizophrenic (by your definition): you can not simultaneously demand "public infrastructure" treatment and refuse to spend taxpayers money for said infrastructure.

Villa: Why feed reading is an open web problem, and what browsers could do about it

Posted Apr 28, 2013 14:16 UTC (Sun) by pboddie (guest, #50784) [Link]

Now if you go back and compare all this with that article dberkholz had linked to it's exhilarating how it matches my fantasizing here down to the "But I'm now a Google employee and won't comment further".
How often you see public discussions about future of Boeing aircraft or Intel's CPU by random engineers of Boeing or Intel? While they are with Boeing or Intel, that is? Why should Google be any different? "Don't air your dirty laundry in public" principle is ages old one!

I still think the point originally made is somewhat valid. The bloggers in question are quite happy to talk about their work at Google, Microsoft, whoever, but when any kind of negative issue arises they prefer to remain silent. There are probably exceptions to this, but they most likely involve very senior people who have very solid reputations and long careers behind them.

For some of these bloggers - and none of them are "random engineers" by any means - no-one would really care who they worked for if they didn't make a big deal about it. I know that Tim Bray wants to operate under "full disclosure" and doesn't want to be accused of bias by operating a supposedly neutral blog when it turns out that he works for Google (but apparently isn't paid to blog by them, since he's been doing it for years), but one might think that by disclosing affiliations it might buy him some opportunity to be negative about things he doesn't like. However, for all I know, he might not have much to complain about.

It doesn't surprise me that you bring up the "dirty laundry" analogy. Corporate culture can be secretive but also hostile towards criticism. Sometimes that criticism appears on the outside because the internal channels either aren't there or function as a means of excluding and expelling dissenters. In any case, if someone clearly has a problem with their employer's strategy and are happy to talk about the good stuff, it's only reasonable to expect them to acknowledge the bad stuff, too, and not self-censor themselves. Otherwise, we end all up being given pure advertising to read, and at that point we might as well block that as well and get on with looking at more interesting things instead.

Villa: Why feed reading is an open web problem, and what browsers could do about it

Posted May 1, 2013 17:06 UTC (Wed) by tpo (subscriber, #25713) [Link]

I was a bit provocative, but I think not completely wrong when I wrote: "... Lately I am getting the impression, that even though Google is innovating hard, whenever it puts down its foot somewhere, it immediately kills the whole ecosystem there..."

Upon which you asked: "... but what can Google do? ..."

I assumed and still do, that this was not a rhetoric, but an honest question and tried to explain what I'm seeing as the root cause. Maybe my proposition could be summarized as: "It's by priorizing it's own insatiable greed for data that Google is causing the damage".

You countered by trying to lead ad absurdum one of my arguments that people should not stop to be critical, even of their own employer and even in public. And on the way you ridiculed me a bit ("it's funny how you..." - a solid rhetoric technique).

But I think neither refuting me nor the "funny bit" are relevant in face of the important issue, which still is "what can Google do?" and "why is it that Google is causing damage?".

As said, my proposition is:

It's the greed. It needs to be kept in check. Only the public can be expected to do that.

What's your position on that? Where do you see the causes? What remedies do you think are possible?

Really Senseless Syndication

Posted Apr 23, 2013 19:09 UTC (Tue) by Topaz (guest, #60130) [Link] (3 responses)

RSS is a solution in search of a problem. It's folly to blame users for not adopting what a handful of technophiles are infatuated with.

In the browser, the "news feed" experience has already been widely adopted and works perfectly well. I go to my favorite websites, browse the items on their front pages, and pick and choose the content I want to read. There's no separate app for it. There's no need for a separate app for it.

The best way to improve RSS uptake would be to make it easy to browse feeds on a web page, or as a web page. But then again, that's what front page news feeds are for! So what's the purpose of RSS again?

If webpage-based news feeds aren't clean, light, and easy to follow, that's the website's problem.

Really Senseless Syndication

Posted Apr 23, 2013 19:17 UTC (Tue) by corbet (editor, #1) [Link]

I follow a lot of web sites. I don't want to visit each site's news feed individually regardless of how "clean, light, and easy to follow" it is. I simply do not have the time for that.

Really Senseless Syndication

Posted Apr 23, 2013 19:30 UTC (Tue) by apoelstra (subscriber, #75205) [Link]

> In the browser, the "news feed" experience has already been widely adopted and works perfectly well. I go to my favorite websites, browse the items on their front pages, and pick and choose the content I want to read. There's no separate app for it. There's no need for a separate app for it.

A RSS feed shortcuts two of those steps, and can also store and sort links for you. It gives you a consistent interface and doesn't require connecting to 30 domains and running all sorts of random scripts.

Really Senseless Syndication

Posted Apr 23, 2013 19:43 UTC (Tue) by davide.del.vento (guest, #59196) [Link]

Do you "follow", "like" or "have circles"? Well, if not and you're happy about it, fine. RSS is not a solution in search of a problem: it's the open solution on the open web to the same problem that the social networks "solved" in their walled gardens.

Villa: Why feed reading is an open web problem, and what browsers could do about it

Posted Apr 23, 2013 20:39 UTC (Tue) by lmb (subscriber, #39048) [Link]

It is obvious why technology like RSS will fail: it makes inserting advertisement much harder, so "free" sites have no incentive to add it. End of story.

Few sites offer even ad-free subscriptions. For those, it'd make sense for an even smaller percentage to add a special interface to retrieve the content.

hacker culture is dead

Posted Apr 23, 2013 23:07 UTC (Tue) by b7j0c (guest, #27559) [Link] (13 responses)

the s**tstorm over google reader marked the death of old hacker culture for me. in olden times, so-called hackers would have routed around this trivial barrier, by either producing a new centralized feed resource, or just writing a crawler that can digest the feeds they read (i've done this, its the equivalent of fizzbuzz for internet programming).

instead we get weeks of "first-world-problem" tantrums from white males in their 30s who are clearly overpaid, underworked, and lacking in imagination.

i'm hugely enthusiastic that google cancelled reader. this move primarily punishes *takers* merely posing as *hackers*.

hacker culture is dead

Posted Apr 24, 2013 0:04 UTC (Wed) by Cyberax (✭ supporter ✭, #52523) [Link] (6 responses)

There are alternatives (LWN covered them, btw) and people are working on migrating all the feeds from GR.

hacker culture is dead

Posted Apr 25, 2013 12:21 UTC (Thu) by pboddie (guest, #50784) [Link] (5 responses)

I think the comment is still apt, if a bit severe, however. In some Free Software projects there is a level of infatuation with Google services (and services from other corporations), and it has fostered a mentality of dependence and an unwillingness to spend very much effort on developing genuinely free infrastructure because some generous benefactor "has got us covered".

I see this as being largely a symptom of modern consumerism where people will gladly seek out a "deal" that saves them money today but obliges them to do the same tomorrow and every day if they don't want to end up out of pocket (even though they will go through considerable inconvenience and waste considerable amounts of time and effort, anyway). In the software development world, the convenience of "just putting everything in Google Docs" (or some other service whose terms might change and cause a crisis, even ignoring the basic issues of accessibility and availability) is a way of deferring or ignoring awkward but important decisions and is usually justified by a bunch of people who claim that they should not get involved with "ideology" by considering free and open alternatives. However, by failing to consider the sustainability of their own project they are in fact neglecting the foundations on which new and similar projects may be built, especially after the favoured corporations have withdrawn their tempting offers.

I've seen people post things to mailing lists requesting that people lobby some company or other to add support for a project to a proprietary product. Rather than encourage others to develop a comparable offering that can be used freely by everyone, they would rather that people fall into line and channel their energies into clicking "like" buttons to get what they want instead of remedying the situation creatively and productively. People should of course be allowed to spend their time and money on whatever they want, but it says a lot that deal-surfing and petitioning are apparently popular activities and are perceived as solutions rather than the lazy way out that they most often are.

hacker culture is dead

Posted Apr 25, 2013 17:00 UTC (Thu) by Cyberax (✭ supporter ✭, #52523) [Link] (4 responses)

Why "putting everything in Google Docs" is bad?

It has lots of advantages and the only disadvantage is reliance on external infrastructure. Should every project be an isolated island?

hacker culture is dead

Posted Apr 26, 2013 9:26 UTC (Fri) by pboddie (guest, #50784) [Link] (3 responses)

Google Docs was just an example, but since you asked, a few reasons people give include not wanting to have a Google account, not wanting to use their Google account in certain contexts, finding Google Docs less convenient to use than other solutions (see below), finding Google Docs to be sluggish or having poor performance, not wanting to have to connect to the cloud every time an edit needs making to something, and so on.

I've been involved with projects where people won't even use a wiki or a simple through-the-Web editor, preferring to commit stuff into a repository and turn a handle to crank out a site update, so there is most certainly an audience that won't use what others regard as natural or convenient. Personally, I find that office software often encourages poorly structured documentation, mostly because such software has evolved towards rewarding off-the-cuff visual tweaking by people who don't know what they're doing, usually leading to lots of tidying up and extra work afterwards.

As for my choice of example, I could have used GitHub instead (because distributed version control apparently needs a "one-stop shop"), or just rattled everyone's cage and mentioned the BitKeeper fiasco.

hacker culture is dead

Posted Apr 28, 2013 23:17 UTC (Sun) by man_ls (guest, #15091) [Link] (2 responses)

Well, why is using GitHub bad then? Or even against the hacker culture? With git you can switch a repo to a different provider in two minutes if needed, as long as you don't use the remaining GitHub services such as the wiki pages (and then it would take about 10 minutes). Mind you, GitHub is not a service that keeps hostages: if they tried to pull a GAE and multiply their fees by 10, they would lose most of their user base in hours.

Yes, we could all set up git servers, back them up periodically and so on. I have done it, it is just not worth the hassle. I prefer to just pay the $12/month (in my case) and be done with it; it is even free for Free software! A fine business model if you ask me. The same could be said about Amazon AWS: they are as good as their service, as long as you stick to renting virtual machines from them. It does not detract from hacker street cred to use the cloud instead of paying for a user shell on some colocated server.

Finally, for GitHub the user is the customer. For Google users are goods for sale. There is a huge difference.

hacker culture is dead

Posted Apr 29, 2013 9:06 UTC (Mon) by pboddie (guest, #50784) [Link] (1 responses)

If I had used SourceForge as an example, imagining that we might have had this discussion a few years ago, would you have been so eager to defend it?

(I don't personally have a huge problem with GitHub, despite the Web interface being sluggish and full of JavaScript code fetching often-irrelevant information, bit I foresee a time when people will abandon it, too, and then it'll be up to those people to test out how well migration from such services works in practice.)

hacker culture is dead

Posted Apr 29, 2013 10:46 UTC (Mon) by man_ls (guest, #15091) [Link]

Good point. SourceForge started becoming "evil" around 2003 IIRC, source control was centralized, they tried to suck you in with all possible means. However it was not a huge issue for most projects to move away from it, either to free software alternatives (such as GNU Savannah) or to self-hosting. Moribund projects lacked any incentive to move and are still hosted there in suspended animation, which is not a bad way to live their last days.

In the end all value-added services (mailing lists, issue tracking and the like) are not so hard to move away from. Nowadays with git it should be even easier to migrate when the time comes, and GitHub only provides minimal value-added services. So I would say that we are learning to avoid the worst lock-in effects. Yes, I am an optimistic person.

hacker culture is dead

Posted Apr 24, 2013 13:27 UTC (Wed) by nye (guest, #51576) [Link] (4 responses)

>i'm hugely enthusiastic that google cancelled reader. this move primarily punishes *takers* merely posing as *hackers*.

I'm hugely hopeful that the power company cancels your electricity, your ISP cancels your internet connection, your phone provider cancels your phone line, your bank cancels your account(s), your local government cancels its law enforcement, education, health care, and road maintenance, and your local shops all close down.

That will punish those worthless *takers*, and sort them out from the *real hackers* who can maintain their *own* society. I've done this; it's the equivalent of fizzbuzz for post-apocalyptic survival.

hacker culture is dead

Posted Apr 24, 2013 14:51 UTC (Wed) by louie (guest, #3285) [Link]

I had someone ask me once (in all seriousness) why so many libertarians were attracted to free software. nye, your response (plus the original post) captures the answer just perfectly. Thanks :)

hacker culture is dead

Posted Apr 24, 2013 21:33 UTC (Wed) by b7j0c (guest, #27559) [Link]

almost nothing you mentioned is provided to me as a profit-driven enterprise, so the contrary holds - i am paying for police and road services through taxes - the less i am involved in receiving services from either, the better.

hacker culture is dead

Posted Apr 24, 2013 21:41 UTC (Wed) by b7j0c (guest, #27559) [Link] (1 responses)

and by the way, what were you paying for google reader again? the same as you do for lwn?

hacker culture is dead

Posted Apr 29, 2013 16:22 UTC (Mon) by k8to (guest, #15413) [Link]

That's beneath you.

hacker culture is dead

Posted Apr 24, 2013 18:24 UTC (Wed) by ThinkRob (guest, #64513) [Link]

> i'm hugely enthusiastic that google cancelled reader. this move primarily punishes *takers* merely posing as *hackers*.

A big part of hacker culture has always been -- at least as far as I've seen -- a sense of openness and working with the common good of the community in mind (if not actually towards it.)

The above statement does not seem to mesh with that.

Corbet's insights

Posted Apr 25, 2013 2:33 UTC (Thu) by tonyblackwell (guest, #43641) [Link]

Corbet: "Things have evolved considerably since then, though; getting back to it has been on my list of things to do. If only I didn't have to buy another 1TB disk just to store the to-do list... "

This must be the insight of the month...

Instant agreement from my lady-love, while I sit at my computer doing tax stuff so I'll get a release from her to go fishing tomorrow. (and yes, I snuck a look at LWN).


Copyright © 2013, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds