5 ms·
QUIC at Snapchat
- colesantiago 5y agoWait, is this the same sexting app from years ago? Why would they be involved in QUIC?
- vorpalhex 5y agoNobody wants slow, laggy sexting.
- nefitty 5y agoApparently, my wife learns a lot of Excel tips on Snapchat. My friend’s wife and my wife got into a long conversation once about the productivity stuff they learned on Snapchat. My friend and I are a little older and never used Snapchat. We were surprised and confused. I do use https://map.snapchat.com https://map.snapchat.com occasionally when I’m feeling curious about what other humans are doing at this exact same moment on other parts of the world. I found posts from a community of Inuits once and learned about some of the food they eat.
- sergiomattei 5y agoCan't kill the vibe.
- totetsu 5y agoyou just gave someone flashback trauma about supporting MMS messaging.
- paxys 5y agoThey are a $100 billion company. They are involved in a lot of things.
- qqtt 5y agoFrom what I understand Snapchat has more daily active users than Twitter and also a user base growing much faster.
- tayo42 5y agowow that's surprising, and it looks like its a by a good amount of people. I feel like snapchat is thought of as a dying company and twitter seems to be known by everyone. Though I get the feeling most people don't think twitter is a place for them to participate in, them being regular people.
- rvz 5y agoMaybe Twitter has more bots on the platform than real users, which is why Snap is still alive. Given they are a $100B dollar company, they are far from 'dying'.
- sofixa 5y ago> Given they are a $100B dollar company, they are far from 'dying'. Meh, valuation isn't everything. Uber and WeWork also have high valuations, little tangible assets, but are bleeding money and have no clear path to profitability.
- rvz 5y agoSomehow they have more REAL daily active users (DAU) (not bots) than Twitter, twice as valuable than them and have already expanded out from being just an app but have an ecosystem of integrations in other apps and are still alive after being copied everywhere. Whereas the HN crowd 'thought' they either shut down or got acquired. As always, they 'thought' wrong. Again. It's hard to grasp the reality check here but they are far from 'dying'.
- samtheprogram 5y agoI have used Snapchat for almost a decade and never for sexting. Ephemerality and a lack of feeds make it a decent place for social media without social cooling. Direct messages and group messaging meanwhile can be saved indefinitely on a case by case basis (i.e. in the settings for the specific thread) and notifies the people you’re talking to of the change. It’s actually quite nice. Lack of discoverability (which they are sort of adding, but mostly for bigger influencers and/or publications) is a positive. In my opinion they don’t suffer from the same issues as the other platforms. For example, there isn’t any sort of liking mechanism. If you like something, you message the person directly. Maybe it’s a generational thing. That said, if I were to delete all my social media, I might keep Snapchat. It just isn’t the same. It’s more akin to Telegram but with a focus on photos. EDIT: thread/conversation expiration can be increased to 24 hours, individual messages can be saved indefinitely, or screenshotted. Either notifies the user you’re contacting.
- regecks 5y agoToday, are there any messaging frameworks similar to zeromq or nanomsg ng, implementing a QUIC transport? Looking to play with a bit. gRPC is a bit heavy for me and lacks a pure-C implementation.
- deleted 5y ago[deleted]
- gen220 5y agoI know you already mentioned it, but gRPC does support QUIC. If it helps at all, the C++ surface wraps a C core [1], which supports QUIC via an opt-in Cronet dependency [2][3]. If you wanted to roll your own messaging framework, you'd probably want to build on top of at least Cronet, if not gRPC core. [1]: The pure C core: https://github.com/grpc/grpc/tree/master/src/core https://github.com/grpc/grpc/tree/master/src/core [2]: A visualization of the stacks: https://grpc.io/blog/grpc-stacks/ https://grpc.io/blog/grpc-stacks/ [3]: https://github.com/grpc/grpc/tree/master/src/core/ext/transport/cronet https://github.com/grpc/grpc/tree/master/src/core/ext/transp...
- dargueta 5y agoNit, the core is not C ([1]), it's C++. So it's not really usable by anyone wanting a pure C gRPC application. [1] https://github.com/grpc/grpc/pull/24737#discussion_r522572629 https://github.com/grpc/grpc/pull/24737#discussion_r52257262...
- gen220 5y agoOh wow, I wasn't aware of this! Thank you for leaving this comment.
- flakiness 5y agoCronet on the client side is no brainer, at least for Android. It's Chrome's network stack. I wonder what they're using on the server side. Is there any obvious choice that is not even worth a mention, or they implemented it by themselves ?
- howolduis 5y agoSnaps speed? How about you actually use the camera on android phones?? snapchat doesn't even USE the camera on Android phones. Instead, it takes a screenshot of the screen, resulting ina terrible quality. It's really embarrassing that they're still doing this for a company this big...
- deleted 5y ago[deleted]
- sydthrowaway 5y ago"Snap.. a camera company". Hilarious.
- yellow_lead 5y agoThat was my first impression also.
- deleted 5y ago[deleted]
- tehlike 5y agoWait, can you explain this to me?
- RicoElectrico 5y agoSnapchat "takes a picture" by just grabbing a frame from the viewfinder instead of, you know, using the proper API. This could have made sense back when Android imaging situation was more of a mess, but the current API obviates the need for this.
- overitthrowaway 5y agoIt's likely just a case of "it it ain't broken, there's no budget"
- pta2002 5y ago
- KaiserPro 5y agoI know they are comparing to HTTP2, but objectively HTTP2 was never a great fit for mobile. I know its not the case, but when HTTP2 was being developed it felt like they were only thinking about users with strong wifi and zero packet loss. My company had a number of reps at the W3C, whenever I raised concerns with them I was told that I was being an old sysadmin, and that tcp doesn't work the way I think it does. They were convinced that multiplexing down a single TCP pipe was better than having a pool of connections. They were also convinced that the average size of webpages wasn't going to grow, despite lots of evidence to the contrary. I'm still not entirely convinced that quic is the way forward either. However I haven't spent enough time looking at it to form a proper opinion.
- AgentME 5y agoQUIC has the solution to the issue you brought up with HTTP2: packet loss no longer causes all of the multiplexed streams to be interrupted, but without the costs of using many simultaneous TCP connections.
- foobarbazetc 5y agoAs someone who's spent the last 11 days or so helping debug a bug in a live QUIC implementation, I'm... sort of unconvinced that it's a good idea in general. Every implementation (maybe not Google's?) is just a poorly designed TCP stack, where most of the code is just copy/pasted out of Linux or FreeBSD, and everything learned in those OSes about building resilient TCP stacks is just forgotten only to be rediscovered again. Not to mention that it's just a huge, huge pain to debug because you can't telnet or openssl s_client to a port and type out some HTTP. And Wireshark is basically useless even when you have your SSL keys saved. Here's a table of a bunch of QUIC implementations and their compatibility with other QUIC implementations: https://interop.seemann.io https://interop.seemann.io I mean... why? A lot of smart people are involved here so... there has to be a good reason? I'm not sure a couple of % is worth it.
- dargueta 5y agoI mean, it _is_ a Google project https://research.google/pubs/pub46403/ https://research.google/pubs/pub46403/ :)