planish

joined 1 year ago
[–] planish@sh.itjust.works 1 points 3 months ago

The pita fix only works if you can dig up a CD drive to put it in though. Most people don't have one and are SOL.

[–] planish@sh.itjust.works 37 points 3 months ago (6 children)

That's what the BSOD is. It tries to bring the system back to a nice safe freshly-booted state where e.g. the fans are running and the GPU is not happily drawing several kilowatts and trying to catch fire.

[–] planish@sh.itjust.works 4 points 3 months ago (1 children)

Foreign to who?

[–] planish@sh.itjust.works 86 points 3 months ago (1 children)
[–] planish@sh.itjust.works 1 points 5 months ago (1 children)

I remember it as, Firefox was fast enough, but Chrome was shipping a weirdly quick JS engine and trying to convince people to put more stuff into JS because on Chrome that would be feasible. Nowdays if you go out without your turbo-JIT hand-optimized JS engine everyone laughs at you and it's Chrome's fault.

[–] planish@sh.itjust.works 0 points 5 months ago

KDE and Gnome haven't been stable or usable for the past 20 years, but will become so this year for some reason?

[–] planish@sh.itjust.works 5 points 5 months ago* (last edited 5 months ago) (1 children)

It sounds like nobody actually understood what you want.

You have a non-ZFS boot drive, and a big ZFS pool, and you want to save an image of the boot drive to the pool, as a backup for the boot drive.

I guess you don't want to image the drive while booted off it, because that could produce an image that isn't fully self-consistent. So then the problem is getting at the pool from something other than the system you have.

I think what you need to do is find something else you can boot that supports ZFS. I think the Ubuntu live images will do it. If not, you can try something like re-installing the setup you have, but onto a USB drive.

Then you have to boot to that and zfs import your pool. ZFS is pretty smart so it should just auto-detect the pool structure and where it wants to be mounted, and you can mount it. Don't do a ZFS feature upgrade on the pool though, or the other system might not understand it. It's also possible your live kernel might not have a new enough ZFS to understand the features your pool uses, and you might need to find a newer one.

Then once the pool is mounted you should be able to dd your boot drive block device to a file on the pool.

If you can't get this to work, you can try using a non-ZFS-speaking live Linux and dding your image to somewhere on the network big enough to hold it, which you may or may not have, and then booting the system and copying back from there to the pool.

[–] planish@sh.itjust.works 1 points 6 months ago

That should just be the title bar now

[–] planish@sh.itjust.works 4 points 6 months ago* (last edited 6 months ago)

I don't know why your friend doesn't like it. Ask your friend why they don't like it.

[–] planish@sh.itjust.works 14 points 6 months ago (1 children)

But now the windows one is getting scrapped whereas Waydroid is presumably sticking around.

[–] planish@sh.itjust.works 1 points 6 months ago

I think we can trust that most phone camera apps do in fact obey the toggle they provide for whether or not to embed the GPS location data in the image.

[–] planish@sh.itjust.works 4 points 6 months ago (5 children)

How do snaps make money for Canonical?

 

Obviously it wouldn't be allowed in this community, but how feasible would it be to make a community on a friendly instance and start shipping data through it somehow? If it works for NNTP it ought to work for ActivityPub, right?

Potential problems:

  1. Community full of base64'd posts immediately gets blocked by everybody's home instance.
  2. Community host immediately gets sued for handing out data it might not have a license for.
  3. Other instances that carry the community immediately get sued (see #2).
  4. Community host is in the US and follows DMCA and deletes all the posts that are complained about.

Maybe it would work as a way to distribute NZBs or other things that are useful but not themselves copyrightable? But the problem with NZBs is you have to keep them away from the people who want to send DMCAs to the Usenet providers about them, or they stop working. So shipping them around in a basically public protocol like ActivityPub would not be good for them.

 

Most of the Lemmy instances seem to require an email to sign up. That's fine, except most of the places you would go to sign up for email want you to... already have an email. And often a phone number. And almost always a first name, last name, and birthday.

I promise not to do bad stuff, but I don't want that sort of information able to be publicly associated with my accounts where I write stuff, when everyone inevitably loses their databases to hackers. Pseudonymity is good, actually; on the Internet nobody knows you're a dog, etc.

Is anyone doing normal webmail registration anymore? Set username and password, receive email for free? I don't even need to send anything to sign up for accounts elsewhere.

 

Right now, NSFW-marked communities are by default(?) not shown by their home instance to non-logged-in users in the community list, and even if you go to them manually no posts are shown.

Fine, but they also aren't shown to logged in users on other home instances, unless somehow already federated over. If you go to the community's instance, it can't tell you are logged in, and if you go to your home instance you can't see a list of all communities on the other instance that might be available.

Also, older posts that are marked NSFW can't be gotten by anyone with an account anywhere other than the instance they were posted to. When you subscribe to a community on another instance it federates over a few posts, but to doesn't request and federate older posts as you try and page back through the archive. The normal solution is to view the old posts on the source instance, but if the community is marked NSFW the source instance won't let you read the archive there without a local account.

view more: next ›