HNHacker News
TopNewBestAskShowJobs

zaphoyd

890 karma · joined February 12, 2010

email: hackernews@zaphoyd.com web: https://www.zaphoyd.com

[ my public key: https://keybase.io/zaphoyd; my proof: https://keybase.io/zaphoyd/sigs/7AwrXTTBUkPTzTgg12WEOisWDxg1xGo8hftKyhNPImI ]

submissionscomments
zaphoyd··on DNS tools for developers
I have edited my post to hopefully make it less "rude", that was certainly not my intention. I do want to point out, and I think I am not alone in this, that in 2012, lack of IPv6 support (at least at the basic level of parsing IPv6 addresses and showing AAAA records / reverse lookups) in a network tools suite doesn't make it "not perfect", it makes it "not useful".
zaphoyd··on DNS tools for developers
A friendly reminder from a sysadmin/web app developer who has to deal with dns and network issues in the real world and would like to use a nice clean UI tool like this: Lack of IPv6 support is a deal breaker.

EDIT: for friendliness.

zaphoyd··on IPv6 now deployed across entire T-Mobile US network
IPv4 only content providers beware:

T-Mobile's IPv6 service is an IPv6-only service that uses NAT64 and DNS64 in the network to connect IPv6 mobile users with IPv4 content.  We believe that the majority of the bandwidth consumed by IPv6 subscribers will be native end-to-end IPv6 without any translation required by the end of 2012 as major content providers like Google, Yahoo, Facebook, Microsoft, and many others have demonstrated during World IPv6 Day

zaphoyd··on WebSockets versus REST?
Where does this article talk about >1s connect times for websocket? The websocket handshake is a single network round trip (discounting any added by TLS if you are using it) and the initial client message frames can be sent in the same TCP packet as the handshake. A websocket connection should not add any more latency than HTTP(S) connections.
zaphoyd··on WebM-Enabled Browser Usage Share Exceeds H.264-Enabled ones
Android 2.3+ supports webm via the video tag. I am not sure what the hardware acceleration status is, certainly not as good as the near ubiquitous hardware h.264 support.
zaphoyd··on WebM-Enabled Browser Usage Share Exceeds H.264-Enabled ones
If you consider mobile, which the article did not, the numbers are closer but still slightly favoring webm.

Opportunities for growth 4% world share of Firefox 3.6 users -> webm 26% world share of IE 6-8 users -> up for grabs? iOS/Mac growth -> mostly h.264  Android growth -> both 23% loss for h.264 if/when chrome drops support 

Why webm still doesn't matter yet: demographics and fallback availability. The devices that exclusively support h.264 are more valuable users for video (mobile, console, set top box) and have no fallbacks. Most of the webm support base (desktop Firefox, chrome) can fall back to flash h.264 player. Half of the webm support base presently supports h.264 natively anyways (chrome, android)

Other notes: - webm support can be trivially added to desktop safari and IE9+ by mildly tech savvy users. - h.264 tools and encoders are better and hardware encode/decode support is far better - the openness and cheapness of webm will probably improve its tool and hardware support in the long run especially if/as uncertainty about its patent status declines.

zaphoyd··on WebSockets is a stream, not a message based protocol
The WebSocket protocol guarantees that all hops along the way preserve message boundaries except in the case of explicitly negotiated extensions that dictate otherwise.

Even in cases where your WebSocket implementation exposes incomplete message fragments, the boundaries of the message are still clearly and accurately preserved.

zaphoyd··on WebSockets is a stream, not a message based protocol
As I mentioned above, I agree that that needing to pass maximum message size out of band makes some things more difficult. Whether that was the right tradeoff in terms of convenience vs protocol complexity I think has yet to be seen. At any rate, an extension to perform this in band should be trivial. Perhaps I will try writing one to test out my extension handling code.

I do see your point on the "endless streaming" section of the RFC. Stating that "(section 5.4) The primary purpose of fragmentation is to allow sending a message that is of unknown size when the message is started without having to buffer that message." implies that a web socket implementation should support this sort of operation. Indeed, if you want to support sending messages of unknown size you must expose an interface more complicated than the default message based one.

That said, a message only implementation that does not allow sending unknown sized messages is 100% compliant with both the spec and receiving such messages. The RFC probably could have made this fact more clear. I believe that endless streaming mode will not be a common use case and have not implemented it in my generic WebSocket library. I do believe, however, that fragmentation of messages provides important benefits even without unknown size sends. Once you have message fragmentation there is no additional protocol cost to allow unknown size sends.

zaphoyd··on WebSockets is a stream, not a message based protocol
I think his analysis is flawed. WebSocket is a message based protocol that does not specify a maximum message size in the RFC. This does not make it a streaming protocol until an implementation decides to deliver incomplete messages to the end application. Some implementations have done this, many (including all browsers) have not and will not.

Time and time again it has been demonstrated that we are bad at choosing a maximum allowed value for all applications and all future considerations (see: ethernet frame sizes, IP address lengths, operating system address spaces, file system block sizes/counts, etc).

In some cases (many of those previously listed) there were hardware, cost, or technical concerns that led to nailing down a number in an RFC. For WebSocket there is no clear benefit to forever encoding a specific numeric maximum message size. It is a high enough level protocol that there is no technical or cost benefit to make message sizes limited by anything other than individual application needs.

As such, the WebSocket RFC leaves maximum message size implementation defined, and specifically says that an implementation SHOULD implement a reasonable maximum message size for its purpose. A chat application that knows it will only be moving small text messages can set its maximum message threshold small to improve buffer performance and catch invalid messages sooner. An application that finds a business case for sending a large file in one large message can set itself up accordingly. Generic WebSocket parsers should expose a method of setting the maximum message size the application wishes to receive.

I definitely agree that not requiring implementations to return their maximum message size along with the "Message too big" error will make some sorts of interoperability more difficult. However, it also prevents exposing implementation security details and simplifies the core spec (the author has already complained that the spec is too complicated already). It is relatively simple for an application to negotiate a maximum message size privately if necessary and the WebSocket extension mechanism allows a method for standardizing a way of doing so if this turns out to be a serious issue in the future.

zaphoyd··on Microsoft Co-Founder Paul Allen Unveils Giant Plane for Private Space Launches
Wouldn't Bill Gates be an example of that? Vaccines/medical programs, next generation fission reactors, educational technology?
zaphoyd··on WebSockets RFC is now official
https://github.com/oberstet/Autobahn is another option
zaphoyd··on World Domination Using Arduinos and Websockets
Current story on WebSockets

There are two components to web sockets. The WebSocket API under development by the W3C/HTML5 groups (http://dev.w3.org/html5/websockets/) which defines the javascript/browser API and the WebSocket Protocol under development by the HyBi working group at the IETF (http://datatracker.ietf.org/wg/hybi/charter/) which defines the actual wire protocol.

The WebSocket API has been relatively stable for awhile, most of the changes recently have been hashing out how to handle binary messages in javascript.

The WebSocket wire protocol has been undergoing more substantial development in the past year and is presently in the Last Call phase of IETF standardization. The final wire protocol has not been fixed yet.

Protocol version numbers were added sometime last year and each version stands for which draft version of the protocol the user agent is implementing. Not all drafts change the wire protocol so some version numbers aren't used. The purpose of the version numbers was to help folks who were writing test implementations of websocket to keep track of which implementations should work together for interoperability testing.

The draft/version number primarily indicates that the client can only talk to servers that speak the same version. Clients typically support only one draft, servers often support multiple drafts. The current draft (http://tools.ietf.org/html/draft-ietf-hybi-thewebsocketproto...) uses protocol version 13. FireFox 6 ships with a prefixed (MozWebSocket) websocket object that implements draft 7. FireFox 7 and 8 and Chrome 14 and 15 (beta and dev channels respectively) currently implement draft 8, though this may change before they are shipped. Safari 5.0.1+ and Chrome 7-13 implement draft 0, an obsolete version from 2010.

Draft 7,8, and 13 are nearly identical, a server supporting one will likely support all three. Draft 0 is significantly different. There is a list on wikipedia of the major websocket implementations and which protocol versions they presently support (http://en.wikipedia.org/wiki/Comparison_of_WebSocket_impleme...).

The OP appears to be using a simplified version of a pre-draft 0 that Pusher implemented. I am not actually sure why it is using websocket at all since it doesn't appear to actually use the browser as the source of the connection. It just happens to be using an early draft of the websocket protocol as it's message framing mechanism.

zaphoyd··on Why every programmer should have a Tiddlywiki
DokuWiki is a nice compromise between the two. Instead of using a database it is backed by human-readable flat files. It'll run on a basic shared hosting account (or your home machine) without any setup other than dropping the files into a web accessible directory. Benefit over pure flat file is some basic formatting and links between pages.
zaphoyd··on How To Use UTF-8 Throughout Your Web Stack
Yes you are right on the 3 vs 4 octets for outside BMP, it is the 4 octet UTF8 that MySQL pre 5.5 doesnt work with. With MySQL 5.5 the full basic LAMP stack at least will now handle non-BMP characters.
zaphoyd··on How To Use UTF-8 Throughout Your Web Stack
It is probably worth including a character outside the basic multilingual plane (e.g. anything above 0x10000, like http://unicodelookup.com/#0x22222/1) when testing UTF-8 web support. I recently was working on a Japanese teaching web application that needed such characters and sadly learned that MySQL versions before 5.5 do not support UTF-8 characters outside of BMP (anything that needs more than 4 UTF-8 octets) and text to image drawing library support was also sketchy.
zaphoyd··on Lion's Mission Control: UX fail, especially for multiple displays
With the focus on full screen apps I'd say their future is one small laptop/iPad display. Full screen / mission control brings us much closer to iOS style application switching which in fact does work well on the air and MBPs but is less useful on the 27 inch screens and downright worthless with two screens.
zaphoyd··on IPv6 Day Has Started
try www.ipv6day.org. `ipv6day.org` doesn't even have a regular A record.
zaphoyd··on IPv6 Day Has Started
sprint.net has a pretty nice one. Theirs isn't an IPv6 day exclusive either. Kind of amusing address for a telecom company...
zaphoyd··on IPv6 Test
The two big tunnel brokers are primarily run by network transit companies for whom bandwidth is less an issue and who benefit from more IPv6 traffic and the experience that managing and debugging it provides.

I suspect that tunneled traffic volumes will always be low enough not to significantly affect the bottom line, as anyone willing to maintain a manually configured tunnel will move to native IPv6 transit as soon as possible and higher volume production business needs will use native/load balancers/proxy servers instead of tunnels.

zaphoyd··on IPv6 Test
ipv6.google.com is in fact an IPv6 only site that is not accessible at all over IPv4.
zaphoyd··on IPv6 Test
assuming by ping6 2001:0db8:200:f101::1 you mean ping6 to a real IPv6 address rather than the 2001:db8::/32 demonstration address, then yes, you probably have a link local IPv6 address only. You can also check by running ifconfig (or the similar utility for your OS) and looking for a globally routable IPv6 addresses on your network interface. If you only have addresses starting with fe80 then you are likely link local only and not getting anything globally routable from your ISP.
zaphoyd··on IPv6 Test
weird.. test-ipv6.com gives me 10/10 for full dual stack compatibility and ipv6test.google.com says I don't have IPv6 at all. Anyone else getting this?

edit: it looks like Safari must run dns requests both as IPv4 and IPv6 and uses whichever returns first. Refreshing a few times found the IPv6 is ready message on ipv6.google

zaphoyd··on [dead]
Intel and Apple should market Thunderbolt not as a peripheral interconnect designed to compete with USB but an external PCI format designed to let you connect PCIe style devices (video cards/displays, RAID cards, realtime AV, docking stations, specialty or future ports -- USB3? 6Gbit eSATA? Fibre Channel, 10Gig Ethernet) to laptops, tablets, all-in-ones, etc.

These probably aren't completely mainstream needs (is USB3 even a mainstream need though?) but they represent things that can only be done with traditional form factor PCs now. Why buy a Mac Pro when the only thing holding you back from a compact low power mini or laptop is some port you can only get a on PCI card?

zaphoyd··on Adventures in IPv6: Reliability and privacy concerns
Regarding the IP address privacy stuff...this can already be a problem with IPv4. At home, Comcast gives me IPv4 DHCP leases that get renewed to the same address for many months at a time. At work I (and most other employees) have a static IPv4 address. There is no way with IPv4 to do something like RFC3041 IPv6 random host addressing.
zaphoyd··on Find sites sharing the same IP address
Not that anyone probably cares, but it doesn't work for domains that only have an IPv6/AAAA record. An interesting option there might be to see sites that share an IPv6 prefix of a certain length?
zaphoyd··on IPv4 is depleted: Final five blocks allocated to registries
These guys have been mapping the IPv4 space via ping over time (since 2003) and have an interactive browsable map that also shows blocks marked for localhost/private networks/multicast, etc and which registrars control which regions. It is pretty neat. Most recent data is Nov 2010. Since then the 11 /8 blocks that show as free have been allocated.

http://www.isi.edu/ant/address/

zaphoyd··on IPv4 is depleted: Final five blocks allocated to registries
This is happening already. All of Verizon's currently shipping LTE (4G) devices have native IPv6.
zaphoyd··on Ask HN/PG: Why are comments being paginated?
When did this start? I read almost exclusively through the ihackernews.com mobile site. I just checked and it does not implement the more button and only shows the first 40 or so comments. It looks like I have been missing out on the end comments of popular threads without realizing it. :(
zaphoyd··on Running out of hex words?
IPv6 will provide another market for readable hex words

host www.v6.facebook.com www.v6.facebook.com has IPv6 address 2620:0:1cfe:face:b00c::3

zaphoyd··on World IPv6 Day: firing up the engines on the new Internet protocol
The Norwegian companies A-Pressen Digitale Medier (http://www.apdm.no/) and VG Multimedia (http://www.vg.no/), both news publishers with non-technical audiences, had similar experiences. The IT group that helped them set it up published the results of their experience and brokenness testing here: http://fud.no/ipv6/
← PreviousPage 8 of 9Next →