A quick question: I don’t vote on bug requests because I assumed you’d work on them based on how quickly/easily they could be fixed, which are the most important to rectify, etc. But is it worth voting on bugs? Would it be helpful to show how much it impacts user experience?
The main problem with the votes is the turnaround right now is not that good.ç
Brandon has been busy with big tasks/features, so they languish for a long time.
Having a big number of votes to vote each user also kinda defeats the point, as you could vote anything that seems useful, instead of giving a priority to the ones you want the most.
Is a bit of a balance game to play.
I’ve increased the number of votes. It’s not infinite, but it’s near double what you had before.
It’d be nice to have the game and maybe that is the more appropriate way to play it… but tbh, I don’t think the mechanism is super well tuned. A lot of these votes depend on when something is ‘bumped’ in the forums. And decreasing the number of votes you have also has warts too. If you only had 5 votes for instance, perhaps the only items that would get voted on would be major value adds like Content Tags / Rereads, even though there are things of other value too.
Anyway, I’m not sure i’ll ever keep up with the request volume (life of a dev…), but there are quite a few highly voted small tickets I should really knock out.
This category will serve as a general category for people who want to interact with the broader language community. I ended up naming it ‘All Languages’ rather than ‘Language Learning’ or ‘General’, simply to emphasize that this category contains the same types of topics as the top level ‘Japanese’ or ‘Korean’ categories… just for everyone / multilingual.
If people prefer a different name, I’m all ears!
Also, you will note that there are now more tags in the language categories which everyone can apply (learning-log, resource). We can add to these tags as we see fit. The All Language category additionally has ‘korean’ & ‘japanese’ as tags… but more languages are welcome.
Right now, I’ve included the ‘All Languages’ category into your Natively Dashboard feed, but this will change as we get to have a larger multilingual community.
I worry you’ll end up with duplicate topics in All Languages that are also in the individual language categories, scattering conversation in confusing ways. Guess we’ll see.
One thing from the request topic I want to respond to though:
Is there a reason to have the learning log topics in All Languages given that users can still unmute or visit other language categories?
Those should both be “2 hours ago,” and in fact 20 hrs ago would be 11 p.m. last night in my time zone, though it is properly marked as being finished today, 8/11. When I didn’t see it under Global, I thought for some reason it just wasn’t showing up, but…
Interesting. So it looks like you manually set the date finished, which puts it as finished at 00:00:00 on 8/11 (really we only store the date 8/11/2023, but for activities we treat it as 00:00:00).
If you simply let the auto process mark it finished, then we use the exact time it was marked finished.
In general, we still need to implement timezones, would really solve a lot of these issues.