

What issue did you have? If I can handle it for the user automatically, I can add a best effort attempt to avoid it.
What issue did you have? If I can handle it for the user automatically, I can add a best effort attempt to avoid it.
Hi!
The project is still active! I just haven’t needed to develop any updates because it’s currently stable, and the upstream Docker compose template, which is a reference for my project, hasn’t changed in 9 months:
https://github.com/LemmyNet/lemmy-ansible/blob/main/templates/docker-compose.yml
Whenever Lemmy releases a new Docker container, it will just pull the latest one automatically. This will continue to be compatible indefinitely until the compose deployment (linked above) has any breaking changes added to it that I need to incorporate.
Thank you for the shout out :)
Just being open source is not enough to solve this problem. You would need a record of your “home instance” stored somewhere that all Lemmy instances would always have access to it. Ignoring the security implications of that, you still can’t use browser storage or cookies for that storage. In browsers, those storage mechanisms are restricted to the websites that stored them in the first place. Browser extensions have their own storage, so they don’t have this limitation.
I can’t think of an architectural solution to this problem without a browser extension.
The closest alternative that could be upstreamed is what Mastodon does, which is prompt the user to enter their home instance every time they try to interact with something while not logged in. An upstream solution can never be fully automatic like a browser extension, but this may be “close enough.”
They explain it in the video. They already use algorithms to detect if things are buildings or not.
But if their algorithm can’t make a determination or is uncertain below a certain threshold, they send it to Maptcha to get a bulk human opinion.
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.
I’m really curious to learn how you get calls in so many different languages. I could definitely see Spanish, English, and maybe Vietnamese all being spoken in a general geographic area, but you listed a lot of diverse languages. Pretty cool if that’s really all within one area!
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:
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:
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!
OF requires strict government issued ID verification in some jurisdictions. Patreon does not, at least in the US.
That should be your deciding factor already. No one should have their privacy invaded just to send you a few bucks a month.
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.
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.
It was just how the settlement was worded; this team is prevented from distributing “anything that circumvent’s Nintendo’s blah blah,” and Citra was developed by the same team. So, it got taken down all the same :(
Ah I see. I’ve gotten into some back and forth with the maintainer of Caddy about these build inconsistencies and lack of versioning, and he responded by locking issues on me… twice.
After that communication, I resigned to just keep things as they are because upstream is not willing to make the experience better for use cases like these.
He is impossible to work with, but Caddy is just really good :/