So I went to a little bit of a deep dive regarding this, they do require interrupting DNS as part of their Redemption grace period. Furthermore I went into the hexbear website and their current header indicates that despite the fact that it's in current auction the current owner can still sign in and redeem the domain. Which makes me think that they're running a more gracious rgp then what is to be expected. So that being said they could just be placing bids on a domain that won't actually sell.
Being said though apparently according to other comments the infrastructure maintainer of hexbear has been AWOL for a while so it's entirely possible that they just won't notice it that it will transfer
The way I see it, there's a few things that may have happened here.
Either the domain registrar incorrectly processed their expired domain system and sold the domain without interrupting DNS in which case a third party bought it and then immediately put it to auction (unlikely cause the status / NS is the expired servers), this route would open up the domain registrar to a complaint being filed against them via ICANN
Or their domain registrar had a 30-day preemptive period where they were messaging the person, and then an additional few days with auction rgp that's the actual official last call for it, if this is the case then hexbear's infrastructure admin should be able to just sign in and renew the domain, but they may be forced to pay a Redemption fee on top of it, if that's the case then when they renew the domain, the auction would continue running it's just when it ended no buyers would be selected because the original owner renewed
Essentially the same thing as one, however they never disabled DNS, and instead of it being a third party, it's themselves putting it out to auction on the tail end of the 30-day rgp window. If that's the case then like number one they're in violation of ICANN as DNS wasn't disabled.
Again though, this is off the consensus that they didn't disable DNS a month ago, which I'm leaning at because I haven't seen any comments regarding it nor have I found any ststus sites showing that the domain was offline
I must not understand it properly, how was the instance functioning during the grace period for the domain? I was under the understanding that the grace period still had the domain name disabled it's just the owner had the ability to renew it still
then once the grace period ended then it hit redemption period where it's auctioned.
If the domain expired 1/12, how was hexbear functioning for the last month(or was it not and I just didn't notice cause I don't interact with it)
in all fairness, most developers that are still passionate about code aren't looking for promotion anyway, because usually once you hit the management level positions you do far less code and more bureaucracy bullshit, and what code you do is usually limited to guidance or review.
Now being passed on raises or laid off? that might be annoying.
Good. This needs to be done. So many officials are just "resigning" as a sign of mutual respect as that is what is considered the norm, but honestly they should just wait it out (and if fired fight it out if there is legal recourse like this to do so), there's zero reason to keel over and let federal services get demolished out of moral obligations.
Honestly this really depends on how much you use the service $80 a year is probably four or five decent games that you keep forever versus every game that's part of the catalog which is constantly rotating. But if you are someone who plays a game once to completion and then never touches it again, using subscription-based services like this makes Financial sense, unless you're planning on using physical copies only and selling after
If you are more interested in games that you keep forever>! ignoring licensing clauses cause steam!< and you run on pc, I would highly recommend humble choice it's like 150/$160 a year and they give you like six or seven games a month that you can have forever, not all of them are great but in my opinion it's worth the money paid.
I feel like I need to add in this is being disingenuous. As someone who had the Ps3 during that time, for the most part PlayStation network was fairly reliable. With the exception of the 2011 Anonymous hack that took their entire system down for a month. But they came back and gave a handful of games free to everyone that was involved out of it.
Like sure it would be down for an hour or two at a time periodically during update windows, but that's standard and it was a mostly reliable service,
I would play the PS3 basically daily cuz I was a massive Cod fan at the time. I rarely ever had an issue of logging on and having the network be offline.
Because at the end of the day it's not worth it for the company, they don't have enough reputation loss out of not having the product available to Warrant the effort to put the system like that. They're not losing any money because the scalpers are still buying, Plus for some reason users aren't putting two and two together that if they didn't buy the scalpers products the scalpers would stop scalping and therefore the cycle just continues
If people would just stop buying cards at or above MSRP from third-party sellers, this problem would have been done away with 5 years ago
In my opinion they should have moved the entire series that way, that or implemented account based registration like the steam deck did, it's better than nothing tho
It's entirely possible the employee had more than one hat and was dabbling in customer service that day. it's not unheard of in the IT field for the buckets to mix when demand states it. Being said the better question is how you could mistake a shutdown/deactivate button as an apply button
apperently cloudflare thought the same as they removed the button from the panel the employee used lmao
100%, someone who used to sell the units the amount of confusion we would get from Grandma's coming in wanting to buy their grandkids a new console and having both the One X and the Series X out was tough to explain. It was always the same puzzled look of "who the hell greenlit that naming choice"
What I'm saying is that you have to look at the bigger picture. Not only Sony would be affected by that, back in 2011 when they were breached consumers were charged in the estimated tens of millions of dollars range. A figure that Sony only ended up having to repay about 15 million in settlement fees for after a solid year and a half.
Additionally, Sony still managed to go up in profit that year, despite the PR nightmare out of it. Going up from 1.2 billion after operating costs in 2010 to 1.4 billion after operational costs in 2011 and still made 1.1 billion in 2012 ( after the 172 million in damages was done)
I understand hating big business and their practices as much as the next guy, but I have a hard time getting a sense of satisfaction knowing that at the end of the day the company itself isn't going to be impacted by the hack more than a small itch, while fucking over the everyday consumer significantly more
The last time this happened was when Anonymous hacked PSN and took them down for a month after they went after Geohotz(cant remember the spelling) for jailbreaking/reverse engineering the ps3.
Radio silence like before as well. I hope they weren't breached again.
It was a good read, personally speaking I think it probably would have just been better off to block gotosocial(if that's possible since if seems stuff gets blocked when you check it) until proper robot support was provided I found it weird that they paused the entire system.
Being said, if I understand that issue correctly, I fall under the stand that it is gotosocial that is misbehaving. They are poisoning data sets that are required for any type of federation to occur(node info, v1 and v2 statistics), under the guise that they said program is not respecting the robots file. Instead arguing that it's preventing crawlers, where it's clear that more than just crawlers are being hit.
imo this looks bad, it defo puts a bad taste in my mouth regarding the project. I'm not saying an operator shouldn't have to listen to a robots.txt, but when you implement a system that negatively hits third party, the response shouldn't be the equivalent of sucks to suck that's a you problem, your implementation should either respond zero or null, any other value and you are just being abusive and hostile as a program
Yeah, even if that wasn't the intent that was the outcome. And honestly yea probably was done just using air tools, it's still blows my mind of how stupidly tight that was on there.
Thankfully though I live in a fairly low population state so there's never a line for any shops, usually most things can be a walk in or leave that night to have it worked on next day...you just have to be willing to drive 45 minutes to get to one. I do agree, finding a decent mechanic can be helpful, even if the only real work you ever need done is the yearly inspection.
So I went to a little bit of a deep dive regarding this, they do require interrupting DNS as part of their Redemption grace period. Furthermore I went into the hexbear website and their current header indicates that despite the fact that it's in current auction the current owner can still sign in and redeem the domain. Which makes me think that they're running a more gracious rgp then what is to be expected. So that being said they could just be placing bids on a domain that won't actually sell.
Being said though apparently according to other comments the infrastructure maintainer of hexbear has been AWOL for a while so it's entirely possible that they just won't notice it that it will transfer
The way I see it, there's a few things that may have happened here.
Again though, this is off the consensus that they didn't disable DNS a month ago, which I'm leaning at because I haven't seen any comments regarding it nor have I found any ststus sites showing that the domain was offline