octatone2

9 ms·

31.
by octatone2 13y ago
Just this past weekend I clicked a google link to Quora and there were so many steps trying to get to the discussion and answer that I ultimately just closed the tab and went on to another search result. Horrible "onboarding" exp
32.
Show HN: Give javascript errors prominence in Chrome(chrome.google.com)
1 points by octatone2 13y ago|0 comments
33.
by octatone2 13y ago
It was made "with these samples, in this order, from this song". Not made "with this specific software".
34.
by octatone2 13y ago
Rand not Ron, but I know reading is hard.
35.
by octatone2 13y ago
I think there is a generation who simply care not of privacy.
36.
by octatone2 13y ago
They simply need to own up to a poor implementation of a useful feature and take protecting user data more seriously.
37.
by octatone2 13y ago
"Work from the moment you wake up until you go to sleep." Depressing as fuck.
38.
by octatone2 13y ago
That was something you chose to do, just like sending out devices without leases or contracts was a choice you made. I don't see how you have any legal grounds to request that he give the device back to you.
39.
by octatone2 13y ago
Then it is yours to keep.
40.
by octatone2 13y ago
Leave out the snap sending part, just make it a friend request. Don't expose to the sender whether the number is not attached to account, it is accepted or rejected. User can or can not send snaps then.
41.
by octatone2 13y ago
The problem is they did not see it as a vulnerability, they touted it as a feature, and even made a blog post outlining how you could exploit it. That was the most WTF event in following this story.
42.
by octatone2 13y ago
No, via snapchat's delivery system; they obviously can map a phone number to username, therefor they can implement sending snaps to phone numbers (as a proxy) in place of a username.
43.
by octatone2 13y ago
Why is user info presented in the clear to anyone who asks for it via their api? Here's a more sane approach I imagine: Allow sending snaps to a phone number (rather than to a username - since you would not know it the time), and attac
44.
by octatone2 13y ago
Did you sign a lease or contract for said device?
45.
by octatone2 13y ago
<sarcasm> OP just wants to harvest Snapchat usernames to harvest mobile phone numbers. </sarcasm>
46.
by octatone2 13y ago
No.
47.
by octatone2 13y ago
Satire on the past few days of HN. Flowing loosely from Math vs. Lisp, Lisp vs. Scala, Clojure vs. Scala ...
48.
by octatone2 13y ago
The chart at the end needs a key, I have no idea what I am looking at. Should be on http://wtfviz.net/
49.
by octatone2 13y ago
Did you miss the errors column? :/
50.
by octatone2 13y ago
It was perfectly clear, I don't know what the parent is on about with blackmail.
51.
by octatone2 13y ago
Not really.
52.
by octatone2 13y ago
A lot of your assets are not retina compatible. Specifically your logo image: https://d2avfbmbvwlo8q.cloudfront.net/assets/logo-fd9cab1e82...
53.
by octatone2 13y ago
This depresses me.
54.
by octatone2 13y ago
TIL youtube is text with the occasional image.
55.
by octatone2 13y ago
Are normal tickets called "boy tickets"? Are they required to be in blue lanyards? Will women caught with blue lanyards be kicked out of the conference? -_-
56.
by octatone2 13y ago
Sorry, you had issues signing up. We patched that bug within 24 hours. You shouldn't have issues signing up anymore with the packaged chrome app.
57.
by octatone2 13y ago
Yes, two wrongs make a right! It all makes sense now.
58.
by octatone2 13y ago
They may want to fix that JS heap spray exploit first in their ESR ...
59.
by octatone2 13y ago
> The ability to sue for millions of dollars is the one "advantage" That isn't necessarily true, as some states have caps on tort damages, and more corperations are lobying for similar caps/limits on civil restitution
60.
by octatone2 13y ago
I really want to test drive this! :)

More ›