api tokens?

[j-koziel]

[JudeDavis1]

👌

[j-koziel]

So I made the base model just now with some standard fields... if there are any other fields which you think people would need to provide to use this api

[JudeDavis1]

By User, do you mean API user (the engineer that is interfacing with it), or frontend user?

[j-koziel]

By User, do you mean API user (the engineer that is using it), or frontend user?

API user

[JudeDavis1]

Right. I also think that this may be useful for mCart because it can suggest scriptures to do with ministry, angels guiding us, etc. if you know what I mean.

If we can write an algo to index the scriptures, I can design a spicy ML algo to vectorize the scriptures and classify them based on topics. I can then display them on mCart as a 'featured' scripture or something.

[j-koziel]

Right. I also think that this may be useful for mCart because it can suggest scriptures to do with ministry, angels guiding us, etc. if you know what I mean.

If we can write an algo to index the scriptures, I can design a spicy ML algo to vectorize the scriptures and classify them based on topics. I can then display them on mCart as a 'featured' scripture or something.

good idea... now please explain what you mean by index the scriptures... I'm sorry to have to do this 😭💀

[JudeDavis1]

No problem at all. By indexing, I mean to categorize, or order (index) by topic (or at least a few). Then with the ML algorithm, we can classify by topic/relevance

[j-koziel]

No problem at all. By indexing, I mean to categorize, or order (index) by topic (or at least a few). Then with the ML algorithm, we can classify by topic/relevance

Cool, thanks for explaining 👌

[JudeDavis1]

And I removed the passwordConfirm because that is to be done on the frontend, not the backend. I left a note next to the commit.

[j-koziel]

No problem at all. By indexing, I mean to categorize, or order (index) by topic (or at least a few). Then with the ML algorithm, we can classify by topic/relevance

I know that mongodb actually has an indexing feature and you can use it to find documents quickly. Instead of looking through every single document to match a specific field mongo looks at the index and it only examines the necessary documents. This improves read performance for obvious reasons, but I wonder if the functionality extends further than read/write performance.

[JudeDavis1]

API tokens could be stores as part of a User model in mongoDB

[JudeDavis1]

stored*

[j-koziel]

Ok since I haven't really made any real progress for this in terms of commits and actual code im going to downgrade this to a discussion.

[j-koziel]

So I think I am going to end up making this use a database (rip databaseless architecture). I'm probably going to just do standard email, password data model for the users

[JudeDavis1]

So is there no API tokens, just vanilla email/username/password?

[j-koziel]

not exactly... so I was thinking in my head of what the front end would look like and I just decided that there would be a dashboard with stats and stuff. There each user could request a token.

[JudeDavis1]

What sort of stats?

[j-koziel]

how many times the token was used, resources used etc

[j-koziel]

by resources i mean api resources so how many times the person hit the "getVerse" endpoint

[JudeDavis1]

@j-koziel the tokens could be sha256