Why feed reading is an open web problem, and what browsers could do about it | Luis Villa
… [D]espite what some perceive as the “failure” of RSS, there is
obviously a demand by readers to consume web content as an
automatically updated stream, rather than as traditional pages. Google
Reader users are extreme examples of this, but Facebook users are
examples too: they’re no longer just following friends, but companies,
celebrities, etc. In other words, once people have identified a news
source they are interested in, we know many of them like doing
something to “follow” that source, and get updated in some sort of
stream of updates.
Why should browsers treat RSS as a first-class web citizen in a way
they don’t treat other things? I think that the difference is that if
closed platforms (not just web sites, but platforms) begins to the
only (or even best) way to experience “reading streams of web
content”, that is a problem for the web. If my browser doesn’t tightly
integrate email, the open web doesn’t suffer. If my browser doesn’t
tightly integrate feed discovery and subscription, well, we get
exactly what is happening: a mass migration away from consuming (and
publishing!) news through the open web, and instead it being channeled
into closed, integrated publishing and subscribing stacks like FB and
Twitter that give users a good subscribing and reading experience.
entitled: RSS needs to be easier | posted: 14:46Z
filed: /tech/web | 0 comment(s)
http://jsbeautifier.org/
Don't know how well it works.
entitled: De-obfuscate JavaScript | posted: 09:04Z
filed: /tech/web | 0 comment(s)
From Wikizine #130:
=== Did you know … ===
… what protocol relative URLs are?
Normal URLs look like: http://test.wikipedia.org/wiki/Main_Page or
https://test.wikipedia.org/wiki/Main_Page.
Both of these URLs define the protocol that will be used. Protocol
relative URLs look like this: //test.wikipedia.org/wiki/MainPage.
Dropping the protocol from the URL allows the browser to assign the
current protocol to the URL. So, if you are visiting the site in HTTPS
mode, links will point to HTTPS, and if you are visiting the site in
HTTP mode, links will point to HTTP.
:*
http://blog.wikimedia.org/2011/07/19/protocol-relative-urls-enabled-on-test-wikipedia-org
– full post about this by Ryan Lane :*
http://blog.wikimedia.org/2011/09/27/protocol-relative-urls-enabled-on-all-wikimedia-foundation-wikis/
– protocol relative URLs are now live
entitled: Protocol-relative URLs | posted: 15:08Z
filed: /tech/web | 0 comment(s)
JulianHyde goes through chan history on reddit
It's … a well-known fact that the legendary meme-forging /b/ is now
butf a buffer to keep idiots off the better boards (an
oversimplification, perhaps; /b/ is still an entry point and a place
for infusion of culture). So, where did all the old /b/tards actually
go? Well, some say a few still camp out at 7chan, others say the only
trace left is in WTFux, but I'll let you in on a little secret: they
came to reddit.
entitled: History of the chans | posted: 08:56Z
filed: /tech/web | 0 comment(s)
