Post AXOX2OpjfNN7kLJJUu by kkarhan@mstdn.social
(DIR) More posts by kkarhan@mstdn.social
(DIR) Post #AXOX2O0KkUFtAvGGNU by gingerrroot@kitty.town
2023-07-03T21:45:05Z
0 likes, 0 repeats
every single streaming or storing device where you can purchase or browse things should have a “dont ever show me this again” buttoni dont want certain artists, movies, shows, games to ever be recommended to me by your bad algorithm and there should always be an option for it
(DIR) Post #AXOX2OpjfNN7kLJJUu by kkarhan@mstdn.social
2023-07-03T21:58:02Z
0 likes, 0 repeats
@gingerrroot AND this should not require any login at all, but at most a perpetual "dislike cookie" for said site.And yes I can totally understand why, because I've been there...Today was a record: I wished for that 6 times out 8 just on #YouTube's main website alone!https://mstdn.social/@kkarhan/110649459333905684
(DIR) Post #AXOX2PUrCUGVnsY9aq by gabri@tech.lgbt
2023-07-05T19:50:44Z
0 likes, 0 repeats
@kkarhan@gingerrroot Cookies are limited to 4 KiB of information so I guess the best we can do is let users have a cookie that points to a list of public URLs with the things they don't want to see. (kind alike linking to a paste bin)Now that I'm thinking about it, this feature sounds so useful it might be a good idea to standardise it somehow. Perhaps even with an IETF RFC.As for the file format itself, I think that some simple JSON thing is enough. (let me continue in another toot)
(DIR) Post #AXOX2QOVrYmiaUabLM by Jain@blob.cat
2023-07-05T20:05:16.853672Z
0 likes, 0 repeats
@gabri @kkarhan @gingerrroot nah thats a bad idea... basically there exists 2 situations:- the server sends the recommendations, then the server needs to know the full block list anyway- the client gets the recommendations, in this case just use the local storage for the block list...using cookies for storing a anti recommendation list just adds useless overhead and cookies are way more complex and designed to do other things than keeping userdata
(DIR) Post #AXOX2QokI1lhtqrYES by gabri@tech.lgbt
2023-07-05T19:55:01Z
0 likes, 0 repeats
@kkarhan@gingerrroot The file is a JSON array of dicts representing items to hide/block.Each item as keys for the various identifiers the item has (e.g. common name, full name, ISBN, URL, DOI, ISSN, etc.) and three special boolean keys named: "hideThis", "hideStuffByThis", "hideStuffAboutThis". So you still get recomended articles about say JK Rowling without getting recomended anything she made.The big implementation issue will be the fuzzy matching needed tho.
(DIR) Post #AXOX2V48UkSL4k5tmC by gingerrroot@kitty.town
2023-07-03T21:49:30Z
0 likes, 0 repeats
wanna know my fav thing about mastodons explore algorithm? it doesnt take into account blocks of users or instances so itll recommend people youve blocked or instances you blocked all the time.
(DIR) Post #AXOX2aftdmdETIncpM by gingerrroot@kitty.town
2023-07-03T21:52:43Z
0 likes, 0 repeats
isnt it great that, without extra complicated steps from the technical side, blocking means nothing?
(DIR) Post #AXOXE0zY8R29HHRJku by Jain@blob.cat
2023-07-05T20:07:26.784311Z
0 likes, 0 repeats
@gabri @gingerrroot @kkarhan also pointing to a arbitary url is also a very bad idea from a security perspective