178 karma · joined December 5, 2008
Even at 12 I could tell this guy was an annoying idiot. Loved the comic though.
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...
This domain is as fake news as they come.
It's also right on the front page of NYT.com
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.
However you're no doubt correct that radar absorbant materials is high maintenance on any aircraft.
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.
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.
2) Using a MO drive on the first NeXT box.
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.
Looks like the downtime isn't slowing them down much.
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.
> "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?
EDIT: Thanks, I guess the answer is no...
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.