wldcordeiro

We've just had a file called `.rules` that is symlink as `AGENTS.md`, `CLAUDE.md`, etc to support the 3 or so common ones used around our projects.

I've been curious about using it but the fact it needs to upload everything makes it something I can't do with work and then don't see the immediate value of on projects by myself.

For what it's worth Liquipedia is sort of aimed at different people than the fandom wiki. Liquipedia has a very e-sports bend to its content so it may be that the ranks are skewed because the fandom wiki has more general purpose info about the game, lore, etc while Liquipedia has info about teams, matches, events, etc.

I think once you have it in Rust the next ask is using no "unsafe" code from that crowd.

heh reminds me how every app lets you report ads as "spam" still but in this day what is even the difference?

Reminds me of what Brasil did with Pix which of course the outside payment processors have been trying to undo.

blah blah blah justifications for gatekeeping.

What a completely rude comment that tells me everything I ever need about you and whether I'd want to interact with you. They're not asking for the literal answer. They're asking a question about why that is important to surface at all.

Absolutely, you're hitting the same conclusions I've reached. The algorithms are optimized for the lowest friction users that just replay the same music they like over and over again and accept whatever the popular music is. If you're a user that likes music discovery you're fighting against the system to get what you want.

I don't think the recommendation engines behind Spotify, Youtube Music, etc compare to the recommendations I got from last.fm over the years. The algorithmic ones seem to have a bunch of issues that bug me as a long time music listener and someone with a large music library.

- their memory is short as hell so you can listen to something for a while, stop and then it'll suggest it to you later as something to "discover"

- they are way too biased towards recently listened music and will replay things over and over if you're not actively managing your queues.

- because they're so based on what you have listened to (recently) they suggest things that are extremely obvious music no one is "discovering"

- they suggest the "top" songs from artists, albums, etc, it's very hard to get it to play a "deep cut"

- if you have a large library you'll inevitably hit playlist song limits and other things silently. Each service handles this differently, Youtube Music seemingly kicks things out of my library or liked playlists each time I add something else.

I've literally just gotten in the habit of never using the autoplay features and just starting whole albums from start to finish again because the algorithms annoy me so much. Youtube Music has been getting worse about it too where now it often ignores the music you chose to start a playlist and starts playing things you've listened to recently regardless of it doesn't match the genre/vibe at all.

I was wondering that too. They explained the differences between the tools but didn't really qualify which was doing things "right" just that they differed.

These days it's hard to tell and there's always a mix of both with any high demand items so it makes the stock limits even more pronounced. With how Valve has done hardware releases lately though I imagine it's more a stock limitation.

Yeah I can see that. I probably wouldn't be subscribing to issues that weren't feature requests/gaps very often. Ones that are tied to bugs are the only others that come to mind that I'd subscribe to but just thinking about my own dev experience in various jobs and how even there our internal backlogs of issues would have unclosed, out of date stuff, I think some portion of issues in public projects would be too.