Follow Slashdot stories on Twitter

 



Forgot your password?
typodupeerror

Comment Yes: Newsblur.com (Score 1) 438

I've been happy with Newsblur.com: the UI has a number of improvements over Google Reader — especially the trainer which allows you to prioritize keywords, domains, authors, tags, etc. up or down (great if you follow people who share things on multiple topics and you're just not interested in one of their hobbies) and the option to have it automatically load the remote article text, which is configurable per-site — perfect for sites which only publish a snippet of the full article. The social features are decent but definitely show the market fragmentation since the number of users is so much smaller than when almost everyone was on Google Reader.

Beyond the technical aspects, there are two things which I really like about Newsblur:
1. A non-bubble business model: it's a lean but reportedly profitable service, which means you're not looking to move as soon as the venture capital runs out
2. It's all open-source: https://ancillary-proxy.atarimworker.io?url=https%3A%2F%2Fgithub.com%2Fsamuelclay%2F... has the entire site and the official Android and iOS clients

Feed Schneier: House of Lords on the Liquid Ban (schneier.com)

From the UK: "We continuously monitor the effectiveness of, in particular, the liquid security measures..." How, one might ask? But hold on: "The fact that there has not been a serious incident involving liquid explosives indicates, I would have thought,...

Comment Re:Somebody Explain Wikis, Please (Score 1) 397

I used to have the same question - then I set one up for internal documentation. Features like searching, ease of linking, version control, etc. get bandied around a lot but the simple, compelling argument is that they're easy enough to use that people actually use and, most importantly, write documentation.

In most places the general process goes something like this: nag someone for 6 months and they'll either foist the task over to someone lower on the food-chain (who is, of course, completely incapable of doing the job well - that's why they weren't asked in the first place) or eventually produce the bare minimum needed so they can say it's done with a straight face; this will be placed somewhere where a couple people will look at it once or twice and never updated. Eventually someone will realize that there's no documentation which reflects what's actually going on and start nagging someone...

With a wiki we actually have people writing documentation as they go. There's always going to be someone lazy but the barrier for entry is so low that they won't be able to come up with lasting excuses. Basically this is the first time I've worked anywhere where we have up to date, accurate documentation and it's basically due to lowering the barrier to entry that much further.

Slashdot Top Deals

There is no royal road to geometry. -- Euclid

Working...