I'm working on a coding agent with built in sandboxing to restrict network access or filesystem access of commands run. It also has a few other interesting features I haven't seen in other agents and I'm currently focusing on polishing the UX across its cli, tui, and web ui. It's not quite ready for use yet and I've only recently begun dogfooding it. https://github.com/agent6-dev/agent6/
I also recently resumed working on picosnitch, a per executable network monitor for Linux. I rewrote the UI, ported the core from BCC to BPF CO-RE, and used AI to benchmark the completeness and accuracy of it. I let AI decide the tests entirely on it's own to hopefully eliminate any of my bias and published the results here [1]. It identified one gap I'll be fixing in the next release, and is currently the most complete and accurate bandwidth monitor on Linux.
I'll definitely check both of these out! I've been working on a design doc with my assumptions, threat model, and required security controls for an agent sandbox so that I can use it as a baseline when comparing different offerings.
Same here, I suspect the majority of people with average to small hands could never really one hand phones (with a good enough screen size) in the first place so it makes less difference to them.
I really enjoy that roller coaster feeling both in real life, and in VR games like Jet Island and Windlands.
I'm pretty interested in this and would like to participate in a study as well if given the opportunity. I think one of the potential causes and solutions is it being a self-fulfilling prophecy that may be overcome with self-efficacy as described here [1] for seasickness. My only evidence is that I never knew motion sickness was a possibility when I first tried VR, and my friends with the worst motion sickness were worried about it before they even tried VR, even if they never got seasick or carsick.
From the article and other comments, they also mention figure skating which I never thought of before, and I play ice hockey which is likely similar enough. For reference I've been playing VR since 2016 and never once experienced motion sickness, from any style of game/locomotion.
Well I never got seasick on boats (large or small) and even took up windsurfing for a time. When I tried VR initially, naseau wasn't a widely known symptom (late 90s), but I got naseau anyway. So I don't think it's always psychosomatic.
I like LocalSend and Landrop. The latter performed better when I sent large files. However, neither of them does it automatically; you have to manually do it every time, which is okay since they don’t claim to be sync software.
I use python more often than tools like awk, which I often forget the syntax of, so I made pyxargs to quickly run python code in the shell for small tasks like this
sp current | pyxr -0 -g "(Artist)\s+(.+)\n(Title)\s+(.+)" -p "{3} by {1}"
There's pyan3 [1] which although doesn't support python 3.7+, I've still had luck with v1.0.4 which works better for me than its most recent version with python 3.11, but there can be some weird issues though depending on your code style.
A quick search also turned up crabviz [2] which has support for more languages than just python.
Great article, I've always been impressed by this too. It's neat that it sounds like even amateurs with nothing but a regular DSLR can contribute to this as well.
> By precisely timing the duration of the occultation from many sites simultaneously, they can refine their knowledge of the size and shape of the asteroid.
> Betelgeuse is the 10th brightest star in our skies (+0.5 magnitude), so observers need only modest equipment to participate.
> the easiest way to capture the event is to use a simple DSLR camera on a tripod ... video frames must have a short (few-millisecond) exposure time ... Millisecond accuracy timing is crucial ... [an app] for timestamping occultation observations is called Occult Flash Tag (Android) or AstroFlashTimer (iPhone)
Sadly this seems abandoned and it seems to have been removed from the Play Store. It's also not on F-Droid, even though it does seems to have a Git repo on Github.
I can imagine it helps to normalize the various perturbations from atmospheric non uniformity which may be able to help the higher quality measurements decrease the noise.
Yep, and from my experience too (made a tool that monitors network traffic with eBPF [1]) in addition to those issues there is also a sizable latency hit.
I think this is still reasonable, attackers may have a database of leaked keys (e.g. if you ever accidentally commited to GitHub, or ever ran a malicious script which uploaded it), which they then try on random servers.
I also recently resumed working on picosnitch, a per executable network monitor for Linux. I rewrote the UI, ported the core from BCC to BPF CO-RE, and used AI to benchmark the completeness and accuracy of it. I let AI decide the tests entirely on it's own to hopefully eliminate any of my bias and published the results here [1]. It identified one gap I'll be fixing in the next release, and is currently the most complete and accurate bandwidth monitor on Linux.
[1] https://elesiuta.github.io/picosnitch/comparison/
reply