go-email-normalizer VS scs

The reason that I use "go-email-normalizer" as "emailnormalizer" is entirely unrelated to the url it's at or the name of the repo it's in. The only reason you use "emailnormalizer" is because that's the package line in all the files in that package: https://github.com/dimuska139/go-email-normalizer/blob/0432b...

Importing a go package will add an arbitrary identifier to the file scope, and you can't know that identifier without reading the package statement of the package you imported.

Although there are pretty good session managers in the Go ecosystem such as alexedwards/scs, golangcollege/session and gorilla/sessions, we won't use any but using this great guide, we'll write our own. This is to keep our project's dependence on external packages at the barest minimum.

github.com/alexedwards/scs is quite pleasant to work with.

This one works ok: https://github.com/alexedwards/scs

I'm a big fan of Alex Edwards' book "Let's Go", and he uses his own Sessions library: https://github.com/alexedwards/scs which you can find in the Authentication section of Awesome Go. So that's a great source as well.

Server side sessions using alexedwards/scs.

Unfortunately I haven't written a cookie/session based auth flow in Golang before so can't recommend any libraries. A quick google led me to https://github.com/alexedwards/scs which may or may not be helpful.