PoorPocketsMcNewHold

joined 4 years ago
[–] PoorPocketsMcNewHold@lemmy.ml 2 points 7 months ago

Maybe you would be interested into maintaining Gradience instead of making a new LibAdwaita theming app from scratch ? Just thinking, haven't tested it but I don't see any straight reasons for one over the other outside the maintainership. https://github.com/GradienceTeam/Gradience

[–] PoorPocketsMcNewHold@lemmy.ml 8 points 7 months ago (1 children)

They don't. They rely entirely on donations (and sponsorship donations). It also mean, they have less resources to maintain and develop their software, ESPECIALLY Conqueror since it's not as much well-maintained compared to other parts of the KDE software suite. Plus, Firefox do maintain their own web-engine, while KDE just use the WebKit one, so even more reasons that Firefox can't substain with the resources KDE currently has.

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

Sure do confirm that hard-coded sudo requirements are kinda dumb. But this proove systemd point. BSD mainly use doas. Linux mainly use sudo. Why not have an universal method for true cross-platform compatibility ? (Yes, I know plenty prefer or explicitly are against the usage of systemd suite of software, was pointing out systemd main reason of planning to propose an another standard, regardless if it will be popular or not)

[–] PoorPocketsMcNewHold@lemmy.ml 1 points 7 months ago (1 children)

When was the last time you had to edit sudo configuration file ? Same goes for doas. It's has nothing going for, for the majority of desktop Linux users (from what I got as an answer)

[–] PoorPocketsMcNewHold@lemmy.ml 3 points 7 months ago (5 children)

Speaking of doas, is there any advantage of using it when… sudo is still available to be used? I agree that most of the stuff we require to use doesn't need all the options sudo as, but if it is for the sake of security, maintenance, and stability… is there any reason to use doas ON TOP of the already setup sudo or su? In the past, I even tried to just apply a simple alias to replace sudo with doas, but numerous scripts and programs when trying to request explicit super-user permissions, just didn't know what to do with doas as expected, so this ain't it.

[–] PoorPocketsMcNewHold@lemmy.ml 3 points 7 months ago (1 children)

Okay, so it wasn't VNC, it was ssh stuff instead.

[–] PoorPocketsMcNewHold@lemmy.ml 15 points 7 months ago (4 children)

Similarly, there's System Admin Girl★まんがでわかるLinux シス管系女子 Imported a physical edition just for the quirky factor of a Linux Admin manga, but it is pretty well made and does explain pretty well some bits (even if from the first episode, they explain how to do VNC if i remember, from a Ubuntu 16.04 LTS desktop, so fairly easy and old) but it still on-going !

[–] PoorPocketsMcNewHold@lemmy.ml 8 points 10 months ago

Well, i believe in all showcased cases from people here, they are NOT replacing sudo entirely (Except if some are from BSD or if I'm incorrect with this assumption). They are just replacing their user habit with doas and use that command instead. In the end, all unix scripts or apps expect using sudo (If not, su) so... ### What's even the need to ?

  • Size : Installed on top of the already system present sudo.
  • Security : Only perhaps if you made a sudo alias to doas (But since it isn't entirely 1:1 identical, if anyone have a cleaner way of implementing that, I'm all hear)
  • Simplicity : You now have two tools. A easy to use keycard, and a key. The second is more complicated to use, so you use it rarely but it's still two tools instead of one.
  • Less dependencies : Again, unless you can actually replace it ENTIRELY, it's just an added tool (Still almost dependency free)

Really looking to corrections if i do some

[–] PoorPocketsMcNewHold@lemmy.ml 2 points 1 year ago* (last edited 1 year ago)

https://github.com/reMarkable/linux At that, there are ways to hack it of course (Fairly certain it “ruins” some returns/warranty policies, but if you can in those cases, you can easily revert the modified bits if needed)

tl;dr : if you want to try to hack it safely, heads up to : https://remarkable.guide/

If you would like to run a pre-made Debian chroot on it. Saw other distros from other users https://github.com/Eeems-Org/remarkable-debian-chroot

If you would like to use (Not fully replace for stability/recovery concerns) another launcher which is MIT licensed https://github.com/Eeems-Org/oxide

You can install the “vanilla” (minus extra bits) kernel via Toltec https://toltec-dev.org/stable/#section-launchers

Aaaand, if you want to go the full libre way, there's a port of parabola on it sold here http://www.davisr.me/projects/parabola-rm/ Article here https://hackaday.com/2020/09/06/a-free-software-os-for-the-remarkable-e-paper-tablet/

If you want something a little easier to install, and especially, allow fixing a couple of those issues safely, and automatically, you can try antidot .

xdg-ninja do already use the antidot rules natively, it's mostly for those who don't want to manually do the safest/easiest of fixes. It should be safe to use alongside xdg-ninja.