KeePass2.x VS Leaflet

And the best part is there are solutions already that do this: https://keepass.info/

Does it work on Android or iOS?

The key difference here being that this is two way hashing so passwords can be decrypted.

In reality, there are a lot of attack vectors like MITM, event logging or sometimes straight up storing data in plaintext. Through these hackers can generally get passwords of all users of these services.

So, why don't people use local password managers?

Just a txt file encrypted with "master password" should be pretty damning to break into. And the reward for breaking in would be password for 1 person. (compared to 100k businesses).

Obviously, this would be less convinient and wouldn't sync between devices. But would do the job.

And the best part is there are solutions already that do this: https://keepass.info/

So, why do people and companies use Okta etc?

When you're at a point where you're relying on a display name to make security-critical decisions, you've already lost.

Character substitutions like ķeepass or ƙeepass or keypass are at least possible to spot if you know the name of the product, but not the full URL.

But there are many ways to create lookalike domains that don't change the product name: https://keepass.org https://keepass.net https://keepass.info https://keepass.cx https://keepassxc.org https://keepass-info.net https://keepass-manager.com

Which of these is the correct one? (It's https://keepassxc.org of course, but just looking at the URL won't tell you that.)

The root cause is downloading software you see advertised on Google even though that does not in any way establish trustworthiness.

> People love to hate on passwords but the reality is that for many circumstances (threat models) they are the best compromise. You can make them more than strong enough (take 32+ bytes out of /dev/random and encode however you like, nobody will ever brute force that in this universe) and various passwords managers solve the problem of re-use (never reuse a password).

> And it comes with the benefit that you control how it is stored and can apply as much redundancy as you want to feel comfortable.

Honestly, I agree! I used KeePass back in the day (https://keepass.info/) but now use KeePassXC (https://keepassxc.org/) and it's really nice - I don't know any of my passwords because they're all randomly generated and are pretty secure. The only one I have to remember is my main password for decrypting the safe, which I also wrote down and entrusted to someone close to me due to its complexity.

It honestly works great, software to interact with the password safe is on every platform where I need it to be, in addition to it being super easy to reason about storage, because it's basically just a file - that I can then put on self-hosted Nextcloud, or another solution like that, or USB sticks or burn to CDs for all I care.

Maybe I should also migrate all of my TOTP stuff over to it and look into good Android apps at some point, then I wouldn't quite need Google Authenticator or FreeOTP anymore, either.

If you have used this combo at many sites (which is of course not recommended) then download one of the available free Password Managers like Keepass, Bitwarden, Lastpass or any others you can find with a Google Search

I also tried out KeePass for a little bit but prefer the BitWarden apps. The key thing here is don't store your passwords in the cloud as they are massive target for hackers.

Best KeePass Windows desktop client: KeePass

If though you can't stand the idea of your password vault on a 3rd party server then you can use an offline password manager like KeePass. Of course, you have to take responsibility for making and storing backups of your vault in case something happens to your device. Fortunately, Syncthing can make this pretty trivial.

If you can't stomach the thought of your password vault stored on a 3rd party server then I recommend KeePass which is a free open-source offline password manager. The key here is that you should back up the database. Perhaps putting a copy of it on your laptop/PC, your phone, and USB Key (probably 2, one you keep local and update periodically to swap with a second stored in a safety deposit box or trusted friend/family member). You can also use the open-source Syncthing to keep your database in sync across devices (thus creating automatically updated backups). I know some recommend putting the database on a cloud storage service to sync across devices, which is fine but in my opinion, if you are going to do that you might as well use Bitwarden or other reputable online password manager.

Why's that? If the issue is that you don't want to trust anyone else with your passwords, you can use an offline password manager (e.g. KeePass). Then all your passwords are only in one encrypted file, and you have full control over who has access to it.

9. Leaflet

Leaflet is the most famous open-source map library, with lots of plugins. 2 of them are used to animate a marker on the map:

Leaflet seamlessly integrates into web applications either directly from npm or through a CDN.

Leaflet stands out as one of the top open source JavaScript libraries for crafting interactive maps. Optimized for both mobile and web devices, it is relatively small (around 42KB) and offers a ton of features, plugins, and a straightforward API. It works across all browsers and platforms.

Finding maplibre 'better' was more valid at the time than today, and is also subjective. The creators and maintainers of both libraries have done some great work (and are still doing so).

Back in January 2022, the stable version of leaflet, v1.7.1, was from September 2020, and was affected by some small bugs degrading the user experience. Although the release of following version seemed close, there was no clear schedule for it, and I had concerns about how maintained the library would remain.

As of today, the bug from 2015 where there is some white space between map tiles on fractional zoom levels [0] is still open.

Also, leaflet was a pain to integrate in Svelte Kit framework, because it depended on `window` and-or `document`, not available at server side.

Maplibre, on the other hands, with a feature set roughly equivalent to Leaflet, benefited from much more frequent releases, and seemed more stable across browsers and devices. It was also easier to make it work in Svelte kit.

[0]: https://github.com/Leaflet/Leaflet/issues/3575

For a personal project, I had to use Leaflet with Svelte, and I faced some problems during development.

Official Website: https://leafletjs.com/

You might wanna check out Leaflet (https://leafletjs.com/) which is a free, open-source library for interactive maps. Combine that with React-Leaflet (https://react-leaflet.js.org/) for seamless React integration. You can find Pond/Lake GeoJSON data at https://gis.mass.gov/ and load it into your map to make it interactive. Good luck!

leaflet was pretty sweet to work with. I'll also recommend if you end up adding JS maps to any live pages.