Comments on: Bloglines Feedback

By: onlinemovieez

onlinemovieez — Wed, 10 Mar 2010 17:00:21 +0000

You Can Watch Online New Romantic, Comedy, Horror, Sexual And Moral Hollywood Full Movies 100% Updated and totally Free Available Only At: http://onlinemovieez.info/

By: OddThinking » Bloglines Networking Issue

OddThinking » Bloglines Networking Issue — Tue, 15 Aug 2006 08:42:30 +0000

[...] The Bloglines web-site appears to be up, but it doesn’t seem to want to talk to me. Did I say something too nasty last time I was freedbacking? [...]

By: Aristotle Pagaltzis

Aristotle Pagaltzis — Sat, 05 Aug 2006 22:49:39 +0000

You know, I would gladly have chopped a bunch of problematic visual details from the IE experience and called it a day (“if you don’t want to surf a fugly web, use a capable browser”), even if that meant less billable time to list on my invoice.

Alas, it was not my call to make.

By: Julian

Julian — Sat, 05 Aug 2006 14:20:19 +0000

Aristotle wrote:

The other week I spent some 30 hours beating IE into submission on an otherwise 10-hour webmonkey job. If more people used browsers with less than paleolithic layout engines I wouldn’t have had to.

I have sympathy; I really do. I, too, have been frustrated writing HTML for IE. However, you have to understand how a web-surfer, rather than a web-monkey, reads a complaint like that:

“Blah blah blah. I have tested my site on IE. I spent a lot of effort on making sure it works with IE. If you use IE on my site, you can be sure that it will work. Blah blah blah.”

I am not sure you made a convincing argument to get me to stop using IE as my browser of first-choice.

(Damn, I was trying not to get dragged into this argument.)

By: Aristotle Pagaltzis

Aristotle Pagaltzis — Mon, 03 Jul 2006 04:17:58 +0000

Yawn…

I’m actually kinda serious. The other week I spent some 30 hours beating IE into submission on an otherwise 10-hour webmonkey job. If more people used browsers with less than paleolithic layout engines I wouldn’t have had to.

Now I just need all the blogging software to make the concept clearly visible to the authors and all authors to take advantage of it.

Yeah, that’s the problem. :(

By: girtby.net » Blog Archive » The Phoney Internet

girtby.net » Blog Archive » The Phoney Internet — Sun, 02 Jul 2006 12:06:10 +0000

[...] Unlike the Joneses I haven’t been using Bloglines for a while now. It has a mobile version but I don’t like it, or the full desktop version, as much as Newsgator’s equivalents. However the advantages are fairly slim and without the advantage of NetNewsWire syncing I wouldn’t have bothered switching. I will say that I have a lot more confidence in Newsgator’s business model than the non-existant one of Bloglines. [...]

By: brainsnorkel.com » Blog Archive » A post about Bloglines

brainsnorkel.com » Blog Archive » A post about Bloglines — Sat, 01 Jul 2006 11:00:39 +0000

[...] Julian has already been freeding backing his commentsing. That post has made me think critically about Bloglines for the first time since Google Reader was introduced. [...]

By: Julian

Julian — Fri, 30 Jun 2006 13:52:51 +0000

Update: I now realise the LHS and RHS Truncation issues are really the same issue and shouldn’t be listed separately. The problem is the right margin is wider than the window, for both frames.

Boo hiss! Shame on you.

Yawn…

Atom already supports that notion. [snip] Bloglines could elect to ignore any changes in an entry that it sees when the atom:updated datetimestamp hasn’t also changed.

That’s cool, Aristotle. For all I know, Bloglines already supports this. Now I just need all the blogging software to make the concept clearly visible to the authors and all authors to take advantage of it.

bloglines freedbacking

Thanks, Chris. I took the precaution of manually submitting the URL to Bloglines feedback form.

By: Chris

Chris — Fri, 30 Jun 2006 09:28:50 +0000

I believe the terms are “bloglines freedbacking” as of this Bloglines post

By: Aristotle Pagaltzis

Aristotle Pagaltzis — Thu, 29 Jun 2006 03:39:30 +0000

(I typically use IE 6 on Windows.)

Boo hiss! Shame on you.

It would be fantastic if there was some convention, supported by Atom and the major blogging software, by which authors could indicate that the changes were minor typo fixes, as opposed to substantial corrections, and hence not worth re-reading.

Atom already supports that notion. It says that the atom:updated element in an atom:entry should contain the date of the last significant update, at the publisher’s discretion. Bloglines could elect to ignore any changes in an entry that it sees when the atom:updated datetimestamp hasn’t also changed.