Live data from Hacker News

Yo

techcrunch.com

91–100 of 101 posts

Re: Yo

#91
post #85

Ridiculous as this sounds, there's a very interesting conversation happening on Twitter with Marc Andreessen about this apps' uses. Apparently, the "missed call" phenomenon, where people will call someone else and hang up, is incredibly popular, especially in other countries (e.g. Bangladesh). It's a free way to communicate 1 bit of information, which in many cases is enough if the people know beforehand what they wa…

When I was in high school our local mobile networks brought out a feature called "Please call me" in which you used USSD to send an unbilled notification for another number to call you - you only got around 20 per day but that was more than enough. Most people seemed to use it to notify their parents that they were ready to be picked up from a prearranged place much like you're describing with missed calls.

Re: Yo

#92
Seeing all these deep critiques/breakdowns of this product makes me feel like I'm in 10th grade english class again.

Re: Yo

#93
post #5

It's Facebook's "poke" feature (which I honestly love) in 2014. There's nothing wrong with it, but I struggle to find anything novel about it.

Poke is for attention whores. Excuse my slang. If you have something to say then say it. Otherwise what's your need to get someone else to initiate conversation?

Re: Yo

#94
post #85

Ridiculous as this sounds, there's a very interesting conversation happening on Twitter with Marc Andreessen about this apps' uses. Apparently, the "missed call" phenomenon, where people will call someone else and hang up, is incredibly popular, especially in other countries (e.g. Bangladesh). It's a free way to communicate 1 bit of information, which in many cases is enough if the people know beforehand what they wa…

The "missed call" is not a phenomenon. Most cell phone callers (not the receivers) in the developing world are charged by the minute for each call. Hanging up before the call is answered incurs no fee. This is simply a way to save money.

Yo is ridiculous and doesn't necessarily solve any problem that is not solved with existing messaging apps.

Re: Yo

#95

Earlier quoted context omitted.

What is the number 840?

6*140. But as your sibling comment points out twitter is not based on octets but on code points so there is actually a lot more information in there. I made the assumption that the limit was the 140 byte limit from GSM messages with a 'payload' of roughly 6 bits per character position but as was pointed out it is in fact now 140 UTF-8 code-points. https://dev.twitter.com/docs/counting-characters

Yeah, I'm familiar with tweeting in Japanese, and how much more information you can get across in a tweet, which made me question the number. However, I'm still not sure why (in an imaginary world where twitter doesn't encode in UTF-8), it might be 6-bits. 7 or 8 I can understand. I'm just curious of what your thinking was, not trying to do any one-upmanship.

Re: Yo

#96

Earlier quoted context omitted.

6*140. But as your sibling comment points out twitter is not based on octets but on code points so there is actually a lot more information in there. I made the assumption that the limit was the 140 byte limit from GSM messages with a 'payload' of roughly 6 bits per character position but as was pointed out it is in fact now 140 UTF-8 code-points. https://dev.twitter.com/docs/counting-characters

Yeah, I'm familiar with tweeting in Japanese, and how much more information you can get across in a tweet, which made me question the number. However, I'm still not sure why (in an imaginary world where twitter doesn't encode in UTF-8), it might be 6-bits. 7 or 8 I can understand. I'm just curious of what your thinking was, not trying to do any one-upmanship.

Well, 'ascii' is ' ' to 'del', above that I can't even type on this keyboard with any reliability so that gives an upper boundary for me of 96 characters. Of those the actual information is carried mostly by the letters, A-Z, twice if you want to count uppercase and lower case for 52 letters, 10 digits, a space. So that's 63 letters. Round up to 64 (maybe add the @ character or the # if you want, those are pretty prevalent in tweets as well). That's approximately 2^6. If you drop the lowercase/uppercase distinction then you can fit all the other ASCII glyphs and punctuation marks in the second half of your imaginary 6 bit code. You can't enter anything below <32 in a tweet, other than a linefeed.

Re: Yo

#97
post #77
post #67

Earlier quoted context omitted.

Can't wait for the Facebook clone. They should call it "Poke". Oh wait.

"Like" would probably be pretty appropriate...

Reminds me of Reverend Harry Powell, an itinerant technology evangelist, con artist, and serial entrepreneur with the words "LIKE" tattooed on the knuckles of one hand and "POKE" tattooed on the other, who would explain this fact to his victims by using his hands in a sermon about the eternal struggle between doing no good and doing no evil.

Re: Yo

#98

Earlier quoted context omitted.

>New startup idea: an app that only lets you say "hey" to people. "It's like Yo, only with 'Hey' instead of 'Yo'"

It's "Yo" for "Hey"

Scott Brown would have something to say about that: https://www.youtube.com/watch?v=rNkMwnsWdjc

Re: Yo

#99

I just Yo'd about 15 times back and forth with a friend. He just texted me "What's Up" Mission accomplished I guess?

Everybody is laughing now but soon they launch: Yo, buy this! Yo, emoji pack, Yo, plus! Yo, for enterprise. Then suddenly their the next whatsapp.

"Yo Glass!" + "Gee, Yo Location" = "Yobiquitous Computing"

Re: Yo

#100

Earlier quoted context omitted.

No, really don't do this, you could get someone killed like that (priority traffic causes tons of traffic accidents annually, if they follow up on a 9/11 when there is nothing wrong you are in very hot water, and rightly so). There are a lot of situations where one bit communications can make big changes. Sending a voltage down the wire to the 'launch' relay on some missile will do a lot worse. In the end, any actuat…

A technical note: Twitter carries unicode messages; the limit is not 140 octets but 140 code points [0]. This is especially useful when tweeting in Japanese. I believe there are more than 65536 code points assigned so a tweet should be able to carry over 2240 bits of information -- 2240+ Yos. --- Incidentally, in Japanese and BEV (probably adopted from jp), the word "yo" has an entirely different meaning. [0] http://…

"YoTor" could push innocuous "Yo" messages out over disposable one-time use IPv6 addresses, and all of the side-band message data could be transmitted in the IPv6 address. "The source address is the message."
Post reply on HN