Source: https://twitter.com/adampash/status/466316191230087168
3,217 karma · joined April 22, 2011
Source: https://twitter.com/adampash/status/466316191230087168
From what I understand, it's less of a deliberate "HAHA SCREW YOU" and more of a caching issue on their iMessage registration side. The removal of my number took around 24 hours to propagate to their services (e.g. if a person who didn't have a thread with me put in my number, it would show green not blue) and I had to have some friends delete our chat history since my iMessage-ness was cached on their phone.
I think Apple only checks iMessage registration in pull format, e.g. when someone toggles iMessage on/off on their phone, rather than constantly checking it through some "does this phone have service" background test.
However, all it took from me was a call to Apple's customer service, I told them I had just switched off my iPhone and no longer got texts from people with iMessage and they immediately sent me to a tech that fixed the problem for me.
Have you been explaining it correctly when you call? All I said was "I had an iPhone until last week, switched to another phone but I'm still registered for iMessage"
Edit: According to my phone I called 1-800-692-7753 (Which is just 1-800-MY-APPLE) and my call took 8 mins 25 seconds total. Not too bad of an experience.
There's some extra details in the speaker notes (in the JS console) here: http://kasrarahjerdi.com/se-goes-mobile/#/7
We're hiring full stack devs: http://careers.stackoverflow.com/jobs/34229/full-stack-web-d...
Head-Fi has excellent recommendations for all types of headphones (IEMs, closed, etc) at different price points.
- I optimized for compression by doing things the same way everywhere; e.g. I always put the class attribute first in my tags
- I wrote a utility that tried rearranging my CSS, in an attempt to find the ordering that was the most compressible
> As we approached the end of our runway, it became clear to us that DrawQuest didn’t represent a venture-backed opportunity, and even with more time that was unlikely to change.
It takes a lot to decide that you should kill something rather than try to funnel more money into it without having an end-game set up.
> Note that there are 6 separate encodings -- mp4, webm, and reduced mp4, for forward and reverse
I think SO and Server Fault are the size they are because they have an intrinsic advantage over our other sites. People in the target audience work and live in the same tech ecosystem as a website, with something like physics that's an initial burden.
SE itself also has a high barrier to entry. Every one of our sites has it's own rules and definition of what type of content is acceptable. This is for a very good reason, seeking out absolute answers to questions. Most other websites on the internet live to foster discussion, but we're not a forum.
Making stack exchange a common name (in more than our sizable niche) is one of our company goals, but I don't really know what we can do to get past the initial issue I mentioned and reducing the second would hurt our product.
It's quite an interesting idea to be more proactive about bringing thought leaders to out lesser known sites, I don't know if we could do it just directly since most thought leaders are very busy people who already have a dozen places people ask them questions but it's something to think about. We already consider expertise of contributors in Area 51, our incubator for new website ideas.
Perhaps while we may not be able to get the top 1% of thought leaders onto our websites without giving them a really hard question to answer (my mom loves difficult questions, god knows how many times she used to run into my room and say she solved a question I asked her in passing days prior) but it might be possible to bring in up-and-coming thought leaders. A lot of my friends from the health and fitness industry (were I used to live) might want to use our Physical Fitness Stack Exchange site to foster their own personal brand.
One of the things I consider a main detriment of our current product is that for the vast majority of users it's built to be transactional. Search, land on SO, read, go back to work.
On our currently in development mobile apps we're trying out something different, for the first time at scale we're pushing content to users rather than having them search for it as the number one utility of the product. The apps have a "Feed" which is machine learned interesting for you questions.
I love it since I search SO at work but when I get home or am walking around town I can open my app and instantly lose 30 mins (at least) to reading and interacting with very interesting content. I can't wait to see if others like it.
After you login to Uber.com it instantly does a GET to /api/clients/[PERSUMABLY_USER_ID]?parameters which would be in the logs or they might have logs of user logins on their side (to show users a 'you've recently logged in from...' list somewhere)
Also thanks for teaching me a new idiom :)
If you are actually interested, here's a report one of our sys admins did a couple years ago estimating how much it would cost to have us running on "the cloud" - http://meta.stackoverflow.com/questions/73969/what-would-sta...