Keyoxide: aspe:keyoxide.org:KI5WYVI3WGWSIGMOKOOOGF4JAE (think PGP key but modern and easier to use)

  • 0 Posts
  • 176 Comments
Joined 3 years ago
cake
Cake day: June 18th, 2023

help-circle




  • There is some more complexity. Melee jetpack jumping is still a thing, but with more skill, you need a sort of double jump that eats jetpack like nothing and takes reach, then land on a fitting slope to launch. You’ll loose height and it ends when you hit ground, so aiming this well under those conditions feels really good. The longer the jumps the more efficient.

    There are also movement upgrades pairing with this you can select. Either just skipping it and going for run speed, or embracing it speccing into the jetpack.
    This also makes sure things don’t feel slow anymore down the progression no matter the specifics.









  • I cleaned it up. Your editor doesn’t like to nest formatting apparently. Using an editor that lets you write the markdown directly is probably better, and you are probably already familiar with markdown anyway, since it’s used all over the place.

    2025-07-09 “Sometimes, when one door closes (lack of code signing) in life, another one opens (vulnerability).”

    The sentence sumarizes well the situation in the previous version, 8.8.2.

    There were - and still are - many false-positives reported in the previous version v8.8.2, by the antivirus software due to the absence of Windows code signing certificate. How to install the root certificate:

    1. Double-click the certificate, it may tell you it’s invalid, ignore that and click: “Install Certificate…”.
    2. In the Certificate Import Wizard, select “Local Machine”, then click Next.
    3. If prompted by UAC (optional, depending on admin Previleges), click Yes.
    4. Choose “Place all certificates in the following store”, then browse and select “Trusted Root Certification Authorities”. Click Next.
    5. On the final page of the wizard, click Finish to complete the installation.For detailed instructions, see Notepad++ User Manual.

    We’re still trying to obtain a certificate issued by conventional Certificate Authorities, for a better user experience. But let’s be honest: it’s probably not happening. Notepad++ isn’t a business - it’s certainly not an enterprise - and apparently, that makes a popular open-source project invisible to their gatekeeping standards.

    If the “gatekeepers” won’t issue a certificate under the name we deserve - so be it. At least it spares us from wasting time and energy on a frustrting process that demands we beg for a new certificate every 3 years. The Notepad++ Root Certificate may not carry their approval, but it leads us to freedom.

    Edit (2025-12-03): Starting with v8.8.7, Notepad++ binaries - including the installer - are digitally signed using a legitimate certificate issued by GlobalSign. As a result, Installation of the Notepad++ root certificate is no longer required. We recommend that users who have previously installed the root certificate remove it.



  • The entire renewal process is fairly cheap, resource wise. 7 day certificates are already a thing.
    In terms of bandwidth you could easily renew a billion certificates a day over a gigabit connection, and in terms of performance I recon even without specialized hardware a single system could keep up with that, though that also depends on the signature algorithms employed in the future of course.

    The dependence on these servers is the far bigger problem I’d say.
    This shortening of lifetimes is a slow change, so I hope there will be solutions before it becomes an issue. Like keeping multiple copies of certificates alive with different providers, so the one in use can silently fall through when one provider stops working. Currently there are too few providers for my taste, that would have to improve for such a system to be viable.

    Maybe one day you’ll select a bundle of 5 certificate services with similar policies for creating your certificate the way you currently select a single one in certbot or acme.sh