In this context it was court orders, usually over an ownership dispute between corporations. The legal fees etc, make it unlikely to be worth the hassle.
I understand your sentiment here, but should the registry decide the domain is not theirs it will simply not be manageable from the registrar/buyer. All they do is update the management id to the new registrar and the registrant contact of the domain, no intervention is possible.
I can tell you I’ve seen legal orders transferring a domain from one registrant to another, if the order has the registry named to take action, the domain kind of just goes poof, sure it’s in your system but you can’t do anything against it.
2 Days ago management of .io registry was transfered from Afilias to Donuts (Due to an acquisition). It is likely that during that window you registered the domain and they are now cleaning up the issue. It may be your registrar took your registration and then when they went to actually process it the registry was down, so someone else got it during that period. It could be other things, however, the bottom line is that the domain was probably never yours and there is really not much to do here. It's bad timing and bad handling of a process on your registrars end.
one thing to keep in mind about new pans that are not as "smooth". That is entirely up to the casting medium, and if you want to you can simply clean the pan, sand it smooth then re-season. So a bit of work, but, much easier to go to a store than hunt for old cast iron at estate sales.
We kind of got off topic, I was arguing that if you were concerned about internal systems being down (including your monitoring/alerting) something like pager duty would be fine as a backup. Even at huge scale that backup doesn’t need to watch everything.
I don’t think it’s particularly relevant to this issue with fb. I suspect they didn’t need a monitoring system to know things were going badly.
This is not true when your the registrar (as in this case) in fact your entire system could be down and you’d still have access to the registries system to do this update
Agreed, it’s also worth mentioning that at the end of every cloud is real physical hardware, and that is decidedly less flexible than cloud, if you locked yourself out of a physical switch or router you have many fewer options.
Even if it can’t, it’s trivial to use it for an important subset, ie is Facebook.com down, is the ns stuff down etc. So there is an argument to be made for still using an outside service as a fallback
This is not completely accurate. The whole reason a registrar with domain abc.com can use ns1.abc.com is because glue records are established at the registry, this allows a bootstrap that keeps you in from a circular dependency. All that said it’s usually a bad idea, for someone as large as Facebook they should have nameservers across zones ie a.ns.fb.com
b.ns.fb.org
c.ns.fb.co
Etc…
See, I just went to ha. My hubitat experience was bad. For two years I had crashes, failed devices and failed automations. The last lockup I had I said enough. At least with HA I could get under the hood and deal
with an issue. Hubitat gui is awful and the rule system is tedious but powerful. It was just way too unreliable for me.
Speaking to Gizmodo, Epik said they were unaware that they had been hacked, but would investigate.
What's interesting here is that if you are an ICANN accredited registrar there is a window in which you must report a breach to them, may be interesting to find if they have/have not reported said breach.
Hubitat user here as well, It's ugly but has been pretty solid for me. It's definitely punching above it's weight class in terms of what it cost. Hubitat has a groovy ide so you can write your own integration if necessary and the community is pretty good, I've rarely found something that doesn't already have an integration.
I think we are missing some information. I know my wife will order items on a separate account, this means some days I get 4/5 packages delivered at the same time. I think a packages/day and stops/day metric would be more helpful
Here I was thinking I was the only one. I have a presence sensor under my desk, when I sit down it triggers the following:
1) Turns on my monitors and desk lamp
2) Turns on the tv in my office
3) Using an hdmi multi plexer sets the hdmi switch to have 4 screens 3-work, 1-with apple tv.
4) Changes a busy light to red outside my office so family knows I'm working
As you say it takes no time to get to work, I was really surprised how automating this helped me get going in the morning because on it's own none of this is terribly time consuming.
Agreed, extra credit when the docs use the key from your account so that you can just grab strait from the docs, I think it's stripe who I'm thinking of who does that, sooooo nice.
I seriously discount your api if I can't do my initial review via curl. As the author stated, having to do all this setup creates friction, your api is supposed to be solving a problem for me. If it just creates different problems you're not offering a good solution. If I can quickly see how it works via curl it will be that much easier to evaluate.
I would add to this; I’ve driven by billboards and actually wanted the phone number/website but didn’t catch it in time. So while like anything it could be abused. It also serves a useful purpose
I agree, I saw the author mention for $25k you could have 1000 keys. I immediately though that is not nearly enough. Given the sheer volume they have, they would start putting a picture together very quickly of ip/key/sites. There is no where near enough uniqueness.
I also thought the idea of the key exchange being fast was a red herring. That's a bad thing. If I'm them I'm paying attention to how long from prompt to exchange it takes a human to touch the button. On my own setup my key is on my laptop, which is in a dock. I must stand up and tap it over my monitor. It's just a few seconds but it's a) consistent in timing b) not < 1s. Imagine the aggregate timing data they have.
Overall they make some good points if you are teeny tiny player and ignore completely the scale cloudflare is operating at.
It’s insane they stopped pulling the thread and the defence didn’t push that, even if you spent it there would be evidence. I would have been highly skeptical that all of it just disappeared Into thin air across the entire group....nuts
TLD's have various compliance requirements around abuse, which does include the afore mentioned. There is significant volume related to this compliance as well as ensuring registrars maintain compliance. It's the nature of the existing arrangement so it's not hypothetical.
Of course the individual cost is low for a single item, however, businesses have never operated on that principle. They aggregate the profit and the risk across a pool, no surprise here.
They're half a dozen lines of text (counting glue records and DNSSEC anchors) in a database, it's OUTRAGEOUS we have to pay for that at all.
This is not what you are paying for. Every time this argument comes up it hides the real problem...what you are paying for is the legal wrangling, security overhead and general compliance that comes with the internet.
Phishing, trademarks, spam, business disputes,and valid legal requests will all still exist no matter who runs things. Those costs are what your domain fees really have to cover.
It’s been a very long time since domain costs were highly dependent on the technical requirements of the data they represent.
Yes, exactly this. In addition you don't really need other people. If you have actual cash, buy gift cards in cash yourself then purchase online. If you can publish one book thats giberish, then you can publish dozens. And it's trivial to have a dozen amazon accounts/email combos to make the purchases with.
This is not the crisis it's being portrayed as. Up until a year or two ago. .io was run directly by the ICB. It had issues as it's not straight forward managing root level dns and the other related tasks of a registry.
Since then a company called Afilias is running .io (they also run .org, .info among many others). Whoever maintains governance of the .io tld is separate from the actual infrastructure running .io. As long as the owners of .io want to keep cashing the checks then nothing will change as the whole operation is outsourced. This is similar to the island of tuvalu outsourcing all of .tv to verisign (they are the .com registry)
Agree, there is an old saying "What gets measured gets managed" These numbers are handy (we look at similar numbers) but they absolutely do not tell the whole story and it's dangerous to think they do. You can often find yourself optimizing the wrong area and in large organizations even marginalizing your best performers because they don't fit the mold.