If you don’t want to open this and solder a chip, then no, you can’t do what you want.

The closest you can get is to enable AutoRCM, which will cause the Switch to always boot into recovery mode and accept a payload. This skips the need to use a jig in the Joy-Con rail, but you still need to inject a payload. And because recovery mode is just a black screen, you don’t have any visual feedback to know if the Switch is actually in recovery mode, or if the battery is just dead.

Your best option is to just boot into whatever OS you use most, then make it a habit to keep it charged enough to not shut down.

They just sent out a mass email to users yesterday informing us of this, I got it too. I wonder if it wasn’t getting enough attention, or if they wrote this back in June but only just made the article visible.

I use Backblaze B2, but stored in an encrypted Restic container, set up using this guide:

https://helgeklein.com/blog/restic-encrypted-offsite-backup-with-ransomware-protection-for-your-homeserver/

Restic has been great for automating backups, and even letting me mount the encrypted storage to grab individual files. I like doing it this way since I don’t have to trust Backblaze isn’t reading my data - I know for sure that they can’t.

Performance of storage that is both remote and encrypted is about what you would expect, but I don’t need access to the data unless something bad happens.

Ok… sure. But what physical devices would I use, and what software would they run?

Are there any “open” solutions to mesh networking that can compare to TP-Link Omada? I don’t think any open source hardware or software can come close, especially not for the newer Wi-Fi standards.

I haven’t bought them yet, but I’m seriously thinking about some Omadas. I imagine I can prevent them from phoning home, and the management software can run locally in a Docker container. Running it like that would be good enough for me even though they’re not “open.”

I’m planning a rework of my home Wi-Fi, and my current plan is an OPNsense box from Protectli, and a few EAP772’s:

https://www.tp-link.com/us/business-networking/omada-wifi-ceiling-mount/eap772/

If there’s something comparable/better that’s more of an open ecosystem, you definitely have my attention while I’m shopping around for different options.

Definitely recommend Motrix:

https://motrix.app/

If the Google download link supports it, it should be fairly resistant to interruptions. If it doesn’t, this might not help much, but you should still use this instead of just a browser.

I haven’t tried to download a Google takeout, so you might need to get clever with how you add the download link to it.

If you just can’t get it to work, you can try getting the browser extension to automatically send all downloads to Motrix. There is some setup required, though:

https://github.com/gautamkrishnar/motrix-webextension

Good luck!

Everyone sees this notice, I saw it on the official desktop Firefox client. They’re just trying to reach as many people as possible.

What do you mean? RPCS3 is an excellent emulator. It’s not completely hardware accurate, almost no 3D emulator is, but it’s still pretty good.

Before it got enshittified with an update a few years ago, I used the RealVNC Android app to connect to a few of my own VNC servers. Wasn’t interested in any of the fancy features, I just wanted a good VNC app.

Now I use AVNC. It’s solid, performs better than RealVNC used to, and it’s open source! You can get it on FDroid.

It should still work!

I only go back and make changes to LED if something breaks with a major Lemmy update, but Lemmy hasn’t had a major update since January. Lemmy v0.19.4 isn’t released yet, but when it is, I’ll make sure the deployment is up to date.

Note that it does not have any advanced features that a major instance might want, such as storing images on S3, exporting data, or image moderation. If you intend for your instance to grow for 100+ users, this isn’t for you. This is only intended for beginners who are overwhelmed by the other Lemmy hosting options, and want an easy way to host a small single-user or small-user instance.

Cloudflare Tunnels are black magic and exactly what you’re looking for:

https://developers.cloudflare.com/cloudflare-one/connections/connect-networks/

Free, no need to self host a server somewhere externally. Can even be used for SSH!

I’m scratching my head to think what Vultr could do better in this case

There was substantial room for improvement in the way they spoke publicly about this issue. See my comment above.

I still don’t like how flippant they’ve been in every public communication. I read the ToS. It’s short for a ToS, everyone should read it. They claim it was taken “out of context,” but there wasn’t much context to take it out of. The ToS didn’t make this distinction they’re claiming, there was no separation of Vultr forum data from cloud service data. It was just a bad, poorly written ToS, plain and simple.

They haven’t taken an ounce of responsibility for that, and have instead placed the blame on “a Reddit post” (when this was being discussed in way more detail on other tech forums, Vultr even chimed in on LowEndTalk).

As for this:

Section 12.1(a) of our ToS, which was added in 2021, ends with “for purposes of providing the Services to you.” This is intended to make it clear that any rights referenced are solely for the purposes of providing the Services to you.

This means nothing. A simple “we are enhancing your user experience by mining your data and giving you a better quality service” would have covered them on this.

We only got an explanation behind the ToS ransom dialog after their CMO whined in a CRN article. That information should have been right in the dialog on the website.

In both places, they’ve actively done vague things to cause confusion, and are offended when people interpret it incorrectly.

There was no judgement, only a settlement. Yuzu is not “illegal.” Nintendo can abuse DMCA and request GitHub take these down, and GitHub will probably listen, but Nintendo would not be “legally in the right” to do so.

I’m not talking about that. I’m talking about this:

I agree with the sentiment here, but all the technologies mentioned allowed us to ship a working application in a timely manner. I think that should always be the first goal. Now that this is out of the way, we can start looking at improving efficiency, security, resilience etc.

“Security Second” is not good messaging for a project like this.

But I’m glad my comment was hilarious to you.

I don’t need or want replication of my private projects to a peer to peer network. That’s just extra bandwidth to and from my server, and bandwidth can be expensive. I already replicate my code to two different places I control, and that’s enough for me.

I’m not sure who Radicle is for, but I don’t think the casual hobbyist looking to self host something like Forgejo would benefit at all from Radicle.

Loading the source code for Radicle on Radicle also seems fairly slow. It seems this distributed nature comes at a speed tradeoff.

With the whole Yuzu thing going on, I can see some benefit to Radicle for high profile projects that may be subject to a takedown. In that respect, it’s a bit like “Tor for Git.”

I suspect that over time, pirate projects and other blatantly illegal activities will make use of Radicle for anti-takedown reasons. But to me, these two projects solve two different problems, for two different audiences, and are not really comparable.

Edit: There is already enough controversy surrounding Radicle, that, if I were someone looking to host a takedown-resistant, anonymous code repository, I would probably be better served hosting an anonymous Forgejo instance on a set of anonymous Njalla domains and VPSes. The blockchain aspect was already a bit odd, and what I’m now seeing from Radicle does not exactly inspire confidence. I don’t think I’ll ever use this.

The API that FDroid is using has only just come out.

Not true. Android has supported rootless unattended upgrades at a system level since Android 12 (October 4 2021). That was nearly 2 and a half years ago, so it’s been a while.

This is what Neo Store used. F-Droid only just now got around to supporting this with this recent update.

Makes sense. The article calls it “unwarranted gatekeeping,” but they wouldn’t say that if they knew how Android internals work.

Looking at the video demo for Circle to Search, it’s very likely they built this on top of ActionsServices, an Android component that enables extra interactions on top of the Recents switcher. This is already what’s being used to do things like OCR in the Recents switcher.

Other non-Google ROMs use ActionsServices too, but their implementations vary, and they can’t just “tack on” something as complicated as this onto any vender implementation of ActionServices and expect it to work. They might not even have a vendor rollout plan for this thing yet, for all we know it was rushed out the door.

Google has had a tight partnership with Samsung since the Pixel 6 came out, which is why it doesn’t surprise me that Samsung will be getting this feature first. Google can essentially boss Samsung around for little system things like this.

The “for a long time” comment was probably due to Android 15 already being mostly final at this point. I wouldn’t be surprised if there were core changes to Android to allow more pluggable customizations to the Recents switcher in Android 16. That might enable Google to offer this feature to other vendors more cleanly (assuming the feature survives that long, which is doubtful).

You are giving it the -d flag. -d means “detached.” There are logs, you are just preventing yourself from seeing them.

Replace the -d with an -i (for interactive) and try again.

Have you completed the podman rootless setup in order to be able to use it? You may need to edit /etc/subuid and /etc/subgid to get containers to run:

https://github.com/containers/podman/blob/main/docs/tutorials/rootless_tutorial.md#etcsubuid-and-etcsubgid-configuration

More than likely, this might have something to do with podman being unprivileged, and this wanting to bind to port 80 in the container (a privileged port). You may need to specify a --userns flag to podman.

Running in interactive mode will give you the logs you want and will hopefully point you in the right direction.

It is. The user just won’t see any content from the server they blocked.