- 0 Followers
- 0 Following
- 1 Posts
KOReader for books, and Mihon for manga and comics. KOReader is spefically designed for e-ink displays, and Mihon has a setting to flash the display when changing pages to reduce ghosting on e-ink displays.
If the pollution bothered them so much, why do they building nests in it? That sounds like their problem ¯\_(ツ)_/¯
Have you tried increasing your first layer extrusion width? A wider first layer will squish the filament into the build plate more, which might help. I use a 140% first layer width.
I’ve been using FolderSync. It let’s you sync to/from a remote server through a bunch of different protocols like SMB, SFTP, and WebDAV. You can schedule it to run automatically.
I haven’t tried it myself, but I think there is a way you can get Tasker to run scripts in Termux. You could set up your own rsync scripts that way.
If you’re worried enough to encrypt the drive, you shouldn’t be auto mounting it.
This really depends on your threat model. If you are only concerned about the drive getting stolen, or wanting to keep the data on it private if you need to RMA the drive, mounting it automatically on boot with a key stored on the rootfs can be perfectly fine. If you are a journalist in a hostile country and protecting your sources from state level actors is a matter of life and death, then yeah, this would be woefully insufficient.
It can be. Some of those keys might just taking advantage of regional pricing to buy keys in cheaper markets and resell them elsewhere, but some of them are purchased using stolen credit cards. Those actually cost the devs money from chargeback fees once the actually owner of the credit cards finds the fraudulent transactions. It’s hard to say how many of them are from stolen credit cards, and key-resellers try to stop it, but it still happens. This was back in 2019, but the Factorio devs had a couple blog posts talking about G2A:
Blog post saying G2A is worse than piracy
Follow up blog post where G2A reimburses them (at very bottom)
Friday Facts #303 - Under 100 bugs (but still not stable) | Factorio
Under 100 bugs We have a record low in our bug report forum, of only 55 active bug reports. I don't think in the history of Factorio the bug forum has been so clean. No doubt once we mark 0.17 as stable the count will shoot up again. For this weeks graph I added the count of players on Steam as the left axis. We thought it would be somewhat interesting to see if there is any correlation between the two. Note: The axis have different scales. I also prepared the same graph but for the duration of the 0.17 release. You can see our player numbers are dropping quite a lot, from the all time peak of 22,457 on the 3rd of March 2019. While bug reports might be at an all time low, we are not going to call the game stable yet. We still have an important milestone to reach, that is, implementing the new Introduction campaign graphics (FFF-301). A lot of the team has been on vacation these last few weeks, including the whole campaign team and most of the art department. What this means is that we expect it will be a few more weeks before we can call the current version stable. We have been asked a few times when stable will be released, but my question is, why does it matter exactly which version we call stable? Are you waiting for stable to play a new playthrough? The thing is, this stable is only going to be the 'first' stable. Our plan is to have a number of short experimental phases after the first stable, where we will add new GUI's and such, which will add bugs and technical debt. After fixing the bugs in a 'small' experimental content release, we will then mark that as the 'new' 0.17 stable. Besides, there are still a few edge cases with signals that kovarex is busy fixing: For instance the setup above took him 3 hours to fix. The cause of the issue was that the segment has both an incoming and outgoing signal at the same position.
- What steps did you take to rollback your root partition?
- Can you log into the emergency shell and share any logs?
- Is your root partition mounted in the emergency shell, or is the initramfs still mounted in the emergency shell?
I pre-ordered the 128GB SKU in the second wave. Soldered RAM doesn’t matter to me if I am already maxing out what the platform is capable of. If I can dynamically configure the memory allocation between the CPU and GPU, this will be an extremely potent little AI workstation. I’ll be able to cancel the pre-order of things aren’t what I expect, and it isn’t much of a loss for me ($100 refundable deposit).
I do agree that this branching away from Framework’s roots, but I am still very happy that they are doing interesting things. I’ve always thought that what Minisforum has been doing with their SFF workstations has awesome, so I’m glad to see other companies wading into the same space.
Apparently Framework did try to get AMD to use LPCAMM, but it just didn’t work from a signal integrity standpoint at the kind of speeds they need to run the memory at.
What filesystem are you using on the external drive? If it is NTFS or FAT, they won’t store permissions on the filesystem, which would explain why the owner/group changes are not persistent. To fix that, you can set the uid/gid on mount in your fstab.
/dev/mapper/YOUR_DRIVE /path/to/mnt <fstype> rw,uid=<jellyfin_uid>,gid=<jellyfin_gid>,dmask=0002,fmask=0113