Bug in the latest firmware. Should be patched during the next recharge or OTA for the newer models.
2,583 karma · joined March 3, 2013
There’s an intro to IPFS content identifiers here: https://docs.ipfs.tech/concepts/content-addressing/.
I wouldn’t carry a voice only phone, or a text only messaging device, or a standalone GPS, music player, or PDA. But I do find a phone that combines these pretty useful.
Would be very nice to see if this works on the new iPhones. A thin client with decent security in your pocket with keyboard/mouse/display at both home and work seems like a very approachable computing setup.
Photo for reference: https://twitter.com/_______kim/status/1348736952330301440
I was an early(ish) adopter of smart watches/wearables - think Pebble and LG G Watch era. I walked away from that experience with the perception they exist solely as expensive distraction machines with an extremely short functional life and have been enjoying mechanical watches since.
This tech has me on the verge of trying again. It's seems to be getting pretty close a ubicomp device. There's enough compute onboard to do useful things with the sensors, particularly with the addition of the neural cores. The UWB proximity awareness look interesting too for someone with other apple devices (HomePods etc).
What I'm not familiar with is the current software ecosystem. Are there any core functions or third party apps that make use of this outside of just slinging notifications?
If you continue to think about the problem space during that ‘off time’ (which you likely will) add the thought to some notes for review when you return.
This can be implemented in a way that remains transparent (albeit via JS), poses little impact on ‘good’ users, but protects against a lot of traffic patterns that may be undesirable. The cost can be scaled to match infra capability and the challenge can be a combo of the request data and time. Valid windows for that time can then be synced with cache validity which removes the need to keep tabs on any state.
For those deeper in this space. What am I missing here that prevents this from being the norm?
Not associated, but have been using them for some personal infrastructure lately - it's a really nice platform. If you have strong isolation requirements they have bare metal options too.
Expressing the core statement up front allows proceeding content to serve as an optional framing, if required. If the recipient already has context they can skip the cruft.
This structure is mirrored in larger org settings that use memo's. It's not a new idea, but definitely a well proven and effective one.
I used to ride a Zero SR. It was a phenomenal bike but also completely unserviceable in Australia. I ended up reverse engineering the log protocol [1] to get a sense of how it was performing and maintain what I could myself. It was horribly painful, inefficient and completely avoidable spend of time.
Hackability for devices is one thing but when you straddle an energy source that propels you, a fragile meat sack, at speed imo it's essential to have absolute confidence in how the machine behaves.
[1]: https://github.com/zero-motorcycle-community/zero-log-parser
I know it’s a fairly popular resource here - has anyone extended the content to go all the way with an FPGA implementation?
The obvious solution is to start yeeting compute and/or users into space.
Speed of light in a vacuum is higher than what can be achieved in a fiber-optic. Combine that with a more direct path than what can be achieved with an undersea cable and things start to get interesting.
A “defect” is a declaration that something is evidently faulty with a clear onus on the vendor to fix.
Amazing solid bits of hardware with ingress protection, strain relief, and good usability for environments with a lot of equipment movement.
Looks like the single quote doesn't play nicely with the auto-linker.