4 stories
·
1 follower

NewsBlur, flush with Google Reader refugees, rolls out redesign

16 Comments and 20 Shares
Dscf1264_large

The independent RSS reader NewsBlur, popular with power users, is getting a major facelift two months after the announcement of the Google Reader shutdown. While NewsBlur is one of the most powerful RSS readers available, it’s not known for being the prettiest — and its hefty feature set made for some tradeoff in usability.

The redesign has been available for beta testers to try out, but today it will roll out to all users. The new NewsBlur is faster and includes a number of user interface tweaks such as a unified notifications popover and a new list view for brisk scanning. The iOS and Android apps also got a refresh.

While the redesign looks slightly better, the reasons for using NewsBlur are the same. It fetches feeds quickly,...

Continue reading…

Read the whole story
gzulauf
4201 days ago
reply
San Diego, CA
popular
4201 days ago
reply
Share this story
Delete
15 public comments
henrypootel
4200 days ago
reply
the new newsblur update thingy is rather lovely
Auckland, New Zealand
synapsecracklepop
4201 days ago
reply
I've been really, really happy with NewsBlur. The redesign is icing on the cake.
ATL again
Zaphod717
4201 days ago
reply
Redesign looks nice
The Belly of the Beast
MotherHydra
4201 days ago
reply
How about that new iOS update? Very slick and very quick!
Space City, USA
DMack
4201 days ago
reply
erm, ahem, this article is very well written. I like your hair, Adrianne~
Victoria, BC
jackwiplock
4201 days ago
reply
I love the changes. It just keeps getting better and better.
emrikol
4201 days ago
reply
My reader of choice just got better.
Linton
jdgonzalez
4201 days ago
reply
This may make me want to come back.
Cedar Park, Texas
BiG_E_DuB
4201 days ago
reply
Congrats. Love the service but please keep adding features (searching, custom keyboard shortcuts, on/off preview pane permanently, etc)
Charlotte, NC, USA
samuel
4201 days ago
reply
Big story of the day!
Cambridge, Massachusetts
mgeraci
4201 days ago
Congrats! Glad to see it live, and glad to see a great publication cover it.
MotherHydra
4201 days ago
This is great coverage! Woo!
rgsunico
4201 days ago
Been enjoying this in the dev channel but glad to see it live! So pretty! So much reading space!
hansolosays
4201 days ago
reply
<3 newsblur
Norfolk, Virginia
tedders
4201 days ago
reply
Newsblur redesign is out. I am still trying to use it and Feedly.
Morgantown, WV, USA
irunfrombears
4201 days ago
reply
The redesign is pretty awesome and I've noticed it's a lot easier to use, and less frustrating, since the redesign. NewsBlur just went up in the "Who will replace Google Reader?" standings by A LOT.
DC
autocorrelation
4201 days ago
Still needs a mark all as read option at the bottom of a feed's item list (so you don't have to scroll back up to clear a feed)
irunfrombears
4201 days ago
Still needs a lot of things but I'm pretty impressed with it.
autocorrelation
4201 days ago
Oh, don't get me wrong, I think it is a very good redesign overall. I am pretty impressed as well. It was just one of those things that I thought they would have caught.
Courtney
4201 days ago
@autocorrelation you can mark-as-read right from the folder/feed list -- hover over a feed, click the arrow, kaboom.
WorldMaker
4201 days ago
@{autocorrect,Courtney} or double click the unread counter in the folder pane.
samuel
4201 days ago
or hit shift+a
autocorrelation
4201 days ago
You guys are blowing my mind. So glad I went for premium.Thanks for the suggestions.

ITAPPMONROBOT - The Daily WTF

1 Comment and 5 Shares

At the turn of the 21st century, Initrode Global's server infrastructure began showing cracks. Anyone that had been in the server room could immediately tell that its growth had been organic. Rackmounted servers sat next to recommissioned workstations, with cables barely secured by cable ties. Clearly there had been some effort to clean things up a bit, but whoever put forth that effort gave up halfway through.

It wasn't pretty, but it worked for years. As time passed, though, a proprietary gateway server to communicate with credit processing agencies would crash more and more frequently. And these were bad crashes, too — the kind of crashes where the server wouldn't respond to ping and would have to be restarted manually. It wasn't really a big deal for the admin, Erik, to hit the restart button on the server when he was there, but that was only 40 hours a week. The credit union needed it to be active 24/7, but was unwilling to hire 24 hour staff in the datacenter. The problem kept getting worse and worse, so the IT manager called up a meeting.

"OK guys, what can we do about this?" asked Laura, the IT manager. "Can you guys in dev fix this?"

"No," began Erik, before anyone in dev could respond. "The issue is with the server, not our software."

"Well, when does the support contract end?"

"Two years ago."

"Great. And we can't replace the unit while we're in a budget freeze..." Laura wasn't sure what to do. "Well, what's our workaround for now? What happens when it goes down?"

"Right now, I just hit the restart button."

"OK, well, we'll have to replace it once I get the budget approved. For now, though, what can we do? We need this online all the time." Laura sighed and began tapping her pen on the table. "No one has any other ideas?"

At this point the room fell silent and everyone tried to avoid making eye contact with Laura. Erik had a script running that would ping the server every few minutes and alert him if it didn't respond so he could halfway proactively keep things running. It had to be restarted manually whenever it crashed, so there was no easy way to fix it remotely.

"We could build an admin robot," Erik joked.

Hours later, Erik was in the datacenter, hitting the restart button again, disappointed that the meeting had ended without a workable solution. Laura walked into the room and greeted Erik.

"So, at our meeting earlier, you suggested building a robot." Laura had apparently taken his suggestion seriously. "Is that something we can really do?"

"Well, I was just ki... I mean, I don't know anything about circuitry, or how to build robots." Erik tried to keep his tone somewhere between serious and kidding, so he could gauge Laura's reaction.

It was then that he idly looked at his computer, which had just ejected a disk image DVD he'd burned.

It sparked an idea, but it was too absurd to say out loud. Still, he couldn't help but chuckle at the thought.

"What?" Laura asked.

"It's nothing," Erik responded. "It's stupid."

"We're desperate. Do you have an idea?"

"No, it was really stupid." Erik sighed. "I just had the idea that a CD ROM drive in an old system could eject and hit the reset button. It was a ridiculous idea."

"Wait," Laura began, "could you really do that?"

It was another uncomfortable moment for Erik, but she seemed serious, so he just went for it. "Uh, yeah, I could, but it's hardly the best solution... I mean, I'd have to position the servers just right, somehow get the heights and alignment correct, and update the polling script to eject the CD ROM drive any time it didn't respond to ping."

And that was exactly what Erik found himself spending the rest of the afternoon setting up. He found an old PC, updated his script to ping the server every two minutes and eject if there was no response, and with the help of a few phone books found the perfect height and position on the floor. At any point while he was setting it up, he expected Laura to jump out from a corner and yell "just kidding," but it never happened. Finally, Erik stood up, and ashamedly admired his work. He slapped a label on it that read "ITAPPMONROBOT," and another below with big underlined letters that read "DO NOT MOVE."

Years later, and long after Erik had left, the faulty server was taken offline and replaced with a new one working under a new IP address. During the swap, ITAPPMONROBOT was moved to a neglected corner of the server room, plugged back in, and promptly forgotten. It spent the last weeks of its life dutifully opening and closing its CD ROM drive every two minutes, reaching in vain for the restart button that it'd never touch again.

Read the whole story
gzulauf
4254 days ago
reply
San Diego, CA
Share this story
Delete

Sergio Garcia climbs a tree to hit one-handed second shot

1 Comment and 3 Shares
Read the whole story
gzulauf
4258 days ago
reply
San Diego, CA
Share this story
Delete
1 public comment
randall
4258 days ago
reply
Nuts. Sergio Garcia hits his ball from a tree.
Ogden, Utah

Google Public DNS Now Supports DNSSEC Validation

1 Comment and 2 Shares


We launched Google Public DNS three years ago to help make the Internet faster and more secure. Today, we are taking a major step towards this security goal: we now fully support DNSSEC (Domain Name System Security Extensions) validation on our Google Public DNS resolvers. Previously, we accepted and forwarded DNSSEC-formatted messages but did not perform validation. With this new security feature, we can better protect people from DNS-based attacks and make DNS more secure overall by identifying and rejecting invalid responses from DNSSEC-protected domains.

DNS translates human-readable domain names into IP addresses so that they are accessible by computers. Despite its critical role in Internet applications, the lack of security protection for DNS up to this point meant that a significantly large portion of today’s Internet attacks target the name resolution process, attempting to return the IP addresses of malicious websites to DNS queries. Probably the most common DNS attack is DNS cache poisoning, which tries to “pollute” the cache of DNS resolvers (such as Google Public DNS or those provided by most ISPs) by injecting spoofed responses to upstream DNS queries.

To counter cache poisoning attacks, resolvers must be able to verify the authenticity of the response. DNSSEC solves the problem by authenticating DNS responses using digital signatures and public key cryptography. Each DNS zone maintains a set of private/public key pairs, and for each DNS record, a unique digital signature is generated and encrypted using the private key. The corresponding public key is then authenticated via a chain of trust by keys of upper-level zones. DNSSEC effectively prevents response tampering because in practice, signatures are almost impossible to forge without access to private keys. Also, the resolvers will reject responses without correct signatures.

DNSSEC is a critical step towards securing the Internet. By validating data origin and data integrity, DNSSEC complements other Internet security mechanisms, such as SSL. It is worth noting that although we have used web access in the examples above, DNS infrastructure is widely used in many other Internet applications, including email.

Currently Google Public DNS is serving more than 130 billion DNS queries on average (peaking at 150 billion) from more than 70 million unique IP addresses each day. However, only 7% of queries from the client side are DNSSEC-enabled (about 3% requesting validation and 4% requesting DNSSEC data but no validation) and about 1% of DNS responses from the name server side are signed. Overall, DNSSEC is still at an early stage and we hope that our support will help expedite its deployment.

Effective deployment of DNSSEC requires action from both DNS resolvers and authoritative name servers. Resolvers, especially those of ISPs and other public resolvers, need to start validating DNS responses. Meanwhile, domain owners have to sign their domains. Today, about 1/3 of top-level domains have been signed, but most second-level domains remain unsigned. We encourage all involved parties to push DNSSEC deployment and further protect Internet users from DNS-based network intrusions.

For more information about Google Public DNS, please visit: https://developers.google.com/speed/public-dns. In particular, more details about our DNSSEC support can be found in the FAQ and Security pages. Additionally, general specifications of the DNSSEC standard can be found in RFCs 4033, 4034, 4035, and 5155.
Read the whole story
gzulauf
4264 days ago
reply
San Diego, CA
Share this story
Delete
1 public comment
skorgu
4264 days ago
reply
This is *excellent* news.