tantanel

No, I think the example is correct. __bar in this case is interpreted as an element name (custom html element), not a class.

You will need to restart your PC for the changes to take effect and show in the app.

Couldn’t the same analogy be used if I left my front door unlocked? The door would happily say: “yes, you may enter” to anyone trying the handle.

I think the real question here is: did the website provide enough information for the user to have been assumed to understand that what they were accessing wasn’t meant to be public (e.g. did the door look like a door to a private property)? And did the user cease to access the data once they understood it (e.g. did they close the door and leave)?

In Estonia they allow you to vote multiple times and only the latest vote counts. They even allow you to then go and vote in the booth which renders your e-vote invalid. I don’t know the internals of how they store the votes but I can’t think of a way to do this without the side effect of knowing who voted for whom.

This is true for the username but it's possible to make your email address private on GitHub in which case the message that your email is taken can still be considered an information leak.

The message is still not wrong if you think of "or" as the boolean or, not as the boolean xor. The system knows the username is wrong but it doesn't know anything about the password.

Op here. This is a side project I've been working on for the last couple of months. I still have a huge roadmap of planned features ahead of me, but I feel the app is now polished enough to be presentable. I'm releasing the beta version, hoping some of you will find it useful. Please let me know what you think. Thanks!

This, I think, is the most important feature off the app, and should be the first paragraph of the value proposition.

Waking up to a random new song every morning is not very appealing (many alarm clock apps can do that) but knowing that the song is manually selected, picked to be suitable for waking up, and knowing that every other user of the app will wake up to the same song on that day, makes it infinitely more interesting.

It was a wonderful read, I thoroughly enjoyed it. Thanks for sharing!

This bold.co site is a bit confusing though - I can't find a place where I can subscribe to the author's posts. Does it even have such a feature?

The debate is not really whether the algorithm should be made public or not, it's about the method used to try and keep it secure.

If the algorithm can be reverse engineered then trying to suppress the knowledge that is already "out there" will only create an illusion of it being a secret, and the fewer people know about it the more damage they can potentially do (i.e they more they can financially benefit from their knowledge).

It's the same as with information security - if you discover an exploitable bug then chances are someone else has already discovered it too (or can discover it any time) so making it public is one of the most sensible things you can do.

The UI looks decent and easy to use. Two suggestions though: 1) The auto-complete search widget could do with keyboard navigation. 2) I think the Icon Generator logo shouldn't link away from the app. There's no "Reset to defaults" button so I assumed clicking the logo would achieve the same thing.

I think I would have noticed far less of the placements if it hadn't been for the "warning" before the episodes. :)