Random Ramblings

[HarlemSquirrel]

👋 Welcome!

We’re using Discussions as a place to connect with other members of our community. We hope that you:

• Ask questions you’re wondering about.
• Share ideas.
• Engage with other community members.
• Welcome others and are open-minded. Remember that this is a community we
  build together 💪.

To get started, comment below with an introduction of yourself and tell us about what you do with this community.

[HarlemSquirrel]

@Aetherinox @antelle I enabled discussions so we don't have to keep chatting on that PR 😁

[Aetherinox]

Nice. Sorry, right now I've been fighting with Google Cloud Services. The API key for the local environment kept coming back that it was invalid; so I had to register an app so that I could get an API key that worked.

Now I'm looking into Microsoft Teams because that seems to be a large issue as well.

[HarlemSquirrel]

Thanks for tackling these!

[Aetherinox]

No problem, I enjoy it.

This Microsoft Teams one is a pain. I don't want to bother antelle and get the proper configuration, but I'm currently looking for the correct redirectURL required by Microsoft Azure. Since this is a desktop app, there should be no need to redirect to the keeweb.info website. Not unless it's supposed to be https://localhost.

I deal with Google's Cloud portal, I've never messed with an Azure app. So it's making my brain hurt.

Edit: My comment gave me an idea, to try localhost, and that got me somewhere

http://localhost:8085/oauth-result/msteams.html

But that begs the question; what happens if the user changes the port? Or what about running a docker container and it using port 443.

Edit 2: Ok, well luckily the Microsoft documentation states

Due to ephemeral port ranges often required by native applications, the port component (for example, :5001 or :443) is ignored for the purposes of matching a redirect URI. As a result, all of these URIs are considered equivalent:

So that solves that issue, but the other issue is the official keeweb.info website. You're not allowed to have dissimilar TLDs, so if I use localhost as the TLD, all of them have to use localhost. If I put keeweb.info in there, it throws an error about it not matching the other results.

But some of their docs make no sense, because it says that using 127.0.0.1 is preferred, but if I use that, MS complains that it's not a valid address. It also says wildcards are allowed, but then the validation checker says "Do not use wildcards".

[antelle]

For Dropbox we have:

For teams we have three different apps: local, prod, desktop, with different redirect URI’s.

[HarlemSquirrel]

GitHub also has a merge queue feature. I tied it on another project but it doesn't have high enough traffic to really see the benefits.

[HarlemSquirrel]

Ugh. I've set up OAuth and SAML on several platforms but if there's no official documentation on this that may mean it's not really supported and anything we get working could break at any time

[Aetherinox]

I can already tell that me and Prettify are going to have issues.

I have a certain style I'm used to writing code, and prettify blocks me from doing anything. I had to switch over to pushing on my dev repo, because I'm six commits in on the same exact code, and it's complaining about spaces. Had to go install eslint for vscode.

[HarlemSquirrel]

I added a command to auto fix lints on my node 18 branch

1c5adfc

[Aetherinox]

It's a little easier now that I have eslinter in Visual Studio Code. I don't have to guess what the heck it means.

Bigger update incoming sometime soon. Fixing bugs, adding a few new features.

Working on passphrase implementation as well like how KeePassXC has it.

Adding "Spaces" was an interesting task.

Because if you just add a space within the "include" values; it throws spaces for like every other letter, depending on the number of character types you have. So I had to do some logic so that it's a little smart about how spaces are distributed. Plus ensuring that spaces are distributed randomly, and there's no pattern to how they're added.

There's a mountain of stuff to modify / update / etc. But I wanted to at least add a few minor things to get development going again so users have at least something fresh until we can do things like migrate to react.

Passphrases needs some adjustments, because you should be able to change the length without it resetting back to a normal password.

There's a lot of settings I can do, but the interface needs to be re-worked a bit to allow for such settings.

[Aetherinox]

We're making progress