brianlovin

Should be fixed now, I hit rate limiting issues upstream.

Should be fixed!

Should be fixed. Minor hug-of-death with CMS rate limits

I started a company, that has taken all of my focus. Fair point.

Posted below, but:

Creator here - thanks for bringing this up. I was concerned about the message here as well. I'm not getting paid for that ad. I had a couple companies offer sponsorship of this list, but I decided to not pursue. In the end, 1Password simply offered this discount to visitors. For me this felt like the best thing I could do from a user experience point of view (switching to a password manager is hard for most people, and giving the extra nudge to do something really important for their online security might just do the trick) and from an ethical point of view (I'm not getting paid, and will continue adding competing password managers to the list).

Creator here: PR has been opened :) https://github.com/brianlovin/security-checklist/pull/46

Open a PR! This list is far from complete.

I thought about buying privacycheckli.st at the same time and pointing it here, but ended up deciding that "security" feels like a broader umbrella and might reasonable capture privacy concerns of an average person.

Creator here - thanks for bringing this up. I was concerned about the message here as well. I'm not getting paid for that ad. I had a couple companies offer sponsorship of this list, but I decided to not pursue. In the end, 1Password simply offered this discount to visitors. For me this felt like the best thing I could do from a user experience point of view (switching to a password manager is hard for most people, and giving the extra nudge to do something really important for their online security might just do the trick) and from an ethical point of view (I'm not getting paid, and will continue adding competing password managers to the list).

Creator here: glad someone opened an issue to add Linux, sorry this was missing in v1! Will get it landed shortly :)

Edit: https://github.com/brianlovin/security-checklist/pull/46

We do have the concept of channels within communities. Channels can also be optionally private.

Hey there - if you selected 'private' during the community creation flow, everything in that community will be private. However, there will still exist the concept of "public" and "private" channels, however those scopes are still constrained by the community settings. For example, a private community with a public general channel means everyone who has access to the community can see those conversations. But if you have a private channel in a private community, only a subset of authorized community members will be able to see those threads.

Hey, co-founder here. We've really been focused on threaded, public-by-default, search-indexed conversations. We've found this to be super helpful for large, async communities so far, and the search-indexing is really great for organic discovery and preventing too many duplicate questions that someone might ask in a synchronous chat app. But we also support private communities, private channels, direct messages, public community/user profiles, and more. We've seen these things be really useful for content and community discovery.

Thanks for the kind words! For reference, we open sourced everything back in April: https://spectrum.chat/spectrum/general/announcement-spectrum...

Author here, thanks for submitting! This post was a lot of fun to write, having been an iOS users for 7 years now. Hope everyone out there is enjoying it as well :)

Thanks for the feedback! I've heard the contrast come up a couple times, and definitely seems like something I could improve :)

Thanks for the feedback! This is something I've been constantly working on, and this comment is totally fair :) Also, the contrast mention below has come up a time or two before so it sounds like something I should fix up.

Aesthetics aside, I hope that the podcast sounds interesting! We're very excited to get things started.

$2.5b revenue in Q12014. ~$321 revenue per second. A costly outage, no?

Yep, thanks for including Buffer here (I designed this pricing page) - there's lots of improvements to be made here which will be coming soon :)

Feels like there's a fine line between having a negative attitude about a new product and exposing real weaknesses - whether those are weaknesses in the product itself, or the market within which it falls. Probably nothing wrong with exposing weaknesses, as long as its done in the context of "here's what's wrong, and my idea of how it could be fixed or improved."

I agree with your assessment though, the Nest post this morning really was quite 'over the top' so to say, as far as negativity goes.