silverton's dashboard

silverton replied on November 18, 2009 01:52 to the problem "Help.. Feedy doesnt start!" in Feedly:

Happy update!

As described above, Feedly with proxy has been broken for several weeks on my end, until today!

Both Chrome 4.0.249.0 AND Namoroka 3.6b3pre ...

Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2b3pre) Gecko/20091111 Namoroka/3.6b3pre GTB6

... on Mac OS X 10.6.2 with Feedly version: 2.x.140 (build 5013) are FINALLY WORKING AGAIN WITH PROXY! YAY!

Still need to check the PC.

For the longest time, it would work without proxy, but if I turned on proxy it was just raw HTML. I didn't complain every day because I know this product is in development and the crack team eventually gets around to these things.

Case in Point: Team Feedly RAWX!

P.S. While @davemcclure says I'm "pushing the envelope" by expecting PayPal to work with anonymizer proxies / VPN's, lots of freedom loving netizens behind the Great Firewall of China would tend to support my side of the claim that *all* net apps should work with *all* internet standards!

silverton replied on November 18, 2009 01:48 to the question "Unable to access Feedly" in Feedly:

Feedly on Chrome for the Mac (with proxy) has been broken for many, many weeks on my end, until today. Chrome 4.0.249.0 with Feedly version: 2.x.140 (build 5013) FINALLY WORKING AGAIN WITH PROXY! YAY!

For the longest time, it would work without proxy, but if I turned on proxy it was just raw HTML. I didn't complain all that much because I know this product is in development and the crack team eventually gets around to these things.

My faith in Team Feedly has been reinforced once again! I may need to cross post this to one other thread that touched on this issue.

silverton started following the question "Unable to access Feedly" in Feedly.

silverton replied on November 02, 2009 14:03 to the problem "Help.. Feedy doesnt start!" in Feedly:

I've kept quiet because I'm pushing the edge with Namoroka on Snow Leopard (FF 3.5.4 on PC), but feedly hasn't been working on Mac or PC for about a week here. Generally, in the past, I've had to hack the maxVersion in install.rdf but feedly always worked in Namoroka up until last week. Today, I made a fresh install of 2.x.117 and got the following:

Sorry. You just ran into a bug!
[error] failed to load the Feedly user interface because TypeError -- g is null [.../js/10101_fx-app_4901.js@212]
[feedly version:2.x.117 -- build: 4901]
[navigator user agent:Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2b2pre) Gecko/20091101 Namoroka/3.6b2pre GTB6]

and

Sorry. You just ran into a bug!
[error] failed to load the Feedly user interface because TypeError -- g is null [.../js/10101_fx-app_4901.js@212]
[feedly version:2.x.117 -- build: 4901]
[navigator user agent:Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.4) Gecko/20091016 Firefox/3.5.4 GTB6 (.NET CLR 3.5.30729)]

and Chrome still displaying page source (well, posting raw HTML doesn't work, even with pre or code tags):

html
head
title Feedly, your magazine-like start page /title
meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/
= all txt HTML follows =

I certainly do not expect feedly to support Firefox nightly builds, but it was awesome that it did work for a very long time. ;-)

silverton started following the problem "Help.. Feedy doesnt start!" in Feedly.

A comment on the problem "Problems with Feedly for Chrome and MacOSX (v0.7)" in Feedly:

Thanks for the reports, Luca. With 4.0.223.11 I'm back to getting some weirdness described over here http://getsatisfaction.com/feedly/top... Will keep poking around to see what I've done wrong this time. ;-) – silverton, on October 26, 2009 17:40

silverton replied on October 26, 2009 05:53 to the problem "Feedly Chrome Mac OS X" in Feedly:

I bet it's something stupid on my end, but if we can track it down, it might help others if the same issue is encountered later. Thanks!

silverton reported a problem in Feedly on October 26, 2009 05:46:

Feedly Chrome Mac OS X

I love feedly on chrome for windows; however, I have yet to get it working on Mac OS X 10.6.1:

1. Followed instructions on http://blog.feedly.com/feedly-chrome-...


2. Chrome version 4.0.223.11


3. Feedly.crx begins to install, but doesn't give any indication of completing


4. Have refreshed, cleared cache, ensured cookies enabled.


5. Visits to http://www.feedly.com/home display a "show source" like page of the raw html

Tried to include code excerpt, but code tag didn't seem to work quite right. ;-)

silverton replied on October 17, 2009 15:32 to the question "How do I view my annotations now?" in Feedly:

Bit of a bummer. Just installed version 2.x.086 (build 4411) and still no link to Annotated in left-hand margin where one might reasonably expect. I don't mind which direction the design goes, but do suggest presentation consistency between Narrow and Wide navigation. E.g., groupings of "Articles I recently" ... "Social" ... "Others." Just my $0.02.

I heart Feedly more each day!

Andreas Fuchs' reply to "Where can I find the default CSS definitions?" was just promoted to the most useful! silverton and 2 other people think it's one of the best replies.

The two primary CSS files that define your soup's look. You can find them at:

http://www.soup.io/skins/shared.css -- shared definitions, and

http://www.soup.io/skins/[skin name]/screen.css -- skin-specific stuff.

where [skin name] is the name of each skin, that is, "whitespace", "default", "column", and so on. There are no indexes enabled for these directories, but to learn more about the inner workings of the styles, you can change your skin to the one you want and look in your soup's HTML source for the links to the CSS files, as well.

A comment on the problem "New lowercase "id" beta login issues?" in OpenID Foundation:

Yeah, I do remember that, was hopin' there might be some cross-monitoring here. Totally understand why not. – silverton, on September 17, 2009 20:43

silverton marked one of Chris Messina's replies in OpenID Foundation as useful. Chris Messina replied to the problem "New lowercase "id" beta login issues?".

silverton reported a problem in OpenID Foundation on September 17, 2009 20:12:

New lowercase "id" beta login issues?

Looks like maybe some challenges rolling out beta program? Not able to use OpenID today. http://u.nu/3bb93 Thanks for all the astounding work!

silverton started following the question "Export full tweet archive" in Twitter.

silverton marked one of Lukas Fittl's replies in Soup as useful. Lukas Fittl replied to the question "soup.io - business model". silverton and 2 other people think it's one of the best replies.

silverton shared an idea in Soup on September 16, 2009 18:37:

Creative Commons Licensing

pondering further the best ways to not infringe on free expression while empowering individuals to decide how their own free expressions can or cannot be used, perhaps Creative Commons licensing of our unique Realtime Remix Lifestreams seems appropriate.

each stream is a unique expression that, particularly when approached with a methodology and specific intention or audience in mind, can be interpreted alternately as an art form, an academic, or professional discipline. as such, i believe these streams are absolutely a form of intellectual property that are in themselves built upon a stream of inherited creations and permissions.

while some may argue -- with great validity -- that attribution is perhaps adequate for the vast majority of cases, i'd nevertheless like to propose Creative Commons as the best framework within which soup.io users may choose to pay it forward, moving forward.

thanks again for the fantastic work.

silverton started following the question "Copyright/licensing of soup.io-posts" in Soup.

silverton shared an idea in Soup on September 16, 2009 18:23:

Feature Request: Twitter-Like User Blocking

while reading the topic block user, it was good to learn that soup.io isn't into randomly shutting down feeds.

on the other hand, there may be cases where blocking is the right response and i'd think that soup.io admins have better things to do than spend their time content policing all day.

maybe a better solution to allow us to individually block users, like we can in twitter.

for example, i'm all for gutterstar69's right to free speech, but i think i have the equal right to veto use of my curated and original content. followers of my lifestream are extending some amount of faith or trust in the fact that i won't lead them off into time-wasting directions (well, not too often, anyway). in the #curatedweb, the role of Reasonably Valuable Curator can be both hard won and easily lost.

so this is a feature request for a twitter-like user-side tool to click on another user and say, "sorry, you don't get to read or repost my stuff." that seems

above all, thanks for all the great work on soup.io!

silverton replied on September 15, 2009 21:06 to the question "How do I view my annotations now?" in Feedly:

Yeah, if you resize your browser window, it will automatically adjust to the best layout. Whenever I want the Annotations option, I just narrow the browser until the drop down appears. Per @edwk, this is only a temporary work around until Annotations link joins the wide view as well; every day in every way, getting better and better. Hope that helps!

silverton replied on September 14, 2009 23:44 to the question "How do I view my annotations now?" in Feedly:

Tessa: Go to Preferences, and scroll way down, 3rd from the bottom, to "Navigation Layout" section. Select "top navigation - optimized for 1024px" and you'll get a more narrow layout with menu bar at the top. Click the 'down pointer' at the right of that top menu bar and you'll find 'annotated' there.

Personally, I like "automatically adjust to the width of the window" in that Navigation Layout section, to get best of both worlds.