Hacker Newsnew | past | comments | ask | show | jobs | submit | bryanbraun's commentslogin

The post talks a bit about this:

In a perfect world, when your legitimately good content isn’t being surfaced by Google, it’s a failure on their part, and their problem to solve, not yours. In practice, it is your problem and you have to do a bunch of work to help them see that their current assessment of your domain name is no longer accurate.

You're right, the fault lies with the search engines, but in practice it sure feels like the domain itself is tainted somehow.


We should avoid words and concepts which places the blame unfairly on mostly powerless individuals.


"Haunted" is actually a pretty good descriptor.

Something terrible happened here in the past.

The intangible spirts from this terrible event remain.

The new owner discovers his pictures scream at him and his closet constantly fills up with blood.

The fault, ultimately, belongs with the one who did the terrible deed.


blacklisted would be a good description as well.


Blacklist is too concrete.

With some domains, you merely will find a higher % of your emails land in spam, or your content ranks a bit worse, etc.

There's a somewhat random continuum. Haunting is a funny word that does sort of include some variability.


Yes, but they are on some blacklist somewhere. One could say greylisted. The point is the whatever term describes the issue shouldn't be mystical.

Haunted implies a supernatural condition that just isn't helpful in system administration.

If something isn't working with a service there is always a method to troubleshoot and isolate the issue. Contact the appropriate people when needed. This is how NeoTokyo restored his "listed" domain.


Maybe, but it's not "blacklisted" per se. You can go to the URL and do whatever.

It's not getting SEO blessings, true, but it's not disappeared.


Domains aren't individuals. Owners of domains aren't necessarily individuals either.


OP here, and yes, I've been getting that same message for musicbox.fun. I thought it just needed some time but I requested a fresh index two weeks ago, and nothing seems to have changed. :/


Yep, more details here: https://archive.org/about/dmca.php


Yeah, just look at how balanced the design looks. Either they programmed that flight path or the pilot spent a lot of time on an etch-a-sketch growing up.


This reminds me of Code-a-piller. It's a toy designed for pre-schoolers, so definitely not a full language, but it's physical and lets you sequence basic instructions in an intuitive way. More here: https://www.youtube.com/watch?v=iYEKD1Befg8


I've never made the Flash connection but I totally agree.

On my end, I try not to worry too much on the gaming vs coding thing. I'd rather have my kids playing games on Scratch then some other place where they can't view source.

I figure, if they have some basic skills and know what's possible, they'll eventually get curious and poke around. I think that's more true for some kids then others though (even in my own house).


I wonder if there's a way to smooth out the transition into modding "real" games that teenagers are already playing with their friends. I'll bet it would be pretty motivating to have that kind of power in these online spaces where a bunch of your friends hang out.

Minecraft and Roblox support mods written in Java and Lua respectively but it's a pretty big leap from Scratch to Minecraft mods.

I was recently discovered a dedicated editor for Minecraft modding (https://bridge-core.app) and that seems pretty cool. A lot more could be done in this space though.


Oh wow, great find! Gonna put this on the calendar.

That "Hacking apps with Makey Makey & Scratch" session looks particularly interesting.


Andrew Healey just took a pass at this and did a great write-up about it here:

https://healeycodes.com/doom-rendered-via-checkboxes

It looks decent but dithering would be nice so I created an issue for it here: https://github.com/bryanbraun/checkboxland/issues/20


Good callout... I updated the post to link this one.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: