I don't think that was a malfunction...
That was 'working as intended'.
It'd be easier to train clamp scientists to static fire than to train rocket scientists to clamp.
I thought one thruster has been permanently disabled now? Not that that's a major problem, but it does eat into their redundancy somewhat.
How will they filter it out? If they just don't mirror anything with 'forbidden' terms, we can poison repos to prevent them being mirrored. If they try to tamper with the repo histories then they'll end up breaking a load of stuff that relies on consistent git hashes.
Starship is about 80% the width of Falcon Heavy - but all the way around and practically all the way up!
My my, here come the fuzz.
One would hope there's never a need to restrict any content here for legal reasons, though.
Thanks for your continued service.
Any idea what's up with the response times? I was thinking there may be some ongoing conversion operation but it still seems somewhat slower than before. Unless the reporting has changed.
I can see that, but surely there wouldn't be much difference matching the first 4bits (0x2XXX, 0xfXXX) vs the first 16 (0x0001)?
0:: is presumably all for loopback-type stuff, but I don't see a reason not to use 1:: through 1fff:: and they would be much easier to type/remember/validate for public DNS servers which are needed before name resolution is available.
Why start at 0x2001 though? Why not 0x0001? Then we could have addresses like 1:1:1::1 or 1:2:3::4.
2606:4700:4700::1111
Hmm, maybe Google is easier:
2001:4860:4860::8888
Quad9 is 2620:fe::fe or 2620:fe::9
I don't understand why they can't get better addresses than that. Like surely 1::1 would be valid?
Edit: So IANA only control addresses 2001:: and up and there are quite a few IETF reservations within that. I don't know why they picked such a high number to start at. Everything else seems IETF reserved with a little space allocated for special purposes (link-local, multicast, etc.).
I'm using ATmega micros, on my Lily58. If I remember correctly, the default QMK behaviour was to use the USB to select which half was the master and what side it was on. That would work on RP2040 boards just as well so that may be what the provided firmware does.
I would suggest you just flash them both then see what they do. If they are swapped, try connecting the USB to the other half. If that works then you don't have a problem. There's no risk of damaging them and the RP2040 is pretty easy to reflash.
I wasn't satisfied with that method and set QMK to store the sides in eeprom so I could use the same firmware but connect to either one. I'm not sure if the 2040 has a separate non-volatile memory so you'll likely need a different method. I think a GPIO can be grounded to set the side but the Lily58 doesn't do this. You could add a bodge wire if you want this but you have to customise QMK to use that method.
It's just looking in a sqlite file and listing the jpeg directory. The only extra step is running icacls to let the user read the files.
Right but if I use a hammer to prove the lock I just bought is useless at protecting my shed, I'm not committing theft. This was a few lines of Python to look at data that is explicitly stored for the user to look at later.
It requires full disk encryption doesn't it? If someone already has access to your account then they can access this data the same way you can. The new issue here is that this silos a load of private data in one easy to grab location. Users would have to set up the filters perfectly to prevent recall capturing anything more sensitive than what's already accessible to their account. This is in a world where many users are probably storing their passwords in a Word document on the desktop.
Who is this 4chan guy anyway?
cross-posted from: https://feddit.uk/post/12276336
> Sorry for the crap photos - I just wanted to share these extra keys I added to my Lily58. > > I noticed there was a gap in the matrix so I tacked a spare hot-swap socket to the pads on the back of the PCB. That worked with minimal modification to my QMK set-up. I couldn't really use it dangling off some wires so I set out to make an extension that would slot in and be retained by one of the standoffs. I don't have a laser cutter or 3D printer so I just hacked these out of a sheet of ABS plastic following a printed template and glued them up. They're nice and solid and line up really well, despite being rather rough around some of the edges. > > I'm finding the 1.5U keys a bit confusing at the moment, swapping them out for 1U keys makes it a bit easier to home my thumbs. These are certainly much easier to access than the outermost keys on the lower row or the keys below the display. I'm thinking they need to be called Lily Pads. > > ! > !
cross-posted from: https://feddit.uk/post/12276336
> Sorry for the crap photos - I just wanted to share these extra keys I added to my Lily58. > > I noticed there was a gap in the matrix so I tacked a spare hot-swap socket to the pads on the back of the PCB. That worked with minimal modification to my QMK set-up. I couldn't really use it dangling off some wires so I set out to make an extension that would slot in and be retained by one of the standoffs. I don't have a laser cutter or 3D printer so I just hacked these out of a sheet of ABS plastic following a printed template and glued them up. They're nice and solid and line up really well, despite being rather rough around some of the edges. > > I'm finding the 1.5U keys a bit confusing at the moment, swapping them out for 1U keys makes it a bit easier to home my thumbs. These are certainly much easier to access than the outermost keys on the lower row or the keys below the display. I'm thinking they need to be called Lily Pads. > > ! > !
Sorry for the crap photos - I just wanted to share these extra keys I added to my Lily58.
I noticed there was a gap in the matrix so I tacked a spare hot-swap socket to the pads on the back of the PCB. That worked with minimal modification to my QMK set-up. I couldn't really use it dangling off some wires so I set out to make an extension that would slot in and be retained by one of the standoffs. I don't have a laser cutter or 3D printer so I just hacked these out of a sheet of ABS plastic following a printed template and glued them up. They're nice and solid and line up really well, despite being rather rough around some of the edges.
I'm finding the 1.5U keys a bit confusing at the moment, swapping them out for 1U keys makes it a bit easier to home my thumbs. These are certainly much easier to access than the outermost keys on the lower row or the keys below the display. I'm thinking they need to be called Lily Pads.
Hi All, I'm still very new to Nix but trying to daily-drive NixOS.
What I'm currently stuck on is injecting Python packages into a Jupyterlab service. What I have at the moment in the home-manager.home portion of my system flake is the following:
systemd.user.services.jupyter = let jupyter = pkgs.jupyter-all.override { python3 = pkgs.python311.withPackages (python-pkgs: with python-pkgs; [ numpy matplotlib ]); }; in { Service = { Type = "simple"; WorkingDirectory = "${home.homeDirectory}/notebooks"; ExecStart = "${jupyter}/bin/jupyter-lab --no-browser"; }; };
This fires up a JupyterLab process that I can connect to and which runs fine, but numpy etc. can't be imported. From a devshell, I see that the python.withPackages mechanism seems to rely on $PYTHONPATH to pass in a python3-3.11.8-env package that contains a lib/python3.11/site-packages. I'm guessing that the systemd service just needs to have an Environment key, but where do I get the python3-3.11.8-env path from?
The Jupiter executable is in a /nix/store/#-python3-3.11.8-env/bin location, but the site-packages only include the modules for Jupyter so I assume there's another python3-3.11.8-env in the nix-store that does have the python packages I'm trying to get. Trying things like jupyter.env gives errors like *** Python 'env' attributes are intended for interactive nix-shell sessions, not for building! *** but I'm just taking a stab in the dark here.
I'd appreciate any pointers on this. I see there are helpers like JupyEnv, but these seem focused on setting up ephemeral devshells, not running a service for long-term notes and seem like overkill for what I want.
RFA uploaded a short overview video of their ARGO vehicle: Youtube link Piped alternative
Explore Argo, our flexible & reliable cargo capsule with an end-to-end service for only €150M/launch for 4,000kg up-and-down mass & 15.5m³ pressurized cargo volume.
Developed with Space Cargo Unlimited Atmos Space Cargo, Argo is our commitment to rebuilding independent European space cargo capabilities.
Find out more about Argo here: https://www.rfa.space/argo/
I seem to have gotten a saved account that can't be switched to and therefore can't be removed.
My instance had some server side issues and on PC I had to delete my cookies to get the desktop site to work. Connect wouldn't work and I had to add the account again. At some point the account name has changed to my email address @feddit.uk, which looks weird since it has two @ symbols. The newly added account works fine, but there's this stuck second version of it.
When I try to switch to the broken version I get an error pop up that just says "Error: unable to switch to 'me@email.domain@feddit.uk'" and it seems to retain the currently selected account.
Since I can't switch to that account, I can't sign out to have Connect forget it. So I don't see a way to get rid of it.
Has anyone else run into the same problem? Any suggestions?
