The only thing I'll say is that it's great to see the feedback in this thread applied. It became very obvious to me what the tool is for and an abstract idea of what I can do with it.

However as others have said:

- A demo video would do a lot for your product.

- nit: Real-time markdown -> change to something that emphasizes collaboration/collaborative editing. For two reason - it's a much more familiar term in the space you are building and it's easier to understand (I think) for more people.

- A sample workspace (either public or a "starter workspace" that's available by default in a new account) that is non-trivial would be great to showcase your product. Look at obsidian using obsidian itself for it's own documentation site.

- Your about page is very well written - I wonder if you can pull up somethings from there onto the main page. https://hyperclast.com/about/

I didn't sign up yet however so can't provide more feedback.

Thank you so much, I'll improve those points. I agree that a sample workspace would be great. I'm going to work on that today.

Doesn't help much because even the standard library bitrots after enough Python releases. I have things I write today but can't run on a NAS that has older Python. No issues like that with Powershell for example.

I dunno what issues you are running into, but generally, code from old Python should work fine under new releases if you are developing, you just have to set up your venv right up front and install the specific version of libraries that don't have modern Python code.

I still work on projects that were written under 3.6.

If you care enough, you can also use something like asdf to install an older Python alongside the system one.

Which of those are evolving at the rate of frameworks?

BTW I'm of the opinion that frontend tooling developers should actually try to contribute things to HTML and CSS instead of building "component libraries" on top of them.

If the native controls were good and if the browsers allowed using "uniformly styled" versions of them then there would be no good reason for such libraries to exist.

It's both reassuring and frustrating. Reassuring because they decided to secure IPC somehow. Disappointing because this is such an unexpected failure mode.

My scroll direction broke, custom operations that I had apparently "saved" to the mouse also stopped working.

Redbook is also the Audio CD standard. Lots of redbooks exist.

The area I live in has homes that remain empty because the investor doesn't need the capital nor the space and just holds empty units for multiple years when they eventually sell (for even more than they would have sold in the past).

Housing demand will always be > 0 as long as population is growing and hence there can never be a oversupply.

In areas where there is demand without risk.

It's trivial to enumerate all the phone numbers in the world.

exactly. to claim enumerating phone numbers is a whatsapp bug is stupid. and to say profile pictures were not revealed = not reading tfa.

"The accessible data items used in the study are the same that are public for anyone who knows a user's phone number and consist of: phone number, public keys, timestamps, and, if set to public, about text and profile picture." Source: TFA, which I read.

From my understanding the accessible data items meant they got them through the bug? Maybe I read wrong

Going from -50dB to -44dB is a much louder change than going from -6dB to 0dB.

Human hearing is logarithmic. The dB is measuring ratio of sound pressure level and it's accurate that +/-3dB is almost doubling/halving of the SPL.

That doesn't make sense. -50dB to -44dB and -6dB to 0dB is the same change in power, as a factor. If human hearing is logarithmic, the same factor produces the same increase in loudness.

This is exactly it. The people who get confused by decibels are treating it a unit in it's own right when it's really just a ratio of some unit.

Disagree.

The people who get confused by decibels, are exposed to other people treating it like it's a unit in its own right.

I agree that what the parent described, should be done. If it was what was done, this article wouldn't exist.

As I've said in the other comment, I believe this should be ultimately addressed by the SI.

I would agree.

Right now what we've got is basically "millis", and you just have to know whether the speaker is talking about length or mass. I like your proposal.

I actually want those suffixes mandatory, because there may be multiple plausible suffixes for each use. For example the loudness might be dB(A), dB(B), dB(C), dB(D) depending on the exact curve or even dB(SPL) if the sound pressure level is used as a proxy. So it is much more confusable than, say, "millis" when suffixes are implied.

There is a legitimate use of dB without a reference point. An attenuator attenuates by -20dB, not by -20dBm.

This is right and all... But this usage still leads to confusion about what you are measuring your filter by.

There are filters we measure on power, there are filters we measure on signal amplitude, and "signal amplitude" can be ambiguous on some contexts too. There should be a way to specify this one better.

Well, dB is fully specified in that regard. It's always power. You can calculate the voltage gain from it under certain assumptions, and under normal assumptions you get that factor 2. But a -20dB attenuator will always reduce the power by a factor of 100.

There is also antenna gain in decibels.

dBi

It's SI that caused some of this weirdness in the first place by discouraging "same unit" ratio units like m/m or kg/kg and then intentionally disallowing those derived units to be individually named. On the one hand, there is a sort of "clean sense" that km/km cancels out and disappears, but on the other hand there are too many "unitless quantities" in SI that are very formula-specific that a ratio unit would better explain and help save the wrong thing from being plugged into the formula. It's enough of a need that scientists found themselves using worse tools like deciBels for some of these "same unit" ratio formulas just to have "some unit at all" to avoid accidental unit-less mistakes.

Some Scientists and Mathematicians would rather use random log_10(x) functions than allow units like km/km in their formulas. It's wild, and SI has been a part of those decisions all along.

people are often confused by decibels because the necessary disambiguation is more often than not absent (see: spec sheets of some kind of appliance talking about noise)