I’d recommend Quad9 or Mullvad as both have a good record on privacy. DNS is also often unencrypted by default, so make sure to use DoT or DoH while you’re at it.
I’d recommend Quad9 or Mullvad as both have a good record on privacy. DNS is also often unencrypted by default, so make sure to use DoT or DoH while you’re at it.
This is insane. You want to send kids to the frontline? No? Then how is this going to help?
If your army needs more soldiers, maybe try a compulsory military service again. You don’t need to get little kids all excited about guns, the military and the possibility of war.
Look at those happy faces and sparkling eyes, they’re all feeling so strong while fantasizing about real combat and asking themselves if they would shoot someone. Horrible.
I’m not saying that we (speaking as a EU citizen) don’t need a strong military to defend ourselves, we definitly do. But teaching young children how to operate assault rifles is not the way, it’s dangerous symbolism at best and bleak warmongering at worst.
I’d say ask the original developer directly. Getting your changes merged upstream should be the preferred option for you, the original dev and the users. If everything goes right, you both could figure out a way to do this, maybe by re-introducing your refactorings and fixes one by one in smaller pull requests. Maybe you could become a maintainer in the process and support the original dev long term so everybody wins.
If the original developer doesn’t respond or declines you could think about bringing your own fork forward. Think about the consequences though, the original dev might get frustrated by a competing fork and abandon the project completely. The users on the other hand might be confused or insecure about which version to choose. Your fork must offer a lot for them to jump ship and switch.
Generally I’d say open source is about working together, not against one another, so just shoot them a message and see where it goes.