You probably have a higher attack surface from the gremlins in your walls. OTOH, Amazon knowing that you use Mullvad is a tangible downside, as they will probably use that to stick you in a marketing group or something. Monero is still an easy solution with the ~same cost if you’re concerned about that.

How would Amazon track a voucher? It’s a physical scratch off code, sealed by Mullvad before they send it over to Amazon. More importantly, if you think that was possible why would Mullvad be unaware of it and/or lie about it? Just go with the vouchers if you want untraceability. They’re also cheaper in USD than other methods IIRC, at $29/6 months and $57/12 months.

I wrote a short guide on this method recently: https://lemmy.ml/comment/6708735

I feel piracy for demo purposes is fully justified if you buy it after you like it. People always say vote with your wallet but it’s more like gambling with your wallet if you don’t get to see and touch the product before you make the purchase. Giving proper demos should be more common with digital media.

Wow I feel dumb for not thinking of that. In my defense I like the text as #FFF on gray. KOReader’s arbitrary CSS snippets and style tweaks are really neat.

This is all I needed to do so: https://www.mobileread.com/forums/showthread.php?t=314220

Run the script from the second post, then eject the Kobo and let it install. Afterwards you can open it from the new NickelMenu button at the bottom right. My Kobo just stays in KOReader mode all the time.

You can change the background color by changing the ["cre_background_color"] key in settings.reader.lua (again, I dislike needing to configure it like this). On my Android and desktop I set it to ["cre_background_color"] = "0xECECEC",, which inverts into a nice gray when I set it to night mode, then I invert all the image colors so they’re a normal color. Font color can’t be changed though, TMK. You can change font color with custom CSS snippets.

deleted by creator

Have you tried KOReader yet? It’s not Material UI and doesn’t have any sort of “theme”, since it’s very focused on just showing your text, but it lets you extensively pick fonts and styles for your books, has dictionary lookups (tap and hold), page view, and it can sync with itself (available on the desktop and many physical ereaders). My main gripe is that it’s very configurable, and I don’t personally like many of the defaults. After setting it all up it’s quite powerful, and I use it on my physical ereader, Android phone, and desktop PC in roughly the same configuration.

That was my takeaway from this video as well. It was a lot of “aw shucks can’t we all just get along” and not understanding that in today’s world, getting along is a left-wing policy. I think there is still merit to saying that part of the reason we’re so divided nowadays is that we are forced to interact more often, but it shouldn’t be represented as the entire problem. In a way, I think a video like this is actually worse for discourse because it might convince people that there is only one problem that needs to be solved.

The real problem is that everyone is using the “All” tab as a content feed. Ideally everyone would subscribe to communities and then they wouldn’t have to worry about seeing things they don’t want to see. Lemmy needs to be bigger before we can break that anti-pattern.

We are always “losing money” in this sense unless we are buying and selling the optimal assets every day. Even their example of the “winning” S&P 500 is still just an index scooping up all the big losers along with all the big winners. We diversify because we can’t pick the winning assets every time, so if you understand the benefits of diversification I feel like the drawbacks are already obvious.

I didn’t mean my post to be read as trying to convince someone to use Linux, but as someone trying to convince themselves to use Linux. It’s fairly common that people want to switch but have convinced themselves that unless they have their exact same workflow from Windows they won’t be able to.

Break the beef into smaller pieces first so the germs can’t find it.

I’ve seen a trend where people move the goalposts on the reasons they’re not able to switch. “If only this program worked I could switch”, but when that program is ported it’ll be a new excuse next. Sooner or later you’ll have to draw a line and say “99% of my stuff works, the 1% that doesn’t can get bent”.

All I need to know this election is whether you are pro-Roko or anti-Roko.

Yeah I wouldn’t bother. It intends for you to have a duplicate copy on every device, which is probably not what you want. Syncthing is really good for things like synchronizing notes, calendars, password databases, music, etc to your devices. Things that you want to access in both places, but that are usually disconnected from each other from time to time.

As a Debian user I agree with Loius Rossmann’s sage advice.

Edit: (make sure you enable unattended security upgrades at least so you can pretend that you only update once every few months)

Conduit is also licensed under Apache 2.0, so it could also be taken closed source at any point in time. The reason this wouldn’t impact Conduit as much is that there’re other contributors, whilst Synapse and Dendrite are almost exclusively developed by Element.

Right. The current perspective is based on the idea that if Synapse/Dendrite go closed-source right now, an open source version would be good as dead. Element is responsible for 95% of Synapse/Dendrite and I’m sure a community fork would have to play a lot of catch-up to figure out how to keep it going. If the community was more involved in Synapse/Dendrite implementation (and if Element let them) there would be less cause for alarm, as closing the source would just mean an immediate community fork and putting Element on ignore. Also to reiterate, The Matrix Foundation is not going along with Element on this move, and even if Element pulled something shady the Matrix Core Spec etc. would still remain open and under the Foundation’s control, so the max we have to lose is Synapse/Dendrite and all of Element’s developers.

As for the rest I agree and I do actually trust that Element is simply playing their only card here. These maneuvers are all required in order for Element to survive as a company at all, but they also unfortunately leave this backdoor open as a consequence. Matthew has pinky-promised over and over that they are only acting in good faith and that they would never use the backdoor, but it’s understandable that the presence of the backdoor is putting everyone at unease. Best case scenario we take this as a warning sign that if Element drops dead tomorrow then Matrix is also dead. If people want Matrix to not be practically owned by Element then we should diversify and prepare escape plans.

It depends on what your workflow/usecase for putting documents on the drive currently is. Syncthing is usually intended to be put on two separate devices, and then a folder on each device gets synchronized - meaning you have a folder of your documents on each device. Is there any reason not to just mount the network drive’s folder and drag the documents in that way?