The integration isn't perfect (some important things like forwarding notifications to the host system are still missing) but it's already further along than you might have imagined.
6,214 karma · joined July 1, 2011
Matrix: @jon:terracrypt.net Email: jonathan@terracrypt.net
The integration isn't perfect (some important things like forwarding notifications to the host system are still missing) but it's already further along than you might have imagined.
There seems to be a Windows-only update tool available that might fix it, but that's rather inconvenient when it's used as a server running Linux! No update available as a standalone boot disk or via LVFS. So I haven't gotten it fixed yet because doing so involves getting a second SSD, taking my server offline to install Windows on it, just to run a firmware update.
If the design speed of your roads is a safe speed for those around you then yeah that works perfectly.
The value of a bike lane isn't in the lane in isolation, in the same way that the value of a street isn't in that street alone. It's in the ability of that lane/street to get you where you need or want to go.
Lavamoat would, if you get to the point of running your program with lavamoat-node or built with the lavamoat webpack plugin: https://lavamoat.github.io/guides/getting-started/
I think I need to read up more on how to deal with (avoiding) changes to your public APIs when doing dependency injection, because that seems like basically what you're doing in a capability-based module system. I feel like there has to be some way to make such a system more ergonomic and make the common case of e.g. "I just want to give this thing the ability to make any HTTP request" easy, while still allowing for flexibility if you want to lock that down more.
This also means that it's trivial to install a patched version of a package through the same package manager as everything else. No dedicated build infra required (though of course if you're deploying to a large fleet you may want to set up some build servers to avoid the need for rebuilds on most machines).
OEMs and SoC manufacturers have been getting better about upstreaming stuff recently from what I've heard (thank you Qualcomm!), but as far as stock OS images go I wouldn't expect manufacturers to support them for one moment longer than they have to.
This is part of why efforts like PostmarketOS are so helpful. Ironically, if this was an even older Pixel 3a, you could run it with modern software: https://wiki.postmarketos.org/wiki/Google_Pixel_3a_(google-s...
Although this has gotten me looking into what exactly is required to implement mobile payments, and it's given me some clarity. This doc in particular: https://www.uspaymentsforum.org/wp-content/uploads/2019/06/E...
It reads to me like the entity you need an agreement with is a "TSP" (token service provider), and they are at least the sort of organization that you can get a quote from. I don't know if you or the TSP needs an agreement with each bank, but given the relatively slow rollout of Apple Pay support between banks I assume someone somewhere in the chain does.
I can't see the actual specifications though, it costs at least $850/yr as an individual to view them. I did find an old FOSS EMV implementation, but I don't know how much of the spec this implements/what compliance work would be required to use something like it in an actual product: https://github.com/JavaCardOS/OpenEMV
So, thanks for sending me down this rabbit hole. It was somewhat informative at least. :)
That kind of thing (with careful UX design) is how you escape the sandbox cycle though; if you can grant access to resources implicitly as a result of a user action, you can avoid granting applications excessive permissions from the start.
(Now, you might also want your "app store" interface to prevent/discourage installation of apps with broad permissions by default as well. There's currently little incentive for a developer not to give themselves the keys to the kingdom.)
And given a sufficiently flexible phone, it'd be nice to have a mode selector pop up when you plug into a new display. Pick between screen mirroring, desktop mode, and a media center, and optionally remember the choice for next time.
I think offices are the most likely places to have something like this, though. My company has monitors with USB-C dock inputs set up at each desk; you grab a desk and plug your laptop into it when you get there. But they're just using DisplayPort Alt-Mode, and a phone with a desktop mode would work with them as well.
I wish I could do that for work; would save me from lugging around a rather heavy laptop. :)
Phone wiretapping (until recently I suppose) and mail inspection required a human to take some action to listen in; you couldn't just monitor everyone's communications. Now you can.
I do wish they would sell them in the US and had more US band support. I got mine on a trip to Europe and it works here, but not always consistently. :) That's probably the one thing that'd get me to upgrade and repurpose this one with PostmarketOS.
I got the Viture Pro recently and this would be fun to add to that. Ultimately I think this is a very nice form factor both for portable use with XR glasses, and for use with a USB-C dock at home. The XR glasses on the market are still a bit rough, but the nice thing about this kind of setup is that you can replace the computer and the glasses independently, so as the glasses improve (especially looking forward to glasses with high-quality waveguides) you can upgrade.
Pretty sure it is based on a derivative of the original WebOS code! I think the LuneOS folks use some WebOS OSE code: https://en.m.wikipedia.org/wiki/LuneOS
Sure, we obviously weren't going to get to this point with only symbolic processing, but it doesn't have to be either/or. I think combining neural nets with symbolic approaches could lead to some interesting results (and indeed I see some people are trying this, e.g. https://arxiv.org/abs/2409.11589)
I'd be happy to use s-expressions instead :) Though to GP's point, I suppose we might then end up with JS s-expression parsers that still treat ints and floats interchangeably.
I've got a copy of Capability-Based Computer Systems on my shelf that I've been meaning to read for a while, and it covers the Plessey System 250: https://homes.cs.washington.edu/~levy/capabook/
Very much not a new concept! Though note that this book was published in 1984 and there have been several newer developments in the capability literature since then. (Revocation for example, which is mentioned as an issue in chapter 10 but has since been addressed with some capability design patterns.)