semperverus

joined 2 years ago
[–] semperverus@lemmy.world 7 points 4 hours ago

I like your funny words, magic man

[–] semperverus@lemmy.world 1 points 4 hours ago

And you can ban porn off the internet to varying degrees of success, but the sneakernet is unstoppable.

[–] semperverus@lemmy.world 4 points 4 hours ago

There are plenty of misogynistic women, being a man and agreeing with something doesnt make it not misandric

[–] semperverus@lemmy.world 2 points 5 hours ago

I think you're missing the point. What you said is a problem for sure, but that problem isn't related to what we are talking about here.

[–] semperverus@lemmy.world 0 points 1 day ago* (last edited 1 day ago) (1 children)

Just because one systemd dev prepared something to be optionally used for a stupid law, doesn't mean anyone using Linux is forced to do that Seems you don't know how anything on Linux, and it's ecosystem, works, if you believe that

This is disingenuous at best.

Sure, its 'just' a single text field that 'optionally' can be used. until it isn't.

SystemD itself is a perfect example of this. Sure you have choice in theory, but in practice its a wildly different story. Name one mainstream Linux distro that can be used for casual day to day use, ranging from doing taxes to playing Steam games that does not use SystemD.

A lot of people drew issue with SystemD when it came out and as time progressed, but the number of fully supported core distros that do not use SystemD is zero.

Nobody's concerns were considered, and not one uses Runit, InitRC, or even just refused to move on from SysVInit, unless you count Gentoo. Debian is SystemD. Arch is SystemD. Fedora is SystemD. And so are almost all their derivatives.

In order to get away from SystemD, you have to switch to forks that intentionally go out of their way to make it happen like Artix. Arch's wiki page literally tells you that you can have any init system as long as it's SystemD.

You are left to rewrite entire core system components yourself and maintain them if you really want to make it happen.

So yea, you technically have a choice, but not really.

[–] semperverus@lemmy.world 4 points 1 day ago

Yep! Using it now on my Android phone via GameNative (which is GPLv3 licensed so you know it's good 👌🏻).

They don't have an F-Droid release yet but you can install via Obtainium or downloading it directly. Their github URL is: https://github.com/utkarshdalal/GameNative

[–] semperverus@lemmy.world 0 points 1 day ago

I get your sentiment but I think you meant LineageOS and not Graphene. I'm running Graphene now but there is only a small handful of supported devices due to its strict security hardware requirements that most phones don't meet.

The next best alternative (and technically the big dog in the room) is LineageOS. Preferably with no google-play-services.

[–] semperverus@lemmy.world 3 points 2 days ago (1 children)

Is this true if you don't have Google Play Services but the person you're messaging does? Is one person cutting GPS out enough?

[–] semperverus@lemmy.world 2 points 5 days ago

Smiling Friends

[–] semperverus@lemmy.world 16 points 5 days ago (1 children)

Which they did.

[–] semperverus@lemmy.world 2 points 1 week ago

Underneath the disc, gotta keep 'em stored in a dark cool place for preservation.

 
1
submitted 1 year ago* (last edited 1 year ago) by semperverus@lemmy.world to c/linux@lemmy.ml
 

The Linux Ship of Theseus

  1. pick any distro and install it.

  2. Then, without installing another distro over the top of it, slowly convert it into another distro by replacing package managers, installed packages, and configurations.

System must be usable and fully native to the new distro (all old packages replaced with new ones).

No flatpaks, avoid snaps where physically possible, native packages only.

EDIT: Some clarification on some of the clever tools brought up here:

chroot, dd, debootstrap, and partition editors that allow you to install the new system in an empty container or blanket-overwrite the old system go against the spirit of this challenge.

These are very useful and valid tools under a normal context and I strongly recommend learning them.

You can use them if you prefer, but The ship of Theseus was replaced one board at a time. We are trying to avoid dropping a new ship in the harbor and tugging the old one out.

It may however be a good idea to use them to test out the target system in a safe environment as you perform the migration back in the real root, so you have a reference to go by.


Easy: pick two similar distros, such as Ubuntu and Debian or Manjaro and Arch and go from the base to the derivative.

Medium: Same as easy but go from the derivative to the base.

Hard: Pick two disparate distros like Debian and Artix and go from one to the other.

Nightmare: Make a self-compiled distro your target.

 

Additionally, it appears that the code for the backend server is intended to be public as well, but just doesn't exist outside of a readme.md document in the main branch.

This is setting off sirens, particularly the lack of a license.

 

If you would like to contribute, please consider making a fork of the repo and updating the language strings for your native language. Take care not to change the actual variable names (i.e. leave the word "reddit" and "subreddit" in the variable tags, but change the actual string values).

The languages are available in this folder here, in the various values-... folders:

https://github.com/bqv/slide/tree/lemmy/app/src/main/res

If you'd like to see my commit as an example of what I did to base yours off of, you can see it here:

https://github.com/bqv/slide/pull/2/commits/f346de0ef40b3fb87a9d420d969f2f16edc874a5

view more: next ›