I love how half the links in the comments dont work on Safari
Show HN: I built a website for sharing drum patterns
101–110 of 197 posts
Re: Show HN: I built a website for sharing drum patterns
#102Earlier quoted context omitted.
I worked for an authority that issued digital certificates for SSL and digital signatures. It's not only about providing encryption but also about trust, when a top level entity issues a SSL certificate, a number of identity validations are carried out, adding an extra layer or confidence on that website. This may seem inconsequential for static websites without PII, however most browsers consider it important as it…
you didn't answer the _why do we need all that for a drum beat making website_?
At least so that login / register data don't go to the middle man.
Re: Show HN: I built a website for sharing drum patterns
#103Please allow triplets! You're missing out big without a basic shuffle! I also second the other comments about ordering. Cymbals on top, snare and toms in middle, bass and other pedals on the bottom. e.g. hh |x-x-x-x-x-x-x-x-| S |----o-------o---| B |o-------o-o-----|
I guess you could make a 3x16 pattern but interpret it as a 4x12, so each beat is three steps...
Re: Show HN: I built a website for sharing drum patterns
#104Earlier quoted context omitted.
I would rather everyone use HTTPS than have them individually decide if it "needs to be secure".
Why is that?
The downsides of being secure are a 5 minute setup, once. The thought process of "should this be secure?" is 10 minutes even if the answer is obvious.
So why bother? Just be secure and move on.
Re: Show HN: I built a website for sharing drum patterns
#105Earlier quoted context omitted.
I worked for an authority that issued digital certificates for SSL and digital signatures. It's not only about providing encryption but also about trust, when a top level entity issues a SSL certificate, a number of identity validations are carried out, adding an extra layer or confidence on that website. This may seem inconsequential for static websites without PII, however most browsers consider it important as it…
you didn't answer the _why do we need all that for a drum beat making website_?
You don't. But you will be penalized by Big Co for not supporting https.
(It's effectively a "doing business on the Internet" tax. Thankfully not that expensive for small hobby projects now.)
Re: Show HN: I built a website for sharing drum patterns
#106Earlier quoted context omitted.
you didn't answer the _why do we need all that for a drum beat making website_?
Unauthenticated http is a vector for opportunistic malware. They don’t target specific websites, just inject evil.js wherever.
You ISP sniffing and MiTMing traffic on the wire is the least likely vector of malware injection.
ISP's are usually serious businesses with reputations and don't hack their own customers.
Re: Show HN: I built a website for sharing drum patterns
#107Earlier quoted context omitted.
Why is that?
The downsides of being secure are a 5 minute setup, once. The thought process of "should this be secure?" is 10 minutes even if the answer is obvious. So why bother? Just be secure and move on.
Https does nothing for security.
Its purpose is to authenticate financial transaction packets, not to be "secure". (Whatever that means.)
Re: Show HN: I built a website for sharing drum patterns
#108Doesn't work on FF on iPhone. Very nice otherwise!
Re: Show HN: I built a website for sharing drum patterns
#109Very cool! Reminds me a bit of this visualizer I built a few years ago. https://michaelmior.github.io/rhythm-wheel/
This is actually really cool way to show it.
Love it.
Re: Show HN: I built a website for sharing drum patterns
#110Really nice work!