Appreciate this, also put in another link in the footer to "Report an Error" just in-case it does become a reference source. No factor of safety in the periodic table of elements.
As second suggestion: this probably looks great on a cell phone, but on a 50" display you've got tons more space for additional elemental facts/tidbits. Perhaps detect monitor size, then keep simple for phones?
This could additional put the lanthomides into their correct placement (if window widened enough) [0].
Much prettier. Could easily have larger pop-ups (entire point is to get information on elements, no?) <https://i.imgur.com/IVx5MY5.png>
Heck, even have a link to Wikipedia articles (why not?). You're obviously in the enjoyment of information sharing =D
You also have plenty of space for an example element (e.g. describe what each line represents e.g.g: density, atomic mass, proton/element #). The map's "key" if you will... not everybody knows these standardized chemnerd properties (you can then also remove the 120+ "RT" by simply placing in example element @STP, with a link to what that means, too).
I like that you've chosen to use an actual element for the example / explainer.
To streamline the UI, might I suggest replacing example element (copper) with just the explainers, next to hydrogen [2]... using that elements information (without adding a free-floating copper).
If that doesn't make sense, let me know.
Thanks for being a responsive educator.
[2] perhaps use Beryllium for your example/explainer -- because then you can explain the electron orbitals too ..?
----
Replace the topbar (color==atomic class) location to between Group II & III elements (e.g. whitespace between Be B); does not need to be explained on example element text.
I tried playing with making the elements a bit more full but then it feels too cluttered. So I think the tool tip is good for now till maybe I figure out a way to add other stuff into it but not feel to cluttered.
I updated the Title to show the .org, but also in the mean time picked up https://periodictableofelements.com so working on that as well to make one the educational and the other to support any costs it might ever have and for any traffic leak I guess.
You've added something that dims elements in years before they were officially discovered; but this is not “what the periodic table looked like at the time”. When I was a child, the periodic table had element names hahnium and kurchatovium on it. This is probably not easy to implement because many elements had multiple names between the US and USSR and they were not internationally standardized until 1997 (long after the fall of the USSR).
Made the moible X 36px now, so easier to close. And removed uses and fun fact clues that gave away answers, replaced with density, melting point, electronegativity, and group number
Fixed the Safari bug, replaced CSS transform-origin (broken in Safari on SVG) with native SVG animateTransform which works everywhere.
Also, you can now drag the "Year" slider on the main table to see how the periodic table looked at any point in history. Undiscovered elements fade to near-invisible. Ancient elements (no known discovery date) stay visible.
You make a fair point about terminology. To be precise: our encryption is client-side AES-256-GCM encryption of the stored transcript meaning once transcription completes, the text is encrypted in your browser before being saved, and we can't read the stored transcript without your password. The audio is processed on our GPU during transcription and then deleted."Zero-knowledge" was used loosely a more accurate term would be "client-side encrypted storage". The server does see the audio during processing (that's how GPU transcription works), but the final stored transcript is encrypted with a key derived from your password that never leaves your browser. Update our terminology to be more precise and also the HN thread title. Thanks for the feedback and I hope something in you lives a little again.
> The server does see the audio during processing (that's how GPU transcription works), but the final stored transcript is encrypted with a key derived from your password that never leaves your browser.
You conveniently omit mentioning that the server also sees the transcript before returning it to the client side browser. Whether it is "immediately" erased, is something the client must trust the server to do. You might as well save yourself the roundtrip by encrypting server side, returning the key, then deleting it, same outcome.
Thanks for pushing us on this, you're right. We've updated all our terminology and documentation to be fully transparent:
- Security page now explicitly states the server sees audio + transcript during processing
- Privacy policy and terms updated with a bit clearer language about what's protected vs what's not
For users who need true end-to-end privacy where audio never touches shared servers, we're launching Private Cloud and Self-Hosted options: https://stt.ai/private-cloud/ Your feedback directly shaped these changes. Appreciate it.
reply