Live data from Hacker News

"@" on Twitter

twitter.com

121–130 of 143 posts

Re: "@" on Twitter

#121
post #87

It seems a bit gross when usernames and normal pages are mashed into the same namespace, e.g. https://twitter.com/search I guess Github does the same: https://github.com/pulls Reddit has the nice /u/... thing, but I suppose that is a bit awkward when saying URLs out loud.

This is a real problem. It's also a security issue.

One of the reasons why we created this database of huge disallowed usernames: https://github.com/dsignr/disallowed-usernames

Re: "@" on Twitter

#122
post #62
post #37

Earlier quoted context omitted.

people griefing in online games (hacks/aimbots) often run with nicks like ||||||||||II||I|||||||||||||II1111|||||||IIIIIIIIII||||||||||||

I used to use aim chat booters by a blog named 'esoteric code' program was called subterfuge. Familiar with it by any chance? I thought it was brilliant.

(not downvoting you, but your comment makes no sense at all to me)

Re: "@" on Twitter

#123
post #55

Earlier quoted context omitted.

JavaScript does. var arr = ["one", "two", "three"]; arr["2"] === "three"; // true

JavaScript object property keys are always strings, so technically it’s `arr[2]` that has the 2 coerced to a string.

It's true that object keys are strings, but the array and object situation of JavaScript is quite confusing. Arrays are indexed by numbers, but still accept string indices, leading to behavior like this: https://stackoverflow.com/q/9526860

Re: "@" on Twitter

#124

Earlier quoted context omitted.

Mobile Twitter is maybe the single most useless website I’ve ever had to use lol. Clicking on a link to a tweet has 1/20 chance of ever actually loading the tweet. All other occurrences are evenly split between loading nothing except the top bar and calling it a day, and throwing an error message. Reloading the directly or using the reload button they provide will usually result in the rate limiting message. I don’t…

I blame SPA’s. Nearly impossible to test properly (or was), breaks the whole html model, results in bugs just like this one.

This bug has nothing to do with Twitter's SPA-ness; it's a failed server-side validation.

Re: "@" on Twitter

#125
post #8

That must be Bobby Droptables twitter account :-)

The modern twist to that seems to be little miss Infinity https://www.reddit.com/r/javascript/comments/8f57i1/psa_ther...

Do I get this right that jQuery, for developer convenience, content-sniffs the value of "data-" attributes?

I.e., if the value looks like JSON, it will parse it and return the object tree, otherwise it will return the original value as a string?

This sounds like a horrible idea in general - I'd say the authors of this forgetting that certain english words by themselves are valid JSON is a nice cherry on top but hardly the worst problem caused by this.

Re: "@" on Twitter

#126

Slightly related but very interesting: the 2010 Twitter bug where simply tweeting "Accept [username]" would automatically force them to follow you. My understanding is that for the sake of simpler interfaces such as SMS, which they let hold the whole service back for a long long time, they had a "follow [username]" feature - and if the person had to approve follow requests, it would send one to them. To accept the re…

“Next time you make a seemingly obvious mistake, don't feel too bad. Even Twitter did it.” There most infamous “mistake”, at least as I see it, was neglecting to backup their database data. That was just unforgivable.

Their

Re: "@" on Twitter

#127
post #55

Earlier quoted context omitted.

JavaScript does. var arr = ["one", "two", "three"]; arr["2"] === "three"; // true

JavaScript object property keys are always strings, so technically it’s `arr[2]` that has the 2 coerced to a string.

Actually, that is incorrect. Arrays are different in JavaScript. I don't have time to look up the exact reference, but to get an idea: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe...

> Arrays cannot use strings as element indexes (as in an associative array) but must use integers. Setting or accessing via non-integers using bracket notation (or dot notation) will not set or retrieve an element from the array list itself, but will set or access a variable associated with that array's object property collection. The array's object properties and list of array elements are separate, and the array's traversal and mutation operations cannot be applied to these named properties.

Re: "@" on Twitter

#128

Earlier quoted context omitted.

http://php.net/manual/en/language.types.array.php First sentence, “An array in PHP is actually an ordered map.”

I just read at least half that page and this idiotic design confirms exactly why I feel PHP should be considered harmful

I don't think it's harmful. You just need to know what you're doing. PHP gets a bad rep round here unfairly. It's actually a very useful language which has proven itself over and over again in the wild. I wonder what you think of JavaScript?

Re: "@" on Twitter

#129
post #87

It seems a bit gross when usernames and normal pages are mashed into the same namespace, e.g. https://twitter.com/search I guess Github does the same: https://github.com/pulls Reddit has the nice /u/... thing, but I suppose that is a bit awkward when saying URLs out loud.

Anecdotally, practically anyone who's part of "US internet culture" of my generation (I'm 28) understands what you mean when you say "arr slash worldnews" and how to navigate there.

Re: "@" on Twitter

#130
post #125

Earlier quoted context omitted.

The modern twist to that seems to be little miss Infinity https://www.reddit.com/r/javascript/comments/8f57i1/psa_ther...

Do I get this right that jQuery, for developer convenience, content-sniffs the value of "data-" attributes? I.e., if the value looks like JSON, it will parse it and return the object tree, otherwise it will return the original value as a string? This sounds like a horrible idea in general - I'd say the authors of this forgetting that certain english words by themselves are valid JSON is a nice cherry on top but hardl…

Sort of - there's a jQuery API that does content sniffing called .data(), it's for storing and retrieving arbitrary data on elements. The problem was that they used this API to read from an element where they should have used .attr(), which returns a string.
Post reply on HN