rokejulianlockhart

joined 2 years ago
[–] rokejulianlockhart@lemmy.ml 2 points 1 month ago

That's why it's considered good practice to act on the presumption of innocence until proven guilty.

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

Matrix, via Element.

 

I'd like to install PMOS onto my Fairphone 5, because TWRP recently became available for it. However, the comments and post above this Reddit comment appear to demonstrate that the PMOS installer might overwrite all partitions (A and B, but also Recovery), if I've understood it correctly.

Has anyone used both together? If so, can you confirm whether it functions (as expected)?

 

After researching why current consumer and embedded ARM (and, to a lesser extent, embedded RISC-V) devices are difficult to port to, the primary reason appears to be device discovery and driver support.

Obviously, extracting proprietary drivers from a potentially outdated AOSP-based OS version with a probably quite outdated kernel and getting that to run in mainline is a lot of work.

However, getting device trees shouldn't be, and really shouldn't be necessary, since they're not something that a manufacturer would hope close to their chest, unlike complex driver software.

Consequently, I would like to request to Fairphone – considering their mission statement – that they provide device trees and enumerable busses (if they don't) but would like to verify here that I wouldn't look like a moron asking for the wrong thing.

I hope this makes sense.

[–] rokejulianlockhart@lemmy.ml 2 points 3 months ago (1 children)

Is it FOSS? I'm having a difficult time locating its source.

[–] rokejulianlockhart@lemmy.ml 1 points 3 months ago

No, I had not. That's certainly novel.

[–] rokejulianlockhart@lemmy.ml 2 points 6 months ago* (last edited 6 months ago)

Those criticisms seem reasonable. Regarding package signing, are you referring to https://github.com/NixOS/nix/issues/613#issuecomment-134361033? Additionally, that default for pip seems veritably insane. I understand using system packages, but modifying packages outside the virtual environment is definitely weird.

[–] rokejulianlockhart@lemmy.ml 2 points 6 months ago (2 children)

Can you elaborate?

[–] rokejulianlockhart@lemmy.ml 2 points 6 months ago* (last edited 6 months ago)

I used it yesterday, via Pidgin. I'm rokejulianlockhart@xmpp.jp. Why else would I have referenced it? Don't tell me what I've done. That's not a way to have productive conversations.

Regardless, I can't provide any more technical insight than that - I know solely that the clients provide so much more functionality that irrespective of the protocol, it's better in practice. Fedora, openSUSE, the Bundeswehr, NATO, and Beeper - all chose Matrix over XMPP, not least partially because of Element (which they also all chose).

[–] rokejulianlockhart@lemmy.ml 1 points 6 months ago* (last edited 6 months ago) (2 children)

I don't believe that its existence causes more fragmentation than it remediates. https://news.ycombinator.com/item?id=36939482 explains why I consider Matrix fundamentally superior most (if not all) uses, although in practice it's because the clients (Element and FluffyChat primarily) are cross-platform and support a generally uniform set of features, in comparison to the aged (but glorious) Pidgin, and its counterparts.

[–] rokejulianlockhart@lemmy.ml 1 points 7 months ago

Its bridges are FOSS, but its client (an Element fork) doesn't appear to be.

[–] rokejulianlockhart@lemmy.ml 2 points 7 months ago* (last edited 7 months ago)

Yeah, my experience with Element and a Matrix.org account is that it's sluggish. However, it's been better at Beeper, so I'm uncertain whether it's intrinsic to Matrix or merely Matrix.org and/or Element's servers.

[–] rokejulianlockhart@lemmy.ml 1 points 7 months ago* (last edited 7 months ago) (2 children)

Where did you get that from? I haven't found a relevant blog post.

view more: next ›