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

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.

You’re right, and I suppose I was half-thinking along the lines of “we have all the pieces to solve this, but we don’t because we’re frozen in place by greed” instead of “this is something we could do with infrastructure today”. If everyone could collectively let go and re-distribute wealth and materials efficiently everyone would be much better off for it, but instead we’re stuck in some game theory hell where the optimal personal choice results in one of the worst outcomes.

The existence of poverty/hunger/homelessness in a post-scarcity world. if we wanted to eliminate those problems we could, but humans are blocked on how it can be done without hurting their own wealth.

Garf

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.

The app I use (Eternity) has options for 15/30/60/etc mins. You can theoretically get notifications every second if you set up your own RSS reader to check that quickly (though be considerate of your instance’s resources). Before I settled on my current solution I had an RSS reader check every so often and ding a desktop notification when it found something. I use 30 minutes because if I’m using Lemmy I’ll see the notification alert anyway, and if I’m away from Lemmy I don’t want to be notified potentially every 15 minutes when people keep replying.

Your inbox has an RSS feed that you can hook up to whatever RSS reader you want. Personally I let my Android app watch for notifications every 30 mins, and then KDE Connect will mirror that notification onto my PC when my phone dings.

These will probably need to grow naturally again. We have enough techy users to carry tech-related discussions, but we probably don’t have enough users to carry niche communities yet. By gaining more users of any kind, techy or otherwise, we have better odds of gaining people with a secondary interest in those niche communities. It’ll take some time, but the Fediverse is much more permanent, and investments here will pay off theoretically forever. Even if another open platform supersedes Lemmy, it will be easy to port our community over to it.

Not very surprising to lose users after the big intake from June. If that were the only intake we’d ever get I would be worried but we all know that Reddit will continue to do user-hostile things. Lemmy now exists as a permanent lifeboat for those who get fed up with Reddit over time, and the next time something big happens we’ll be better prepared.

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

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.

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?

This is actually quite a controversial change mainly because of their switch to a CLA. This indirectly gives them the opportunity to switch the license to closed source whenever they feel like it in the future. Semi-controversially, they are also primarly making this AGPL change in order to begin selling dual-licensing to companies. The Matrix Foundation itself does not support this change from Element, though Element is within its rights to do so.

You can read some more thoughts on this from the pessimistic folks at HackerNews. My main takeaway is that I don’t trust Element because I don’t trust anyone. I’m sure they’re doing this in good faith but I don’t like the power they have at the moment. I hope this is what’s needed to begin focusing efforts on alternative homeserver implementations like Conduit.