songgao

Did I miss it or they didn’t mention when you could order it?

I’m having a hard time coming up with a reason why there needs to be any replay protection here. That port is supposed to open without unlocking the car. You can approach a locked Tesla and press the button on a charging connector and it’ll open. The whole thing is unauthenticated by design.

Yes, this has always been the case. The root CA is embedded in the Keybase client: https://github.com/keybase/client/blob/master/go/libkb/ca.go

This provides a way to add some protection against a polluted trusted CA store.

This might be an unpopular opinion but this is a pretty awful headline and it makes it look way worse than what the EMS documents actually say. There’s a bold text [1] “shall not be transported if return of spontaneous circulation is not achieved in the field”. There’s a pretty big difference between abandoning patients with little chance of survival in general, and giving up after failure to achieve ROSC.

Perhaps at some point we’ll be at the place where EMS really have to give up without even attempting CPR, but we’re not there yet.

That’s not saying the situation is not bad — it’s terrifyingly bad. But a headline designed to make incorrect impression just doesn’t help.

[1] https://twitter.com/Pervaizistan/status/1346295476405084168

EDIT: link, to focus on the right tweet. typo.

Yeah starting from Catalina the / is now read-only. Upgrading from an old macOS also kills any previously created files or directories at root that were not shipped with the system. So `/keybase` is gone on Catalina.

You mean this? https://news.ycombinator.com/item?id=19639297

As other comments have pointed out, devices (mobile and desktop app) do require 2FA and there's no way around that. So I'm assuming you meant the keybase.io website where you can log in with username and password.

Note that the functionality of the website is very limited. You can't access any chat messages or non-public KBFS data, for example. The most power thing you can do is resetting your account, and after that is probably using your PGP key if you uploaded an encrypted version of your private key to Keybase. If this worries you, you should turn on lockdown mode [0] to require a device to access those features.

[0] https://keybase.io/docs/lockdown/index

Keybase [Cryptography for everyone!] https://keybase.io/

Positions:

* Front-end Engineer (React.js / React Native) https://keybase.io/jobs#frontend-dev

* Identity Evangelist: https://keybase.io/jobs#evangelist

Locations: New York | San Francisco | Chicago

Other stuff, other than snacks:

* Off-site in different cities twice a year for the whole team to get together.

* 20 vacation days annually, plus 2 floats to choose from non-federal holidays.

* Work-anywhere in July and August.

* Paid travel to SF and NYC offices every once a while.

To apply, please send following to jobs+e4ac1f774a@keybase.io:

* a brief note introducing yourself

* your resume or a link to it (LinkedIn is fine)

* [more as described on the jobs pages above]

Not sure. I’m like everybody else looking for good alternatives here :)

I migrated to Fastmail from Google Apps a couple years ago. When Inbox came around, I moved everything back to google. While Fastmail is a wonderful service, I don’t think it has the features that Inbox provides. so I’m not sure it’d be a good alternative to Inbox.

This old blog post has a pretty good explanation about how Go slice works: https://blog.golang.org/go-slices-usage-and-internals

Once you realize slices are just (pointer, length, capacity) structures, and the structure itself is copied by value, the first 2 WAT is pretty trivial.

Keybase [Cryptography for everyone!] https://keybase.io/

Position: Software Engineer (React.js and React Native)

Locations: New York | San Francisco | Chicago

Tech:

* React/Electron (macOS, Linux, Windows) and React Native (iOS and Android)

* Redux, Saga

* Decent code-sharing between different platforms

* Core client functionalities (chat, filesystem, proof tracking, etc.) are handled by the same Go code on all platforms, interfaced with front-end through RPCs.

* Codebase if you're interested: https://github.com/keybase/client/tree/master/shared

Other stuff, other than snacks:

* Off-site in different cities twice a year for the whole team to get together.

* 20 vacation days annually, plus 2 floats to choose from non-federal holidays.

* Work-anywhere in July and August.

* Paid travel to SF and NYC offices every once a while.

More details: https://keybase.io/jobs#frontend-dev

To apply, please send following to jobs+a538cfb5ed@keybase.io:

* a brief note introducing yourself

* your resume or a link to it (LinkedIn is fine)

* a link to web work you've done, so we can poke at your code

I think it used to be cost/performance and was later fixed. GP left comment before the fix.

Keybase [Cryptography for everyone!] https://keybase.io/

Position: Software Engineer (React.js and React Native)

Locations: New York | San Francisco | Chicago

Tech:

* React/Electron (macOS, Linux, Windows) and React Native (iOS and Android)

* Redux, Saga

* Decent code-sharing between different platforms

* Core client functionalities (chat, filesystem, proof tracking, etc.) are handled by the same Go code on all platforms, interfaced with front-end through RPCs.

* Codebase if you're interested: https://github.com/keybase/client/tree/master/shared

Other stuff, other than snacks:

* Off-site in different cities twice a year for the whole team to get together.

* 20 vacation days annually, plus 2 floats to choose from non-federal holidays.

* Work-anywhere in July and August.

* Paid travel to SF and NYC offices every once a while.

More details: https://keybase.io/jobs#frontend-dev

To apply, please send following to jobs+89ecd0b3@keybase.io:

* a brief note introducing yourself

* your resume or a link to it (LinkedIn is fine)

* a link to web work you've done, so we can poke at your code

I can’t help but think this best aligns with US immigration system. US take in huge amount of international students, but don’t have a reliable (no, lottery-based work visa with a ~50% SLA is not reliable) and easy way for top graduates to work. Instead, policies that were made tens of years ago in fear of US jobs stolen by foreigners are still effective and the same mindset influence many Americans.

This is just an effort among many to attract talent in the US, and at this point any country who doesn’t make this kind of effort is basically leaving free money on the table.

Have you tried this one?

Hacker News (YC) by Dharmesh Patel https://itunes.apple.com/us/app/hacker-news-yc/id713733435?m...

It’s worked fairly well for me as a light user.

There’s an official guide now: https://support.apple.com/en-us/HT208332

It's in a separate repo: https://github.com/keybase/kbfs

> though I guess that allows read-only sharing and a stronger concept of ownership... you can't do that for shared private files in KBFS right?

Actually you can!

Check out `/keybase/private/songgao#ereyes01@hackernews/hi` and try writing to that folder :)

EDIT: typo and missing quote

Oh nice. Thanks!

I was too eager to try it out that I did not read it carefully enough. Completely my fault! Yeah repository selection would be nice!

Before you try it out, just know that it will install a webhook on every single one of repositories that you have permissions on, not just the ones under your personal account, but all the organization ones as well. And GitHub doesn’t seem to have a way to easily remove them all at once, even after the app's permission has been revoked.

EDIT: as pointed out by Prefinem below, using the "Logout" feature uninstalls all webhooks: https://www.realartists.com/docs/2.0/uninstall.html

Thanks for making `kbsecret` and having it based on KBFS!

> Records are shared under the /keybase/private/user1,user2,user3/kbsecret hierarchy, so adding or removing a user would just be a matter of changing the user list (moving the directory) and updating the session to match.

I wanted to mention that we are actually actively working on a feature called, not surprisingly, teams. It'll be useful for both chat and KBFS. A team has builtin mechanism for adding/removing members, and has its own sigchain.

This should provide applications like `kbsecret` with smoother support for team. So for KBFS for example, instead of `/keybase/private/alice,bob`, you'll have `/keybase/team/foo` which has Alice and Bob as members. When Celia joins the team `foo`, you can keep the same path `/keybase/team/foo` rather than having to move stuff (which is actually a copy-then-delete since it'd require re-encryption) to a new folder `/keybase/private/alice,bob,celia`. We'll also have a slightly different rekey process that makes this super fast.

Shameless plug: I made a wireless network emulator [0] for my dissertation. It's a userspace implementation with a lot of extra user/kernel context switches for every packet, so too slow for emulating latencies and only deals with packet loss. But it takes wireless congestions into consideration, and can emulate CSMA/CA. For one node this wouldn't make a difference, but for multiple nodes where interference is a problem, it's a bit more realistic than just setting arbitrary packet loss.

[0] https://github.com/squirrel-land/squirrel

EDIT: typos

Imagine you chop off your head, give both your head and body necessary environment to regenerate. It'd be like cloning.

Although the head gets a brand new body that works just as good if not better, while the body gets a head that is completely blank. Sounds pretty unfair to the latter...

ICQ was a legend! I can't believe nobody has mentioned OICQ yet. It was a Chinese clone made in 1999, and what later on was renamed to Tecent QQ.

Are you sure about them being Bluetooth? I'd be interested to know how they make it work.

If you meant something like this [0], DECT [1] works on a different frequence band.

[0] https://en-us.sennheiser.com/phone-headset-wireless-call-cen...

[1] https://en.wikipedia.org/wiki/Digital_Enhanced_Cordless_Tele...

2.4Ghz is super congested. 802.11g is. Bluetooth is. Even your microwave is on 2.4GHz. If everybody starts to use Bluetooth headphones all the time, I fear it's gonna make it totally unusable.

Here are a couple more:

https://keybase.io/inv/d1439a90ad

https://keybase.io/inv/19ff7aba7d

https://keybase.io/inv/214f008a4f

https://keybase.io/inv/19949fe9a1

https://keybase.io/inv/8c0d7ab033

https://keybase.io/inv/6e0e648a78

https://keybase.io/inv/02bfae461c

https://keybase.io/inv/b643f5505

https://keybase.io/inv/98155df989

https://keybase.io/inv/79f12dd484

> Basically what happens is the client is expected to send an IPv6 packet to the phone carrier which then will translate it to IPv4 if needed.

This will only happen 1) in the test environment that helps ensure that your App will work fine in a IPv6-Only (as opposed to dual-stack) network; 2) your carrier has IPv6 and NAT64.

If I understand correctly, the higher level APIs should be able to choose IPv6 or IPv4 accordingly based on network configuration. If, for example, your carrier doesn't support IPv6, apps using these APIs will continue function well using IPv4. And I doubt Apple will ban IPv4 entirely before all carriers support IPv6 and NAT64/DNS64. So "for now" will likely be several years.

There are many components that need upgrades in order to move to an IPv6 only Internet. Preparing applications for it is an important part, and this is a nice step in this part.