It's research, not a product. Even with that, framing it as a smart home sensor in the press release is a stretch.
1) 93.75% success rate in controlled conditions, 92.1% in a somewhat-realistic deployment scenario - too low for reliability. I wouldn't use something like that to trigger smart home automations.
2) Range hardcapped at ~1m due to how ultrasound works, you can't centralize detection. Their answer is to give everyone in the household a wearable receiver, which is eeeeeeeh idk, doesn't look consumer-friendly to me.
3) Paper suggests a mix of durable and consumable parts for the transmitter. Their numbers show that the 3d-printed PLA cantilever needs to be replaced every 900 cycles or so. Should work fine, but...
4) ...every transmitter pair needs to be tuned per-setup, every time. Not a plug&play in the consumer sense.
I'm going with my fourth (or fifth) attempt to create a digital twin of my apartment in a game engine.
This time it's in Godot and i want to add more interactive stuff in the virutal version, rather than just redraw the rooms with some lights synced with Home Assistant.
So, $100B+ valuation companies get essentially free access to the frontier tools with disabled guardrails to safely red team their commercial offerings, while we get "i won't do that for you, even against your own infrastructure with full authorization" for $200/month.
Uh-huh.
Please don't spread misinformation about Flipper Zero, there is enough of that already. The device has no Wi-Fi capabilities without hardware modifications.
Arc Browser does not have a public monetization plan. The Browser Company is a for-profit company, and they'll need to give something to their investors. Their market share now is abysmal to make a meaningful amount of profit from just selling user data.
At some point, they will need to introduce some kind of subscription for some of their browser features - I assume that current Arc Max is going to be part of it. This would lead to making new features available only to the paying users.
I have really pessimistic views on software development (for-profit or not) in general now, so I'd be really happy to be wrong here.
Choosy - is a must for me. It lets you select the browser/profile after clicking on any link or define the rules for opening them. For example, if a link contains a certain domain or it's source application is Slack, it will be opened in Work profile of your browser.
Obsidian - note taking, making presentations for work-related stuff.
iTerm 2 - it's better than default terminal emulator, but i consider moving to Alacritty to see what's so hype about it.
Scroll Reverser - macOS still doesn't know the difference between mouse scrolling and trackpad scrolling.
While i can't recommend Arc browser, i still use it daily. I don't believe it will exist in it's current form in two years, but now it's much more usable than other Chromium-based browsers for me.
I also have a simple shortcut in Siri Shortcuts that calls m1ddc tool to change the external monitor current input between HDMI and DisplayPort.
I've been always fascinated by subway maps. The best ones are usually made manually and require update from contractors on every infrastructure extension. Were there any efforts to make autogenerated styled subway maps? Not like stylization of OSM data, but real schemes that show the whole system without sensory overload?
I remember finding it in early 10's and posting link on a local forum - people organized and started writing crazy and fun things here, like a minimap or a two-page-ASCII-tank.
It was one of my first realtime collaborative experiences in the internet and it was magical at the time, i still believe that services like Miro grew out of World of Text.
1) 93.75% success rate in controlled conditions, 92.1% in a somewhat-realistic deployment scenario - too low for reliability. I wouldn't use something like that to trigger smart home automations.
2) Range hardcapped at ~1m due to how ultrasound works, you can't centralize detection. Their answer is to give everyone in the household a wearable receiver, which is eeeeeeeh idk, doesn't look consumer-friendly to me.
3) Paper suggests a mix of durable and consumable parts for the transmitter. Their numbers show that the 3d-printed PLA cantilever needs to be replaced every 900 cycles or so. Should work fine, but...
4) ...every transmitter pair needs to be tuned per-setup, every time. Not a plug&play in the consumer sense.