A bit of input on the beta worry:

By no means has our experience been flawless, but as a small business we have been running entirely on Keybase for around a year and a half now.

We use Keybase every day for team & partner chat, shared storage, and git repository hosting. Our email is on ProtonMail, A/V chat via Wire, and our static websites I am not entirely sure where we host. Keybase IPs are not fixed at time of writing, so a CNAME solution would be our only option for root DNS hosting on Keybase - so we are not interested in that at the moment.

Again, we are just a small business and we do indeed run frequent backups of repositories and KBFS to offline storage (though I am not sure I would want things different with any other third party host), but given daily heavy collaborative use for our size, we do not really have complaints on beta-ness.

Primary feedback at this point are mostly feature requests - like support for git-lfs, static IPs for better DNS flexibility, minor client usability tweaks, and support for tablet displays. Thankfully the Keybase team is very active in community channels so we have a good idea on the status of these things and rapid turnaround time for bugfixes.

Active clients in the team are on android, Docker, iOS, macOS, and Win7.

A guess would be that no, they weren't going back on the store without adjusting their rating to R.

And obviously showing that they can keep child porn off their service.

A guess would be that no, they weren't going back on the store without adjusting their rating to R.

And obviously showing that they can keep child porn off their service.

Is an important part of product design not to get into the mindset of the customer? Seems that they did that just splendidly here.

This "don't be evil" thing keeps nagging though. They might want to be a bit more public about its deprecation: https://gizmodo.com/google-removes-nearly-all-mentions-of-do...

This is exactly the "no longer utopia" part of the article (or the extreme end of it anyway). With private systems, this is a real possibility.

> I don't think requiring a smartphone to accomplish what chip & pin and NFC cards do just fine is an upgrade.

Agreed. Though I also don't think that this was suggested anywhere in the article?

If you want a mapping to your situation, your wallet could have an additional card reading "Bank of Canada" next to your Visa, MasterCard, American Express, and Discover cards.

When it is relevant to my work and I can clearly identify a sensible benefit of going, then yes.

If I do not have meetings scheduled or opportunity to schedule ones which would otherwise be difficult to attain, I evaluate the networking value of the event.

Talks are generally always recorded these days. So if none of the above gives a clear indication that I should go, but interesting sessions are given, I just buy access to their recordings.

When at an event I tend to only go to sessions if I need to talk to the speakers or network with other attendees interested in the given topic.

If looking for practical optimisation, there are a ton of articles on optimisation in gamedev out there.

"Though the suit was derided by some fans, The Hollywood Reporter noted that the studios were using it to signal that they would no longer tolerate professional-quality derivatives of its movies and television series."

I would be very interested in finding out how they intend to define "professional-quality". Particularly these days.

Would you not quickly end up needing to "sabotage" your output in order to skirt the rules of such a definition, in what amounts to a strange new dogma format?

> I would be very interested in finding out how they intend to define "professional-quality"

They tried to: http://www.startrek.com/fan-films

Thanks! It seems that the key here is "creators, actors and all other participants must be amateurs".

So can you ever ship two Star Trek fan productions? Or does the first production render you sufficiently experienced to no longer qualify as an amateur? ;)