flurp

^ Yes. Clearly people can't take jokes here, already downvoted.

Edit: Even the above got downvoted and I get reminded again that HN is full of stuck up, overly sensitive and unhumorous engineers. With the exception of this being a great place to find interesting things to read the community aspect is uninviting and unforgiving.

Yep. Apple have released many apps after similar ones had success on the AppStore.

They have much much harsher ToS (and enforce them) than the discussed Twitter ones.

100x less memory and was much more performant

Technically you're not prevented from doing so - you would just have to keep it to yourself (/family/friends/etc). Non-technical people rarely care about these things.

backstabbing developers

I don't disagree. Would be interesting if there are any stats on who/what made Twitter popular, got any?

And why is that a problem?

It's a problem for Twitter when you're trying to run a top-brand. Clients who don't keep up-to-date actually make Twitter look bad to the public. It also makes it harder for Twitter to innovate, move quickly (and probably get usage stats), without coordinating with external developers. Apple actually does (in some aspects) force developers to keep their apps up to date. I develop iOS apps and this actually consumes way more time than I wish it did.

Your concerns are valid from a third-party concern but from Twitter's first-party concern they are distractions.

I actually think they've been very clear on this from the beginning, including the reason why (although it wasn't spelled out).

They've always meant apps that offer more or less the same functionality as official Twitter clients.

For the people who actually read the terms instead of picking up their pitchforks back when Twitter had that big tos "change of heart" would have understood that They definitely could have handled it better and been clear that the user limit was really meant for Twitter-clones.

It's clear they want to control the way most people use Twitter, but also to show advertising. As best I can recall, the tos change came around the same time as they started putting in ads. Besides the few remaining twitter clones always play catchup when Twitter puts out new features (recent example; polls).

I think J-1 would be the most legally correct (IANAL and all but I have some J-1 experience). YC should be able to bring founders on board. Since J-1 is for education and the program is basically an education.

J-1 is also quite openly (ab)used to bring employees over who do not qualify for a H1B or O-1.

Only important thing to remember is to pay the J-1 "student" otherwise they are (depending on origin country, but most I think) subject to a rule preventing said person from returning to the US within two years.

I think J-1's are 18 months max. Plenty of time to get a business up and running. By that time if the founder is successful (e.g. take on more investment) they could probably employ themselves with a H1B or E-2 ("investor") visa.

But I'm sure the J-1 has a bunch of issues concerning founding legal entities - this part I have no experience or knowledge of.

He links to Visual Website Optimizer[1] as the A/B testing tool he will use. I haven't used VWO personally but based on their features page it's a point-and-click to change some visual details on the website. Install a javascript link and good to go. Again, haven't used the tool but doesn't seem like much work to me.

[1] http://vwo.com

"wiggle room": Username limit was 20 characters (or something like that). 20 for username, 140 for message.

I see a lot of (rightfully) upset comments but this doesn't really come as a surprise to me given that Twitter (and others like FB, GOOG, ad networks) already track websites you visit.

I know there are ways of blocking that but I would have a hard time believing that many (outside of HN readers) block that type of tracking.

"just" a browser with a lot of native technology baked in to enhance the experience. Playlist caching for one.

A drone could detect loss of communication with the pocket device (snow or falling into the ocean should be enough to do that) and start some recovery/emergency sequence. E.g. stop + try pinging the device, if there's still no reply automatically call 911 with an emergency and GPS location. Is there a 911 REST API? :)

For those asking/wishing for open source, according to the comments section[1] they will.

"We’ll release the usable parts of the code as free software with the most free license we can. It belongs to the community (and the community paid for it)."

[1] http://blog.brokep.com/2015/04/22/update-on-heml-is/#comment...

[Sorry for the multiple comment replies, I realized a top-comment might be better]

They will according to the comments section http://blog.brokep.com/2015/04/22/update-on-heml-is/#comment...

They will according to the comment section[1]

"We’ll release the usable parts of the code as free software with the most free license we can. It belongs to the community (and the community paid for it)."

[1] http://blog.brokep.com/2015/04/22/update-on-heml-is/#comment...

Seems they changed their mind about open source, according to the comments section[1] "We’ll release the usable parts of the code as free software with the most free license we can. It belongs to the community (and the community paid for it)."

[1] http://blog.brokep.com/2015/04/22/update-on-heml-is/#comment...

EDIT: I found better documentation on this.

Some US states require ID.

The person approached is not required to identify himself or answer any other questions, and may leave at any time

From http://en.wikipedia.org/wiki/Stop_and_identify_statutes#Stat...

http://www.quora.com/In-the-US-under-what-situations-are-you... --old:

Depends. A quick google found this: http://www.flexyourrights.org/faqs/when-can-police-ask-for-i...

As of 2013, 24 states had stop-and-identify laws. Regardless of your state’s law, keep in mind that police can never compel you to identify yourself without reasonable suspicion to believe you’re involved in illegal activity

Maybe the problem is the length of countdown timers? I don't know how they are determined and set but anecdotally I often see 10 seconds or sometimes others in excess of 15s or even 20s on a road that takes ~5s to cross.

It seems to me like this is a reasonable law IF the timers were set to only give the pedestrians minimal amount of time to cross the street. Given it takes 5s to cross, timer starts with 5 remaining. Pedestrians in the road see it and rush to either side. Pedestrians about to enter the road will have an easier decision to make: I can't make it in 5s so I wait. Obviously some will think they can, then fine them; I think that's reasonable. But holding up pedestrians with 20s remaining seems unreasonable to me.

The main problem I see is for slower pedestrians; seniors, handicapped etc. They might need more time and could be caught of guard in the middle of the street with no time remaining... An immediate thought would be a white flashing hand as a warning that time is running low (no counter!)... Probably requires lots of reprogramming though.

I applaud your courage to stand up to that but I don't know about following the advice after reading "i do often end up in court with cops over a lot of things, this included"... Confused.

I agree with the advice above, and adding on to it, as a founder... If the case is morally and ethically sound then I wouldn't hold it against you, probably applaud you. On the contrary if it's a shakedown of sorts I would be questionable.

As an exercise I would look into the recent lawsuit against VC firm Kleiner Perkins. Search the web for "kpbc lawsuit" and read how people have reacted to that case.

I've used some toolbar applications for this for years. The current one I use is Go2Shell: https://itunes.apple.com/se/app/go2shell/id445770608?l=en&mt...

But Cmd+T seems much easier. :)

Seems really cool but I felt my internal warning sign go off when I see the team is mostly comprised of marketers/managers/growth. Three engineers in an eight person team. It can still be a good product but I'll wait until it's on the market for some real reviews.

Maybe allowing users to have multiple API tokens, that way you have one for IFTTT and another for each service you set up. Gmail does something similar to this btw.

Although I agree with you, there's a good chance that people who reuse passwords do so because they don't want to remember usernames/passwords everywhere and by forcing the user to go get their API-token it's just making things harder for them again. But, maybe this just isn't a problem for Pinboard users.

Too bad about OAuth, it does solve both problems above. :)

Maybe sites like IFTTT are doing it because it's much easier to remember a username/password (assuming you don't use generated passwords) than an API token. A global third-party api token barely provides much more safety than giving up a random password to said third-parties. If you want to prevent one third-party app from continued access you have to go around to all the others and update the token (just like with a password).

Don't get me wrong, I'm in favor of removing user's passwords from third-parties (and blocking those who won't update). I'm just wondering why Pinboard hasn't built a proper OAuth system which would remedy all the above problems. It even mentions OAuth on the api docs: "This token is intended as a stopgap measure to prevent third-party sites from having to store Pinboard credentials while the site moves to full Oauth support."

It's well known (I've read articles and heard from inside sources) that service providers like FB and Twitter partner up with big carriers to make use of their app free for carrier customers. It's possible that these music providers have set up similar deals. But could also be that T-Mobile is creative with their offerings (which they're known for) and offer free music an USP against others like AT&T.

More like you can't do that in the USA because of insurance/liabilities. In most of Europe, assuming you found a friendly soul, they'd give you a hand. Liability is mostly an "american" thing. (I'm from Europe)

Unfortunately (in my limited experience with Lyft) the quality of UberX drivers are far better than Lyft drivers. Half the time in Lyft cars I've been worried about crashing! I'd rather pay that extra dollar or two and have a comfortable ride.

Great app! Would be great to estimate "regular" price, right now it's surging and I'd like to know what the price would be for e.g. tomorrow. Hopefully Uber wont shut you off, seems like a breach of ToS to me (I'm not a legal expert).

Check out Ramen: https://ramen.is not for iOS apps/games exclusively but with a core focus on software projects.

The real question is whether Verizon is saying "Use the other bridges" or "If you pay us we can open another bridge for you". What I've read mostly points to the latter and Netflix is either taking a stand against this practice or Verizon wants to much money.

I've been calling Facebook Notifications the Push Notification of the Web, they are great, maybe just as good as native Push Notifications. But they have also "solved" (it's new and yet to see) the spam problem recently by implementing harsh restrictions on how you as a developer can send them. It would be interesting if Apple and Google copied this behavior. Basically Apps that send > 50000 notifications a week have to maintain a 17% Click-To-Impression ratio. However I find the 50K an oddly picked number which should instead be based on installed user base.

This might be your point (didn't quite get your point) but that's exactly why you should fix this. You actually have separate inbound and outbound channels. It's rediciously simple to change those outbound channels' email addresses so that a direct reply will be sent to the corresponding inbound channel. It doesn't matter if the system is basic and uses a smtp server or if it uses a hot new email routing service. It's about setting the correct from address in your systems code.