herczegzsolt

My primary issue with a new password manager is always trust.

Are there any plans to review the source code independently, or do something similar to prove it's end-to-end security?

Why not XLR?

Bluetooth operates in an unlicensed band. If any medical device relies on any unlicensed band for any life-critical thing that is horrible design.

I would absolutely support consequences to any device manufacturer if a death is caused by a jamming of unlicensed frequencies. (In my opinion, medical devices should be able to keep you alive in any jamming scenario if feasible. But using licensed bands is just bare minimum.)

How is this better or different than Solaar?

Absolutely. Starlink outperforms ADSL anytime, and is better than most 4G fixed-wireless-access options. I use it for remote work regularly.

If there's fiber (like GPON) or reliable 5G available, then of course they win. Otherwise, Starlink is better.

Desperately needs a skip button for words I don't know.

I've not done proper scientific comparisons, but had to reimplement some games as websites to make them reliably perform on Raspberry Pi's we used embedded.

This is a bit of an apples to oranges scenario, because the algorithm and architecture is not exactly the same, despite the game functioning identical.

The main weak points of LÖVE that we hit were mainly around embedded video playback though, which is probably very well optimized in chromium.

I've used this for many projects that are still working to this day.

That said, i'm not impressed. A web-based solution is usually better performing, despite all the bloatware necessary. This says a lot about the state of software development unfortunately.

Is this question in any way related to television?

I just had to solve this problem recently. I've settled on Google Pixel Watch 4. There are some rabbit holes to go down though before it works reliably.

I am bit disappointed they did not immediately jump on implementing the two straightforward recommendations:

> PROPOSED MITIGATION. A straightforward mitigation is to have the client sign vault keys using the RSA private key in the keyset before encrypting them with the RSA public key.

> PROPOSED MITIGATION. [...] it would be easy for 1Password to prevent it entirely: the secret key can be used (with proper key derivation) to authenticate the KDF parameters with a cryptographic MAC.

To be fair, these issues are not really impacting long-time users. I have hundreds if not thousands of items in my vaults, there's no way i'm not noticing if they dissappear (which would be a side effect of these attacks).

Overall, I think 1password can be proud of their architecture and product quality, but i'd love to see these improvements - and maybe something like a "signal verification code" for sharing?

I vaguely remember hitting this message id issue in Google Workspace, and being able to work around it in mail routing configuration.

Saidly I don't remember the specifics, it was something along the lines of not all, but only specific routing features requiring it. Workspace settings are a moving target anyway, so the behavior probably changed more than once since.

I'm not saying it's a good idea to send emails without message id, but i'd also double-check that workspace configuration.

It probably wouldn't trigger, because of the 2nd criteria:

> The alert is not triggered immediately: it takes 8 hours during the day, 30 mins at night, and ...

But the warning system is by no means perfect. My family is split 50-50 between iOS and Androd ecosystems, and that's already enough to throw things off and get false positives semi-regularly.

Also, don't even ask the curriers how many alerts they get. Including airtags in valuable shipments is the de-facto standard nowdays.

I'd also love to see some Slack interoperability. We use and pay for Slack, only because our customers use Slack.

It is a competetive advantage to reach our customers via their chat platform. Slack being the walled garden that is, it's basically a Slack-tax we pay.

How is this better than Rocket Chat and what is the guarantee behind the free forever plan?

Slack used to have a generous free tier, until they stopped having it.

This was pretty much the successor of Cody, the initial AI offering of Sourcegraph.

The notable thing about this EoL is that it marks an end to the product line that Sourcegraph entered the AI coding assistant field with.