Hacker News Reader

Comment by Spare_account | Hacker News Reader

https://twitter.com/SwiftOnSecurity/status/13711918852686725...

> What's possible is a Twitter staffer tried to block a street address, but the postal syntax acted as an escape sequence, or the original was multi-line and they only pasted the city.

What postal syntax in the US looks like an escape sequence?

View on HN

Probably the comma faking out a CSV parser? US addresses are typically written like "123 Fake St, Memphis, TN 38002" with commas between the street address and city, between the city and state, but not between the state and ZIP code.

e: I wonder if somebody with a large handful of accounts to burn could narrow down the intended block target by tweeting every combination of "{states_containing_a_memphis__abbreviation} {ZIP_code}" until one of them gets blocked? http://www.city-data.com/zipmaps/Memphis-Tennessee.html

I got blocked too, and so was referring to the ancient Egyptian city.

https://en.m.wikipedia.org/wiki/Memphis,_Egypt

IIRC, Memphis, TN was named after the great city in Egypt and even has a Pyramid, although it may be a shopping center.

I've heard it's a giant Bass Pro Shop. Incidently, I'm driving by Memphis this Tuesday - now I'm inclined to check it out!

There's a great recent video on the Memphis Pyramid from Bright Sun Films [0] - 10th tallest pyramid in the world!

0: https://youtu.be/FEB-YG2iiYA

I meant separator token, sorry.

Very easy to imagine a , or a \n being directly before and/or after a city name.

I'm a bit surprised that this username wasn't already taken.

Could be a typo or filling in whatever field incompletely - e.g. they meant to block a specific street address but only got the city name in the "block" field.

Reply on news.ycombinator.com