Disqus - Latest Comments for cpoetter

Re: First Look- Droid Phone by Motorola

cpoetter — Sun, 08 Nov 2009 11:53:43 -0000

Cool, luckily Android 2 will be available for the Hero as well.

Re: First Look- Droid Phone by Motorola

Jason H — Sun, 08 Nov 2009 11:40:55 -0000

Android 2 gives you a way to do it form the Settings menu.

Re: First Look- Droid Phone by Motorola

cpoetter — Sun, 08 Nov 2009 11:25:30 -0000

Well, all Android phones close apps when they run out of memory. But yes, I also have an app to close them. It saves some battery life. I'm on a HTC Hero, though.

Re: OpenID Logins Take too Long

cpoetter — Thu, 08 Oct 2009 13:13:49 -0000

Yes, emailtoid.net is part of Vidoop.

Indeed, RPX has made it easier for users to log in. It remembers the OpenID Provider users usually use and only presents this provider when users return.

Re: WordPress Category Feeds and FeedBurner

cpoetter — Tue, 06 Oct 2009 12:53:46 -0000

As explained in the article, WordPress automatically creates category feeds: www.example.com/category/yourcategory/feed

Just click on a category of your blog and subscribe to that feed. Usually, this works fine.

Re: OpenID for all Estonians

eddiepetosa — Wed, 23 Sep 2009 14:08:45 -0000

Ok, thanks for the prompt answer!

Re: live.hackr : Yahoo in the mix

hackr — Tue, 22 Sep 2009 14:38:49 -0000

hoffentlich gibts bald ein helvetihoo ;)

Re: live.hackr : Yahoo in the mix

cpoetter — Tue, 22 Sep 2009 14:33:59 -0000

Sehr cool. Bei den Suchergebnissen sollte man unbedingt auch einmal auf Options -> Preferences gehen, um die Suchergebnisse etwas schöner darzustellen.

Re: OpenID Logins Take too Long

cpoetter — Thu, 17 Sep 2009 14:34:28 -0000

Directed Identity makes typing in the OpenID URL rather easy, of course. By the way, Yahoo! is also an option at RPX. Yiid just chose to present other providers on its login screen.

Re: Google Reader Needs Filters

mitchellmckenna — Tue, 15 Sep 2009 21:18:27 -0000

I 2nd the Feedly recommendation!

Re: Google Reader Needs Filters

cpoetter — Tue, 15 Sep 2009 13:11:28 -0000

Never heard of Fever. I will have a look at it as well. :)

Re: Google Reader Needs Filters

cpoetter — Tue, 15 Sep 2009 13:09:56 -0000

Even more Firefox goodies. If I'll find some spare time I will test it. But I don't want to switch to Firefox completely. :(

Re: Google Reader Needs Filters

cpoetter — Tue, 15 Sep 2009 13:06:53 -0000

Ah, sounds good. I will give it a try.

Re: Google Reader Needs Filters

louismg — Tue, 15 Sep 2009 04:35:00 -0000

Feedly is a new interface to Google Reader. It is Firefox only BUT there is a way to use it with Safari as well.

http://blog.feedly.com/2009/07/31/experimental-...

Re: Google Reader Needs Filters

cpoetter — Mon, 14 Sep 2009 17:13:35 -0000

No, haven't tried Feedly yet. It's Firefox only, isn't it? Usually I rely on Safari.

I will have a look at Postrank, though. I wanted to have a closer look at it a loooong time ago already.

Re: OpenID for all Estonians

cpoetter — Mon, 14 Sep 2009 01:33:09 -0000

In the meantime some other countries have introduced electronic ID cards (Belgium, Finland,...). Those cards are secure but can be compromised as I had to learn from some other people, e.g. Marc Wilcox' post (see comment above).

Re: Nambu to be Re-Released (so to speak)

cpoetter — Wed, 26 Aug 2009 00:15:23 -0000

I'd love to see Flickr as an image sharing option. Would be awesome, no Twitter password required there like TwitPic.

Re: Oh, the Trouble With OAuth

rythie — Sat, 08 Aug 2009 13:14:45 -0000

I agree. The main problem that Twitter needed to solve given that they are dependent on the API was that third party apps had to store your password in a plain text or reversible encrypted form, which made it hard to know who had access and how to revoke it. It's something Flickr solved years ago and perhaps never had the problem.

A completely different problem is that users don't like having lots of logins, using Twitter's oAuth for logins helps that, but ultimately it wasn't designed for that and Twitter isn't setup to support that really.

I think the problem with relying on the third party for authentication, be that oAuth, OpenID, FB connect or whatever, is that the third party has to provide a service has to be very very reliable and with a good support system behind it. Twitter is not currently such a company, they are notorious for reliability issues, they are young company with relatively few staff and pretty much all in one location. If you compare that to Google for example, they are an old company with a massive staff, lots of experience and reputation for good uptime. Also, Google have people in several different timezones supporting their core stuff, so if something goes wrong there is always someone who is at work, at their desk, who's job it is to fix it and they are more than qualified to do so.

Re: Oh, the Trouble With OAuth

cpoetter — Sat, 08 Aug 2009 11:40:12 -0000

UX can always be improved. However I still think each protocol should be used the way it was intended to be. The protocol itself can grow and mature over time (OpenID is such an example), of course.

Re: Oh, the Trouble With OAuth

jessestay — Sat, 08 Aug 2009 07:48:04 -0000

I still think there is a need to decentralize the OAuth process from the
Providers. The Authorization process and the API calls to the Provider are
completely different layers. In Twitter's case currently, I can make API
calls, but I cannot get my app authorized.
That also does not address the other issues with OAuth I mention.
Regardless, there's still a huge Ux problem with OAuth. Centralization is
only one problem I see.

Re: Oh, the Trouble With OAuth

cpoetter — Sat, 08 Aug 2009 05:09:00 -0000

I don't think it's an OAuth problem you're describing here. Rather it seems you - and other developers as well - are using OAuth for means it wasn't designed for. OAuth is meant only for authorization of third party apps, so users don't have to provide their passwords to those apps. If the OAuth provider (=Twitter) is down there is no need to make API calls to it because quite simple, the third party can't get any data.

The problem is that third parties use for OAuth for authentication as well. Admittedly, that's even encouraged by Twitter with its Twitter login buttons. However that's not OAuth's purpose. There is OpenID, there is FB Connect.

Re: live.hackr : 1984

hackr — Sat, 18 Jul 2009 10:37:48 -0000

yep, wobei die kulturellen praktiken zwar langsamer sind, aber es geht auch nicht ohne. mittelfristig sehen wir da wohl eine annäherung.

(die diskussion könnte durchaus auch aus deutschland kommen, glaub ich, das viel kleinere canada macht das ja gerade vor)

Re: live.hackr : 1984

cpoetter — Sat, 18 Jul 2009 06:32:37 -0000

Abgesehen vom fehlenden Fingerspitzengefühl zeigt die Story wieder, dass Technologie bereits viel weiter ist als Diskussionen - und vor allem Lösungen - zu Themen wie Datenschutz und Privatsphäre.

Das Web entwickelt sich fast schon zu schnell, als dass jemand noch den Überblick behält, welche Auswirkungen für die Nutzer bestehen könnten. In dem Zusammenhang bin ich auch mal gespannt, wie die Forderungen der Verbraucherzentralen hinsichtlich der AGBs von Social Networks umgesetzt werden. Ich denke da gerade an Facebook, die einige der Klauseln sicherlich benötigen werden, um überhaupt Features wie den News Feed zu gewährleisten. Den Verbraucherzentralen sind die Möglichkeiten des Austauschs von Daten sicherlich nicht bewusst.

Allerdings bin ich mir nicht klar darüber, über welche Wege solche Diskussionen angestoßen werden können, zumal die Entwicklung in den USA statt findet und wir Europäer dort nicht mitreden.

Re: live.hackr : TechFuga

cpoetter — Sat, 03 Jan 2009 14:53:11 -0000

Sieht ja richtig gut aus. Mal merken. :)

Re: live.hackr : Techblogs des Jahres

louismg — Thu, 01 Jan 2009 18:56:39 -0000

Yes, Corvida was very visible in the first part of the year, but she went dark in the second half. She no longer works at RWW, but has a community manager position at The Industry Standard. We may see more of her yet. She got burnt out and has some offline work taking her time, is my understanding.

(And yes, it was me)