Most of the things Psygnosis did; the Wipeout series, G-Police and Colony Wars being the most obvious choices. Tomb Raider is another good one, as are the Tony Hawk games. X-COM: Enemy Unknown is meant to be a solid port of the classic turn-based tactics game. I've heard praise for the Twisted Metal games and Syphon Filter, but haven't played them myself. While I know that old sports games are often considered anathema in the retrogaming sphere, Jonah Lomu Rugby is often considered one of the best games depicting rugby union ever made.
The parts where they go into detail about whale hunting was like reading a manual, I did not know there where other editions and just got the frost one I saw. Maybe it was my part for not investigating before.
I still see Kobo recommended these days, so an upgrade might be a good option for you. I use a Kindle, but that obviously locks you in with Amazon. I wish I’d have gotten a Kobo myself.
That’s cool, I tried a kindle paperwhite, but returned it because I kept accidentally hitting that stupid power button they put on the bottom right where you hold it while reading.
I’m not sure if it’s the same everywhere but in Canada you can for sure. Kindle has a very slightly better selection (small press horror lit tends to be missing from Kobo) but doesn’t support Overdrive here.
My daughter reads a lot of books checked out via overdrive on her kobo (in Canada), though the search feature on the kobo itself is kind of garbage. We have better luck doing a search with the Libby app on a phone, checking it out, then syncing the kobo.
I use a Kindle myself (purchased on one of the good sales for roughly half price), though primarily via epub files transferred to the Kindle using Calibre. It’s a busy UI, but it does work well and has lots of features. Pretty good as an archive of your ebook library.
I use a Kindle, but that obviously locks you in with Amazon.
On my old Kindle I could connect it to USB and put any books I wanted on it. It supports TXT and MOBI on top of AZW. Is that no longer the case for newer Kindle models?
Any Lemmy/fediverse instance could come up with a localized monetization scheme for people that browse through it, but it wouldn't affect other instances (or if they were injecting ads into feeds, they'll just get blocked by everyone else), but for the most part, it's got more of an IRC server vibe, no monetization needed when community volunteers are plentiful and the barrier to entry is low. Eventually 'big boys' like Lemmy.world will want a more formal and reliable way of paying for their server and bandwidth needs beyond primarily unsolicited donations ($ and time) by volunteers.
These are not profit generating services, they are community services. For now.
If you want to break free of an ecosystem / format you can go to a brand like Boox or Pocketbook. I have a pocketbook and like it, but some people think they are klunky/laggy (I wanted a smaller, water resistant reader).
I moved away from Amazon because I didn’t like the idea that they could delete or change a book I had paid for and I hated the ads for books/store on my e-reader.
If you go this route you will likely need to get Calibre free software to load books on your reader, so it does depend on how technical you are prepared to be. Not a steep learning curve but there are some recommended plugins, especially if you want to move books that you have bought on the Kindle Ecosystem. You can also go deeper and do things like have the software auto-estimate page # and reading difficulty, as well as implement tagging/organization systems, change/optimize covers, etc.
Cool, Pocketbook Touch Lux 5 looks pretty good, since it’s the smallest one. But water resistance is a good idea, that’s why my kobo stopped working actually. And I can’t see anything on that model about water resistance. Which did you get?
It’s so good because a lot of people have been waiting for a viable alternative to Reddit for half a decade or longer. It’s non-corporate internet, the way it should be.
I think it's more like a hobby, it doesn't necessarily NEED to be profitable as long as you and other people enjoy it and contribute to it. So far I'm loving it and it really feels like a breath of fresh air compared to reddit, especially without the karma system
Ok, so I have a very unique background in systemd. I worked at Red Hat supporting it basically as the primary support and I’ve worked with the developers of systemd at Red Hat directly. I no longer work there.
So first off, it’s “systemd” all lower case. I don’t care, but for some reason Lennart Pottering (creator) does.
systemd was a MASSIVE change. And Red Hat did a TERRIBLE job relaying it. To the point where I’m still trying to get my company to understand that it can NOT be treated like the old init systems. You can NOT just drop an init script in place and walk away and hope it works. Because a LOT of times it doesn’t. Due to forks, switch users, etc.
systemd is NOT an init system. RHEL 5 and older had sysvinit as it’s init systemd. RHEL 6 had UpStart as it’s init system and looked exactly like sysvinit that no one even noticed. systemd again is NOT an init system. Init system is 1 part of systemd. systemd does a lot of cool things. It bundles applications together, it manages those applications and can restart them or kill children, it can do resource constraints, it separates out users from the system, and lots more.
Because it is not an init system there is a LOT LOT LOT of bad recommendations out on the internet where someone has X problem and person suggests Y and IT WORKS! … except it doesn’t REALLY work as far as systemd is concerned and you’ll hit other issues or your application takes longer to start or stop and people just blame systemd.
It is systemd’s fault that it has done an ATROCIOUS job of helping people adapt. It’s a great example of RTFM. systemd’s man pages are INCREDIBLE and extensive, but when you drop so much knowledge it becomes more difficult to find what you want/need. systemd.index and systemd.directives are your best bet.
So systemd does a lot of amazing things that sysvinit never attempted to do. It’s never attempted to explain anything it expects everyone just learn magically. it’s INCREDIBLY complex, but once you understand it’s basics you can more easily get an application running, but as soon as there’s a problem it’ll just break your brain.
To give you an example, sshd’s old init script is like 250 lines of bash. systemd’s unit file comparative is like 12. Because systemd handles a LOT of what you manually had to handle before. BUT to get to that 12 you literally have to learn EVERYTHING new.
There is no “is it good or bad” here really imo. It’s a completely different fundamental design. Red Hat made it for themselves. Other distros picked it up. It can be argued that lots of folks followed Debian and Debian had a few Red Hat board members that were pushing it. Whether they pushed it of their own accord or because they were with Red Hat I don’t have a clue.
What I can say is at my current company they’re suffering from a LOT of systemd issues and they don’t even realize it. I’ve been working with Red Hat to try to get Insights to alert people to the failures and we’re making progress.
To see if you have issues just to start run the two following commands:
If you have any units that are failed, investigate those. If you don’t need them, disable them. As for the systemd-cgls this shows HOW systemd is grouping things. ANY application that runs as a service (or daemon or application or runs in the background or however you wanna say it) should be under system.slice. ONLY humans logging into the system (meat bags NOT applications switching to users) should be in user.slice. A LOT of times what happens is an old init script is dropped in place, they start it, it has a switch user and systemd assumes it’s a user and puts it into user.slice. systemd does NOT treat anything in user.slice the same as in system.slice and this WILL eventually cause problems.
So again, is it good or bad? Eh. It does a lot of cool things, but they did a MASSIVE disservice to ALL of us by just expecting to relearn absolutely EVERYTHING.
sshd’s init script under OpenRC is 87 lines, of which around half are blanks, comments, closing braces, and other boilerplate. Granted, that still makes the real code maybe three times the size of your systemd unit file, but the difference isn’t as impressive as you’re making out.
95% of people shouldn’t need to poke around in their init scripts or unit files anyway. If you actually need to do that, your use case is already somewhat unusual.
As an end user, unless you’re running a server, then no you shouldn’t have to mess with any of it.
If you’re running a server or a sysadmin you absolutely 100% should be paying attention. Almost every single vendor I’ve seen selling their applications only have initscripts. Which then cause issues. I’ve gone to the vendors and told them and they’ve said go to Red Hat. Well Red Hat doesn’t support that vendor’s init scripts.
Not naming an application, but it was from a BIG BLUE company and they said their only instructions are to call their script from the user. But it won’t remain running if you do that because systemd will close out the slice when the user logs out. SO it’s obvious they haven’t tried what they’re suggesting.
And I’m not attempting to state that systemd is impressive in any way. systemd basically took what had been building over 40 years of init scripting and threw it out the window and said our way is better. I don’t think it is. I’m just saying, with a directive based unit file it’ll be simpler to parse than a bash script.
I’ve actually been looking into this myself, and Kobo seems like the most ‘open’ option. The Libra 2 in particular fit my requirements for size and features. It supports quite a few ebook formats but I think it’s limited to Kobo’s own audiobooks only.
If anyone has one I’d be interested to hear your thoughts.
Got one today actually and after removing the DRM from my kindle books. I loaded it up in 2 seconds. I also installed the Amazon and Google ereader fonts because I love Bookerly. It’s great so far. Feels nice to hold. It’s snappy. 32GB of storage.
Unfortunately at the moment it does only support Kobo audiobooks but it does let you use Libby and borrow ebooks/audiobooks from your local library. I usually use Audible on my phone anyway so I’m not really bothered by that. Would be nice to have though.
Screen is just as good as my Paperwhite with a better eye-comfort mode.
My only annoyance so far is that it’s frozen twice which required a reboot. This might be because I’ve been using I a lot today and connecting and disconnecting from my laptop etc but it’s something I’ll be keeping an eye on.
Edit: hasn’t frozen again in the entire time since.
kbin.life
Oldest