gosumemory VS mkcert

So, lately, I have been trying to get some QOL applications from GitHub for Osu! They are applications that seem very safe and many other people are using them with no problem, just me. (The two Github applications here, and here) Whenever I download the one for my system and open the application, it won't open. If I run the program as an administrator nothing, run it in cmd? nothing. The only thing is if I type it into the search bar, the icon pops up in my taskbar but then goes away. I can't figure it out. I don't feel like I should reach out to the developers of these programs because it's happening with multiple different programs not just one. If anyone knows how I could get the programs to open, that would be greatly appreiciated!

this is a known issue, fix is here

streamcompanion or gosumemory for pp counter (personally recommend streamcompanion)

use stable or the fixed build from this pr or wait for official fix

gosumemory

the only one i know of is https://github.com/l3lackShark/gosumemory but it isn't up to date with the latest rework

I use Gosumemory, I'm not 100% sure if it's updated since some top plays I set today and yesterday didn't 100% match with the pp value I got.

the overlay itself is private but the software is called gosumemory

For any streamers that have used gosumemory and Blondazz's KeyOverlay, keyoverlay-rs will be very familiar out-of-the-box.

The author mentions difficulties with HTTPS and trying stuff locally.

I've had some success with mkcert [1] to easily create certificates trusted by browsers, I can suggest to look into this. You are your own root CA, I think it can work without an internet connection.

[1] https://github.com/FiloSottile/mkcert/

Solution: mkcert – Your Zero-Configuration HTTPS Enabler Meet mkcert, a user-friendly, zero-configuration tool designed for creating locally-trusted development certificates. Find it on its GitHub page and follow the instructions tailored for your operating system. For Mac users employing Homebrew, simply execute the following commands in your terminal:

Well, Certifi does not ship with your company's certificates! So requesting internal services may come with additional painful extra steps! Also for a local development environment that uses mkcert for example!

My project, getlocalcert.net[1] may be the one you're thinking of.

Since I'm also building in this space, I'll give my perspective. Local certificate generation is complicated. If you spend the time, you can figure it out, but it's begging for a simpler solution. You can use tools like mkcert[2] for anything that's local to your machine. However, if you're already using ACME in production, maybe you'd prefer to use ACME locally? I think that's what Anchor offers, a unified approach.

There's a couple references in the Anchor blog about solving the distribution problem by building better tooling[3]. I'm eager to learn more, that's a tough nut to crack. My theory for getlocalcert is that the distribution problem is too difficult (for me) to solve, so I layer the tool on top of Let's Encrypt certificates instead. The end result for both tools is a trusted TLS certificate issued via ACME automation.

1. https://news.ycombinator.com/item?id=36674224

2. https://github.com/FiloSottile/mkcert

3. https://blog.anchor.dev/the-acme-gap-introducing-anchor-part...

Looks like step-ca/step-cli [1] and mkcert [2] have been mentioned. Another related tool is XCA [3] - a gui tool to manage CAs and server/client TLS certificates. It takes off some of the tedium in using openssl cli directly. It also stores the certs and keys in an encrypted database. It doesn't solve the problem of getting the root CA certificate into the system store or of hosting the revocation list. I use XCA to create and store the root CA. Intermediate CAs signed with it are passed to other issuers like vault and step-issuer.

[1] https://smallstep.com/docs/step-ca/

[2] https://github.com/FiloSottile/mkcert

[3] https://hohnstaedt.de/xca/

We use mkcert for this, it works wonderfully.

https://github.com/FiloSottile/mkcert

mkcert: This is used to obtain a trusted TLS certificate with a custom domain name for your development machine. You can install mkcert on your development machine following the official instructions.