3 ms·

On one hand I am thinking about what a very basic algorithm would like (maybe even just categories I might do) and maybe how it would make people happy. On the

by aizk 2y ago

On one hand I am thinking about what a very basic algorithm would like (maybe even just categories I might do) and maybe how it would make people happy. On the other hand, I'm not sure exactly the details of wikipedia's api TOS. Also as it stands this website is entirely in the frontend at the moment, and I'm enjoying just scaffolding out what I can with limited a more limited set of tools to speak. I realize now the suffix "tok" implies a crazy ML algo that is trained every single movement, click, tap, and pause you make, but I don't think I really want that.

codingdave 2y ago
It should be possible to keep this all front-end, even with some basic algorithm for the searches - just use localStorage. That keep things simple and resolve privacy concerns, as people own their data and can delete them any time.
keerthiko 2y ago
browser-store and cookies, among other tools, provide nice front-end-only persistent storage for holding things like recommendation weights/scoring matrices. maybe a simple algorithm that can evaluate down from a few bytes stored in weights might be all the more elegant.
layman51 2y ago
About the “Tok” suffix, I also think that while it has the algorithm connotations, it also has been used a lot to describe communities that have formed on TikTok. For example, BookTok (where some bookstores have started to pay attention to how people on TikTok can make some books popular again seemingly on a whim) or WitchTok.
- l3x4ur1n 2y ago
  StickTok where people show cool sticks they found in the nature!
aizk 2y ago
Update - I chatted with some devs at wikipedia, and they confirmed I'm not hitting their servers hard, which is great.
- Aeolun 2y ago
  Compared to default wikipedia traffic this should be a drop in a bucket right?
  - aizk 2y ago
    Probably? I have no frame of reference, I've never done giant distributed systems before. I just noticed that earlier version had some slowdowns but I think I was just improperly fetching the images ahead of time.
  - deleted 2y ago
    [deleted]
valec 2y ago
keep user profiles maybe with cookies or by encouraging sign-ups and then use NMF https://en.wikipedia.org/wiki/Non-negative_matrix_factorization https://en.wikipedia.org/wiki/Non-negative_matrix_factorizat...
bawolff 2y ago
> On the other hand, I'm not sure exactly the details of wikipedia's api TOS https://www.mediawiki.org/wiki/API:Etiquette https://www.mediawiki.org/wiki/API:Etiquette You are basically allowed to do whatever as long as it doesn't cause an operational issue, you dont have too many requests in-flight at one time , and you put contact info in the user-agent or Api-User-Agent header. (Adding a unique api-user-agent header is probably the most important requirement, since if it does cause problems it lets operations team easily see what is happening) I think the wiktok thing is exactly the sort of thing wikimedia folks hope people will use the api to create.

by aizk 2y ago

codingdave 2y ago

It should be possible to keep this all front-end, even with some basic algorithm for the searches - just use localStorage. That keep things simple and resolve privacy concerns, as people own their data and can delete them any time.

keerthiko 2y ago

browser-store and cookies, among other tools, provide nice front-end-only persistent storage for holding things like recommendation weights/scoring matrices. maybe a simple algorithm that can evaluate down from a few bytes stored in weights might be all the more elegant.

layman51 2y ago

About the “Tok” suffix, I also think that while it has the algorithm connotations, it also has been used a lot to describe communities that have formed on TikTok. For example, BookTok (where some bookstores have started to pay attention to how people on TikTok can make some books popular again seemingly on a whim) or WitchTok.

l3x4ur1n 2y ago
StickTok where people show cool sticks they found in the nature!

aizk 2y ago

Update - I chatted with some devs at wikipedia, and they confirmed I'm not hitting their servers hard, which is great.

Aeolun 2y ago
Compared to default wikipedia traffic this should be a drop in a bucket right?
- aizk 2y ago
  Probably? I have no frame of reference, I've never done giant distributed systems before. I just noticed that earlier version had some slowdowns but I think I was just improperly fetching the images ahead of time.
- deleted 2y ago
  [deleted]

valec 2y ago

keep user profiles maybe with cookies or by encouraging sign-ups and then use NMF https://en.wikipedia.org/wiki/Non-negative_matrix_factorization https://en.wikipedia.org/wiki/Non-negative_matrix_factorizat...

bawolff 2y ago

> On the other hand, I'm not sure exactly the details of wikipedia's api TOS https://www.mediawiki.org/wiki/API:Etiquette https://www.mediawiki.org/wiki/API:Etiquette You are basically allowed to do whatever as long as it doesn't cause an operational issue, you dont have too many requests in-flight at one time , and you put contact info in the user-agent or Api-User-Agent header. (Adding a unique api-user-agent header is probably the most important requirement, since if it does cause problems it lets operations team easily see what is happening) I think the wiktok thing is exactly the sort of thing wikimedia folks hope people will use the api to create.