6
points
app
Joined 147 karma
- app parent"These people wanna see a lobstah!"
- Based on your replies I doubt there’s anything that would actually convince you, but as it happens the data is pretty public and there are plenty of charts charts:
https://bsky.app/profile/jaz.bsky.social/post/3lamm7liwrc2w https://bsky.app/profile/jglypt.net/post/3lahqd45qqw2y https://bsky.app/profile/alice.mosphere.at/post/3lac4bbxhty2...
- Oy. How does a site like this even make it to the front page? America's Frontline Doctors is a right-wing cutout full of the usual conspiracy theorists and ghouls: https://en.wikipedia.org/wiki/America%27s_Frontline_Doctors
This domain is as fake news as they come.
- I got Frontier after moving into a house with no internet in upstate New York ("Upstate" being 100 Mi north of NYC). I ordered the 20Mbit plan and after missing and having to call to reschedule 3 installs (w/ 12 hour windows), the first words out of the installers mouth was "you got scammed". Indeed our signal was so weak we were only able to sustain about 0.5kbps. They wanted $75/mo for this and made it as hard as possible to cancel.
The basic history of Frontier in my area is that they bought up all of Verizon's old copper lines and have done exactly nothing to improve the capability. They don't even know what the capabilities ARE. Areas are either oversubscribed or so far from nodes that the signal is worthless. They're trying to squeeze every last cent out of rural houses with no other options and letting the underlying infrastructure slowly fail.
I ended up using a pretty performant (~50Mbit) LTE connection, hacked AT&T hotspot and yagi antenna for 2 years. Finally, as part of a rural broadband grant program New York State got Altice to come in-- probably in exchange for a monopoly in a more attractive part of the state. Now I have 300Mbit cable for $100/mo. Altice (aka Optimum) is also a terrible company, but Frontier still sends me postcards claiming to be "the best internet in <my town>".
These guys are selling a product that doesn't work. They deserve to be sued and I'm disappointed that New York State isn't involved.
- I think you are thinking of these recent photos of an F-22: https://www.thedrive.com/the-war-zone/29218/these-images-of-...
However you're no doubt correct that radar absorbant materials is high maintenance on any aircraft.
- I was on a Northeast Corridor trip once when the train was struck from the side by a rock. It sounded like a gunshot went off inside the car-- everyone jumped and there were more than a few shouts. I can imagine being hit head-on by a rock at night would be enough to distract an engineer for a few critical minutes. What a shame.
- There's an associated blog post too: https://vimeo.com/blog/post:640
- There's several more here: http://turboencabulator.tumblr.com/
- New York, NY / San Francisco, CA (mobile devs only)
VIMEO -- vimeo.com/jobs
Looking for:
PHP App Engineers
Backend Engineers (http://bit.ly/JLMR3C)
Designers (http://bit.ly/InBF0T)
QA Engineers (http://bit.ly/KsY3BA)
Mobile Engineers (to be posted soon)
Mobile Designers (to be posted soon)
Stuff we use: PHP, Python, MySQL, Mongo, Redis, AWS, Solr, Hadoop, nginx, node. And pretty much any mobile platform.
- If you're looking for a less functional Hubot that's been around for years, why not use Last.fm's irccat? http://www.metabrew.com/article/how-we-use-irc-at-lastfm
It already does the whole "kick of a script with these params from irc" thing and can easily be piped to from any langage that can open a port.
- 1 point
- This caused a bunch of headaches at Vimeo while working on our iframe embed code a couple months back. If I remember correctly Safari (and now I believe Chrome 10) will not send cookies in iframe POSTs unless a user specifically navigates in that iframe. So for example clicking the "like" button in a Vimeo video wouldn't work right away. There is a workaround: you programmatically fake a POST right away, and the second POST works because the user has interacted with it.
This might be a nice "headache" for marketers, but there are legit uses. As a developer I'd prefer if browsers were consistent in their default handling of cookies.
- http://www.davidslog.com/2941069729/200m-page-views-per-week
Looks like the downtime isn't slowing them down much.
- There are two additional security features POST has that GET does not:
1- POSTs cannot be forwarded
2- some browsers (webkit only I believe) require a client to interact with a domain before they can POST to it-- this means iframes cannot POST.
When it comes to XSRF, they are equally (in)secure.
- Great article. I drew that very chart this morning trying to sort out the implications of this change.
> "As a side note, it would be great if MPEG LA would simply open up the licensing terms for H.264 and make it royalty-free forever for 1: browsers to implement it, and 2: people on the Internet to produce & sell video with it."
How hard would this be to do? Is that all that prevents FF/Opera/Chrome from supporting h.264?
- 1. On2 never went to market with VP8 before the sale to Google. To say that they weren't sued for something they didn't release doesn't prove anything, especially since VP8 was marketed as a evolution of VP6.
2. See #1, they licensed VP6 not VP8/WebM.
3. No doubt!
4. Google does not indemnify users of WebM (http://www.webmproject.org/license/software/). If someone were to sue you for WebM, it's not an attack on Google and they have no reason to pick up your legal bill. Sure, it's not unreasonable to assume that if many large companies adopt a technology it's safe to use, but it doesn't protect you from being attacked individually.
Armchair legal hand waving goes both ways.