mbirth

joined 1 year ago
[–] mbirth@lemmy.ml 2 points 1 month ago

If it’s the system with the (locked) KeePass database on it, you should be fine. The encryption can be tweaked so that unlocking the database takes a second even on modern systems. Doesn’t affect you much, but someone trying to brute-force the password will have a hard time. It also supports keyfiles for even more security.

If somebody infiltrates your end user device, no password tool will be safe once you unlock it.

[–] mbirth@lemmy.ml 31 points 1 month ago

Yep, the article is about Apple showing cops how to use the tech, what apps the police in other countries is using to support their daily work and the police evaluating the use of more Apple tech in their daily duty (Carplay, Vision, etc.).

There’s nothing about spying on normal Apple users or Apple handing out your personal data to the cops in that article.

Clickbait headline.

[–] mbirth@lemmy.ml 16 points 1 month ago (3 children)

After trying them all, I’m back at having a local KeePass database that is synced to all my devices via iCloud and SyncThing. There are various apps to work with KeePass databases and e.g. Strongbox on macOS and iOS integrates deeply into Apple’s autofill API so that it feels and behaves natively instead of needing some browser extension. KeePass DX is available for all other platforms, and there are lots of libraries for various programming languages so that you can even script stuff yourself if you want.

And I have the encrypted database in multiple places should one go tits up.

[–] mbirth@lemmy.ml 5 points 1 month ago (1 children)

Yeah, but I didn’t want to fiddle with some custom settings. The same official postgres container works great with other apps.

[–] mbirth@lemmy.ml 6 points 1 month ago* (last edited 1 month ago) (4 children)

I didn’t notice any big drops in network or CPU performance. Usually, because other network traffic had priority. But my server’s HDD constantly rattling along got me thinking that it wasn’t worth it. There are several other containers running on that box and I don’t have that much HDD activity with them.

[–] mbirth@lemmy.ml 21 points 1 month ago (8 children)

I did this for a while. However, after subscribing to several groups, there was constant disk activity and it ate network bandwidth. After two months I’ve stopped my server and went back to using a public instance.

[–] mbirth@lemmy.ml 2 points 1 month ago

Oh, wow, in this case this is indeed the better tactic.

[–] mbirth@lemmy.ml -3 points 1 month ago (3 children)

Limiting charging to only 80% doesn’t do that much. It about halves the battery degradation but that’ll only be a noticeable difference after 3+ years where most people either get their battery replaced or get a new phone anyways.

[–] mbirth@lemmy.ml 4 points 1 month ago

Yep, we have desks at work with a built in AC socket and USB-A and USB-C for charging phones. Guess what? The USB-C only delivers 5V and thus is unsuitable to power Apple’s travel charger for MagSafe and Apple Watch.

Same with our £600 Dyson lamps. They all come with an USB-C outlet. But, again, it’s only providing 5V, no PD.

Apart from that, I’m also pretty happy with USB-C everything. Even though I still think Lightning is the better design in terms of robustness of the socket. No thin plastic lip that can break apart.

[–] mbirth@lemmy.ml 8 points 1 month ago (2 children)

It will save so many £££s heating costs, though!

[–] mbirth@lemmy.ml 2 points 1 month ago (1 children)

Your iOS devices should appear in Finder if they’re either connected via cable or in the same WiFi. Click the device to open the overview page in Finder. Drag&drop the .m4r file from another Finder window onto the overview page. The ringtone will be installed.

[–] mbirth@lemmy.ml 4 points 1 month ago (4 children)

Yep, just do it in macOS using any audio editor, save up to 40 seconds as AAC M4A file, rename to .m4r and drag&drop onto your phone/iPad in Finder. Done.

view more: ‹ prev next ›