https://www.reddit.com/r/ThreadsApp/comments/1wnkje9/my_inst...

Edit: Regardless, I pulled it from production immediately out of an abundance of caution.

However, the unique "roll-up" visualization of traits brought in an interesting method of self-correction. For example, if any other phyla than the obvious 4 showed up with a single egg-laying species, I went back to the drawing board to find out where that incorrect join introduced the error.

Thanks to open data, I offer the same node hierarchy of OTT, among 10 other backbones, but present it with 3 different (perhaps less dazzling) viewing mechanics switchable at the top: Icicle, which packs hierarchy into a fixed vertical height while allowing depth to stay horizontally reachable. Chronogram is the opposite, showing structure even 10 levels deep in a compact horizontal region, but at the expense of large vertical expansion. And Tree, the default, which is a compromise that can also show multiple winding paths simultaneously by folding them against the gutter.

I also focus less on the tree itself and more on trait overlay and rolling up thousands or even millions of species into compact segments so you can get a feel for how many chordates lay eggs or how many spiders are carnivorous at a glance. https://ptree.org/#OTT

The project only exists thanks to thousands of scientists carefully cataloguing all this data and releasing it CC-BY. I am only the interface.

That raccoon you see is actually suffering from Morbillivirus Canine Distemper Virus and that photo is correctly attached to that virus, and that bird is indeed eating a lungfish. I actually do penalize outlier favorite counts for photos because they're often meme-ish. I may blacklist this so the 2nd most favorited lungfish can surface. There are a lot of detailed rules that score which photo you get based on aspect ratio, whether the subject is in captivity, alive, etc.

I do filter structural junk per backbone, but only from evidence that backbone itself supplies: synonym/accepted status, "not-a-taxon", environmental, hidden, unplaced flags. I also insert neutral buckets such as "classes (no phylum)" where ranks are skipped, so thousands of taxa don't spill into one flat level.

What I deliberately don't do is move a taxon to the parent that I think makes more biological sense. Ptree (Ptable gets the same kind of requests to classify metalloids) is downstream of academic taxonomic authorities operating under something like Wikipedia's "no original research" policy. It can expose disagreement among authorities, but it shouldn't quietly become another undocumented taxonomy.

Naldaviricetes is a good example. It is unquestionably a class of viruses, but "Viruses" is not necessarily its formal kingdom. ICTV currently leaves it unassigned to a realm, kingdom, or phylum so Ptree's ICTV backbone places it directly beneath a display root called Viruses. NCBI places it beneath "Viruses incertae sedis," while GBIF supplies it without that viral higher lineage, producing the confusing placement you found.

Across those trees it overlays 41 visual properties (categorical and numerical) assembled from hundreds of biological traits and sources. Color the tree by habitat, nutrition, size, longevity, even see vertical range of birds and depth of fish visually.

The backend is 800 GB of raw data distilled through a 9-step build process that reconciles and links all 11 trees along with hundreds of traits so every node in every tree gets all the properties. Every color and number presented retains and shows its provenance: original wording, citation, and license.

The frontend uses a custom Miller column implementation with fold-away gutter, all composited animation (no frameworks, pure DOM mutation). Use +'s to try to confuse it by expanding many branches and it will fold them away and route edges around them.

Made by the creator of ptable.com, a popular interactive periodic table website around since 1997.

Comments URL: https://news.ycombinator.com/item?id=49559069

Points: 117

# Comments: 28

Comments URL: https://news.ycombinator.com/item?id=49178750

Points: 2

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=48161444

Points: 3

# Comments: 0

Then, a datacenter comes along, effectively a bigger, louder, richer neighbor playing by the same lack of rules and outdoes them at their own game. It's only oppression when a bigger dog shows up?

https://twitter.com/JamesLNuzzo/status/2037859859585179746