HNHacker News
TopNewBestAskShowJobs

VoxPelli

761 karma · joined November 24, 2009

[ my public key: https://keybase.io/voxpelli; my proof: https://keybase.io/voxpelli/sigs/RUQr8ARfVmQun2quBbB3NY9DmUEcTqWfA0NQZYhR1zc ]
submissionscomments
VoxPelli··on We Need A Standard Layered Image Format
Standardizing a format/API upon a tool like SQLite was something that was proposed in the web world as WebSQL but scrapped due to not wanting an entire standard to rely on a specific code base but rather wanting to have the standard be possible to reimplementable by others and thus creating the IndexedDB standard instead.

I'm not proposing that an image format like this one should use IndexedDB, but if relying on SQLite means being reliant on a specific code base that has to be used by anyone that wants to read the file - then it's probably not such a good idea.

When discussing this I think one should also have in mind eg the move to web apps as well - a reliance on SQLite will make it hard for them to read the format. A standardized simple base format that can easily be supported in new languages would be preferable as I see it - but I'm no expert in the image processing area.

VoxPelli··on Google going its own way, forking WebKit rendering engine
That's somewhat different though because the browser and the OS is the same in Firefox OS so you would have to switch the entire OS - which in itself shouldn't be a problem once the app API:s has been finalized and standardized and implemented by others like Chrome OS (and since Google puts a big emphasize on standardization in their Blink announcement it is actually pretty likely that such an implementation will eventually happen)

When it comes to Firefox OS it is more of a question of whether phone manufacturers will allow you to switch OS on your device or not, something that eg. FairPhone has been said to be investigating, wanting to ship their device with an option of either Android or Firefox OS.

But as long as Firefox OS' API:s gets standardized and implemented by others Firefox OS can't ever turn into an IE6 because there is nothing in Firefox OS that keeps you from switching to something else, which the apps in iOS do.

VoxPelli··on Stop Writing REST API Clients
Can't we just stop writing clients for specific REST API:s period and rather just build one good API client that can easily be extended and adapted to any API?

That's the path I've been using in all projects lately - because frankly - I don't want to deal with a bunch of different API clients for Twitter, Facebook, Soundcloud, Instagram or whatever sites it is that I integrate with - all those different syntaxes and all that duplicated code etc doesn't help me - I want all of their individual differences hidden away for me and colleagues behind a single well known syntax which I myself can extend to expose the resources and methods that I need - like if I need it a method for posting a photo for the API:s that support that and so on.

My advice today would be: Pick a good HTTP client, preferably with good OAuth support, and then build your own extendable API-client on top of that and integrate all the different API-resources you need with that client whenever you need them.

VoxPelli··on OStatus: like Twitter, but open
And I would say that it's totally up to any OStatus client to improve on that in their UI if they want to. Mobile phones and e-mail clients rarely uses the raw numbers and e-mail addresses in their UI:s but instead uses data from eg. an address book to make it more userfriendly.
VoxPelli··on OStatus: like Twitter, but open
Has there been discussions about handling private data in Private content? Yes - and there have been efforts in making that possible in OStatus, but since OStatus itself is just made up of other specifications it currently awaits those other specifications to get extended in a way that supports this - not sure what the current status really is.

I personally though would prefer to have the main use case - the one with just public data - work first and learn from that and get that rolling before moving to the more complex stuff.

VoxPelli··on OStatus: like Twitter, but open
Technically it's much more than Twitter - it's a way to subscribe to activities in realtime (Activity Streams + Pubsubhubbub), a way to easily do so for users on a website (WebFinger) and a way to notify people of others activities which they are being part of (Salmon).

The activity can be small status messages like Twitter - but can also be anything else, like photos, check-ins, whatever. So in that way it's much more like a distributed Facebook than a distributed Twitter - but right now the existing clients out there don't really show that very clearly.

VoxPelli··on I Believe in Gittip
As a former Flattr developer my impression is that Flattr's lack of focus on hard numbers is due to one of its core values when it was founded - that all flattrs are equal and should be treated as such - that a flattr doesn't just represent the number of euros given but more so represents the act of giving in itself and that that's what important about it and that the actual size of the donation is secondary as that is dependent on so many factors like the givers personal economical status and such.

As long as people feel comfortable with what they are giving away and recievers feel comfortable with what they are recieving then how much each individual is giving is pretty irrelevant.

Flattr would never reveal any numbers about their users' economy as Flattr very much values, respects and sees the importance in their users' privacy. It's of course always lovely to see users share stories about how they are using Flattr in different ways, but the telling of such stories should be up to the users – Flattr should stay out of that business and instead focus solely on just making such stories possible.

Regarding fees, I think the Pinboard blog makes a great case for why they should exist: http://blog.pinboard.in/2011/12/don_t_be_a_free_user/ Apart from that I also think that micropayment services are a bit like what Steve Jobs described Dropbox as: "a feature, not a product" Features are embedded into products and are not something you pay for separately. Flattr isn't the goal – it's the means to realize the goals – it's the goals, the "products", that people want and it's they that will be flattred and it's they that should be flattred.

VoxPelli··on Please Donate to the Internet Archive
They have twenty donations waiting for them on Flattr: https://flattr.com/thing/425480
VoxPelli··on Quirksmode is seeking to raise € 2,500 in donations
CanIUse builds on top of data from eg. QuirksMode and gathers it in an easily scannable and filterable table.
VoxPelli··on Quirksmode is seeking to raise € 2,500 in donations
ppk is on Flattr - you can subscribe to him here: https://flattr.com/thing/325875/ppk-on-Twitter
VoxPelli··on Flattr no longer requires users to spend money in order to receive money
It starts next month - we wanted people to know in advance.
VoxPelli··on Flattr no longer requires users to spend money in order to receive money
Opps - we will fix that. Thanks for pointing out!
VoxPelli··on Drupal 7 Released
Among other things Drupal 7 has better support for reverse proxies like Varnish. From the changelog:

"Improved support for HTTP proxies (including reverse proxies), allowing anonymous page views to be served entirely from the proxy."

VoxPelli··on Drupal 7 Released
Drupal 6 will still be supported until Drupal 8 is released in a few years and it will for a while still be more stable than Drupal 7 and have more modules supporting it.

So no need to rush an upgrade - you can safely stay at Drupal 6 for at least a year or so.

VoxPelli··on Ask HN: Where do you host your webapp?
Both Linode and Slicehost.

I like the Slicehost admin system more than Linode's, but Linode got servers in Europe which is a big plus - and Linode have better specs than Slicehost as well.

← PreviousPage 9 of 9