I feel the complete opposite - I used to Google for specific tweets I remembered seeing and to help find tweets relating to current events. Google was much better about showing me the stuff I wanted to see than the actual Twitter site!
Wonder what is more valuable: showing tweets along the search results or being able to use them to rank other search results?
Especially for stuff that is happening right now, tweets probably contain pretty good information on what are the most relevant sources of information. And since the text part is show short, it is easier to match what this tweet is related to.
Its going to be heavily censored anyway, Twitter has an excessive amount of trolls, harassment and negative tweets in regards to any major social news event. There is no way Google will let that hit the search results.
Cool! Quick back-of-the-napkin indicates that the RTT for LEO satellites (at the upper bound) would be only ~4.7% of the RTT for GEO satellites. I'm sure there's much more to the story that I'm missing, but an LEO satellite should have a latency of around 11.75ms. In 2012, average US latency to Google was ~50-60ms . Would bandwidth be the limiting factor?
That's just it: It does. Line for line, character for character (even space for space, which is important in Python). I wouldn't say what I did above without having diffed the file against the code displayed first.
I just don't get the mentality here sometimes; someone creates a helpful script, puts the source code on their site for you to read and study, and the first instinct is to assume they have malicious intent before even taking a few minutes to read over it first. Hell, I'm no programmer but I know enough about the basics to follow exactly what the code does. It took me all of five minutes to decide that it flips two switches and nothing more. That the programming gods here can't or won't do that is telling.
I get being paranoid about random scripts, but this one is on display for all to see before running. There is literally nothing hidden, yet you all act as if the author is trying to secretly take over your machines. It would be funny if it wasn't so pathetic.
It is an https request. The internet is not bulletproof. What if your SSL cert expires, or due to being on the front page your webhook is timing out? Do you expect paypal to keep trying that IPN indefinitely? I hate paypal and all my new stuff uses stripe but any system that relies upon a request being made to notify of a transaction is not going to be bulletproof due to the nature of the internet.
The Myopera forums are rife with users complaining about missing features in the Opera 15+. Any unique features which distinguished Opera have been axed and most solutions seem to point towards using browser addons to accomplish what was previously in-built. They might have gained a few users, but it appears the majority of the current userbase will be sticking with Opera 12 for the time being.
Yes, but from what I understand their plan is to bring back most of the features in the future (I remember them mentioning specifically bookmarks, opera link and tab thumbnails), until then: Opera 12.
On the other side Chrome based Opera is also starting to look pretty good in it's own rights: it's fast and snappy, mouse gestures are there if I'm not mistaken, page stack (or whatever the name is) is cool. If I would to choose between Chrome and Opera 16 now I would go with the latter (also because Chrome really pushes too much Google on the user).
I heard that they ditched the fit-to-width feature (ctrl-F11), do you know if this is true?
It's one of those features other browsers simply do not have (Opera has a couple more but this one's pretty unique) that I really do use several times a day, and I'm not "upgrading" until I know they won't take that away.
Not that it matters too much, features or not, I'm thinking to switch to Firefox because these are times no longer to be using closed-source software.
Fit-to-width did all kinds of magic at a layout engine level — it's not that simple to just reimplement on top of a new engine. And then there's the question as to whether Google would let an implementation would ever get upstreamed to Blink.
I think you're generally correct about users not caring about the rendering engine for the most part. I wouldn't care at all that they ditched Presto if it meant they retained all the previous features and user interface they had before transitioning. However, I am worried that is unlikely to happen.
Looking at the course Blink based Opera has taken thus far, it doesn't look like they're focusing on keeping current users happy (any new user base is going to be an uphill climb). It's still new, but as a consistent Opera user for almost a decade, I'm very skeptical of them keeping all the previous customization as well as avoiding "Chromisms" in the UI.
I still use Opera 12 because of the lack of features in the new version. My biggest pet peevs: Ctrl+Tab behavior (Opera default was 'previous tab' now it's 'next tab') and no thumbnails tabs on the left, and they removed the email client.
Yeah, I dislike both of those changes as well. I have a pretty long list of things Opera needs to add to versions beyond 12 before I will update to their Blink version. Until then, I'm still using 12 as well.
So you are suggesting them to maintain two different codebases during the transition rather than focus all their efforts to the new version to make the transition as short as possible?
IMHO they did the correct choice, every new version Opera will difference itself more and more of Chromium. You can continue to use Opera 12.16 until they take the decision to pull the trigger to completely kill 12.16 auto-updating it...
Remember the transition from Firefox 3.6 to the current Firefox, they didn't kill 3.6 until they reached version 12.
How do you increase you're competitive abilities by removing everything that made you unique when you're already the underdog? :S
I'm not going to say that your fingerprints won't fall into the wrong hands, but it's incredibly simple to monitor network traffic from the device, and it's a guarantee someone will do this just to see.
It's also a guarantee that Apple knows this, so why bother lying?