This happens with physical addresses too, for similar reasons. The ABC (Alcoholic Beverages Commision) tracks complaints against physical addresses, and too many violations will get an address banned from permits. Then a new owner comes in with a new business and gets mysteriously denied for a liquor license, even years later.
It is customary to revoke the right of a business to name itself if there were too many violations. If you've ever gone to a nightclub or bar which has no name, only its street address number, that's what has happened there.
Before you buy a domain name, first check to see if it's haunted
171–180 of 195 posts
Re: Before you buy a domain name, first check to see if it's haunted
#172Earlier quoted context omitted.
So much of the world is still based on who you know. This is a bug in our society I would really, really like to see fixed in my lifetime.
Reframe: It's not that the smooth path you can get via nepotism is the base way things work which people who don't "know a guy" are excluded from. Rather, everything is falling apart and shitty, and if you're lucky, you occasionally get to circumvent that shittyness.
Well, obviously it isn't if you're not in the 1%. If you're in the 1% then that's the way the world has always worked and you don't know anything differently.
Re: Before you buy a domain name, first check to see if it's haunted
#173This happened to me and I found this tool super helpful to get my site unblocked: https://dnsblacklist.org/ I purchased a valuable premium domain to host a personal art collection (of anime cels). For some bizarre reason, the site was inaccessible from my work computer and it was de-listed from Google even if I typed the url itself into search. I hired a square space specialist to figure out why, to no avail. I then…
I had no idea such a thing existed.
If you can set up your own domain why would you need someone that specializes in a super limited non technical frontend for customizing prebuilt web templates?
Re: Before you buy a domain name, first check to see if it's haunted
#174Earlier quoted context omitted.
I'd be somewhat interested in seeing the cels. :)
https://www.neotokyo.com I have a +100 cel backlog that I need to catalog and photograph. Was planning to do it this holiday season so check back in.
Re: Before you buy a domain name, first check to see if it's haunted
#175Earlier quoted context omitted.
Well, current approach guarantees you’re getting screwed over. Any improvement is beneficial unless it blocks a better approach?
You're looking at this from the perspective of a haunted domain owner. And from that perspective your idea is fine. A good technique to evaluate ideas though is to try and view it from different perspectives. In this case from the owner of a non-haunted domain. Can you see any potential problem with your idea when viewed from that perspective? Now, if there are potential problems, consider the relative sizes of the t…
Re: Before you buy a domain name, first check to see if it's haunted
#176Earlier quoted context omitted.
This doesn't work because there's a nearly unlimited supply of people willing (out of desperation, drug addiction, or just plain poor decision making) to let bad actors use their IDs.
Also, all that info has been leaked a billion times now, and there are tools to allow real-time filter/overlays of faces to make it even easier.
Re: Before you buy a domain name, first check to see if it's haunted
#177Earlier quoted context omitted.
Also, all that info has been leaked a billion times now, and there are tools to allow real-time filter/overlays of faces to make it even easier.
It's what banks are using now.
Still, an improvement over what they were previously using I guess?
Re: Before you buy a domain name, first check to see if it's haunted
#178Another variant of this is cached or preloaded security configurations. HSTS (which forces browsers to validate HTTPS when connecting) asks browsers to cache the configuration for a set "max-age". Some sites set huge values here, like Twitter's 20 year max-age[1]. There's also the preload lists [2] to consider. This creates a problem if you want to serve non-HTTPS/unencrypted HTTP on your new domain and the previous…
So the sender is supposed to obey the normal DNS TTL caching period, and re-query the assertion record if TTL expired. It should re-fetch the MTA-STS policy if the 'id' value in the DNS assertion changed, or the max_age in the previously fetched policy has expired.
Re: Before you buy a domain name, first check to see if it's haunted
#179Earlier quoted context omitted.
A carfax report lists issues with the actual car . You don’t want a car with “car exploded” in the carfax report, since this would translate to actual damage in the car, damage which could actually affect you if you were to drive the car. On the other hand, a domain reputation at Google et al. is more like Carfax reporting “This car was once parked at the same street where a horrific mass murder took place.” If this…
But in this scenario there are many more parties involved than just "the police". So you can't "just fix the police behavior" for a "solution". You'd have to "fix" any and every party that already exists or pops up in the future. This kind of issue is inherent to any system where identifiers are recycled, particularly when that recycling happens on demand. It's not "fixable", at best it's combatable. And trying to la…
If it was a reputation problem where, say, end clients with web browsers would each have a separate and uniquely derived negative opinion about domain names, this would indeed be a “bad reputation” problem and not a Google problem, since the problem could not be fixed at the Google side. But with domain reputation being so centralized, the problem is at the center.
Re: Before you buy a domain name, first check to see if it's haunted
#180Earlier quoted context omitted.
A system gets reset, what happens in obscure places like old HN content?
The search index knows when the first time it saw that old link was. If it was before the reset, regard it as pointing to a different domain than the current one.
A google rank at zero and lots of 2 hop routes to your site that google can either penalize for being an accurate historical record or not is better than a rank of zero and a domain that has never been in historical artifacts.