Full time work: week 2 update
Published on September 24, 2023 by yayuyokitano
Greetings again!
Week 2 is now up. In good news, we are on very good track! Of the goals laid out in the beginning of the month, we are almost done implementing everything! The following period will mostly be polishing things up, fixing bugs, and getting things ready for release, and then if I'm being a bit ambitious, I think we might get back to you next week to talk about more things to do for the remainder of the month. However, don't take this as a promise.
For the time use this week:
Scrobble Cache: 15:35:18
Create discord rich presence: 6:21:30
Overhaul login UX: 3:48:49
Code Review: 3:30:14
Documentation: 2:48:46
Improve CI: 2:20:29
Other: 1:49:23
Improve Webhook: 0:57:24
Core Development: 0:26:24
Exploring Issues: 0:15:59
Total time (excluding breaks): 37:54:16
Once again I have also done a little bit of untracked work responding to reviews, talking about our progression and discussing things in our discord and on github, committing merges, and doing other small things like that.
Scrobble Cache: The core of this is mostly implemented, which was way faster than anticipated. There are some more features left to implement, but the core functionality is functional, and seems to be pretty stable.
Create discord rich presence: This time has gone to fixing various little bugs here and there, improving code, and improving UX. The discord RPC feels done now, and will almost certainly be released along with the next version of Web Scrobbler.
Overhaul login UX: Various changes have been implemented here, to give better feedback and to generally make things smoother and easier to understand. There is still some work left to be done.
Code Review: This week we have landed a lot of things that were started last week, which has meant some more time spent reviewing. Additionally, the infobox PR has been finished up and merged (Thank you Wigger Boelens for doing the absolute bulk of the work on that). This adds a user-toggleable info box to the DOM that shows what a track will scrobble as.
Documentation: A lot of work was done on the wiki. A page was created explaining the new webhook API. Additionally, the connectors API changes page was finally updated for the first time in three years and is now fully up to date.
Improve CI: We have successfully updated and put our shared ESLint config to use. It has already caught one bug from the infobox PR that was not caught by the previous CI nor manual review, so it's already paying off! The stylelint config is merged and getting ready to be put into use on the main repo, probably over the next couple of days. After that, I think work on this will be done for now.
Other: Most of this time was spent consolidating some of our configs and documents to a new web-scrobbler/.github repo, so it applies to all of our repositories. Recently, we have added the rich presence repo, and plan to add some new repos (notably, I personally made and own the repo we use to publish to Firefox, and Malachi Soord personally made and owns the repo we use to publish to Edge. For future stability, we want to move both of these to the organization in the future.) As such, it has become more important that we create a more standardized environment across the entire organization, rather than focusing exclusively on the main web scrobbler repository. In the process, we also updated our code of conduct (it is fundamentally an extremely similar code of conduct, we just updated to a newer version of the same code of conduct basically.) Additionally, we have added a README that shows on the web scrobbler organization page (the README content itself is very much a WIP.)
Improve Webhook: We have just made some various small changes here for a better user experience logging in. Additionally, a time field has been added which helps servers sort requests, as requests don't necessarily arrive in the same order they are sent.
Core development: This were just some minor improvements to our regex matching.
As a quick recap, here is the list of things we laid out in the beginning of this month, and our progress on them:
[x] Recover after updates - seems to be finished, awaiting merge after a little more testing, but probably no more code goes into this as it seems very stable at this point.
[/] Fix CI to be stricter and more consistent - very nearly done.
[/] Improve login UX - almost done, with the functionality changes already finished. Only one or two exclusively UI-based changes remaining.
[x] Create an official discord rich presence utility - done.
[/] Add scrobble caching - core functionality done, only a couple extra convenience features and polish remaining. What is implemented seems to be very stable from my testing.
[/] Create a separate popup state for tracks skipped because of settings such as not scrobbling podcasts, not scrobbling anything except music category, etc. - Done and merged, but with some more testing and polish to be done before the next update is released, as there seems to be some flakiness especially on youtube.
Once again, thank you for your support, I hope this has been clear enough, and if not (or if there's anything else you're curious about), feel free to ask any questions you may have on here or on our discord server!
Week 2 is now up. In good news, we are on very good track! Of the goals laid out in the beginning of the month, we are almost done implementing everything! The following period will mostly be polishing things up, fixing bugs, and getting things ready for release, and then if I'm being a bit ambitious, I think we might get back to you next week to talk about more things to do for the remainder of the month. However, don't take this as a promise.
For the time use this week:
Scrobble Cache: 15:35:18
Create discord rich presence: 6:21:30
Overhaul login UX: 3:48:49
Code Review: 3:30:14
Documentation: 2:48:46
Improve CI: 2:20:29
Other: 1:49:23
Improve Webhook: 0:57:24
Core Development: 0:26:24
Exploring Issues: 0:15:59
Total time (excluding breaks): 37:54:16
Once again I have also done a little bit of untracked work responding to reviews, talking about our progression and discussing things in our discord and on github, committing merges, and doing other small things like that.
Scrobble Cache: The core of this is mostly implemented, which was way faster than anticipated. There are some more features left to implement, but the core functionality is functional, and seems to be pretty stable.
Create discord rich presence: This time has gone to fixing various little bugs here and there, improving code, and improving UX. The discord RPC feels done now, and will almost certainly be released along with the next version of Web Scrobbler.
Overhaul login UX: Various changes have been implemented here, to give better feedback and to generally make things smoother and easier to understand. There is still some work left to be done.
Code Review: This week we have landed a lot of things that were started last week, which has meant some more time spent reviewing. Additionally, the infobox PR has been finished up and merged (Thank you Wigger Boelens for doing the absolute bulk of the work on that). This adds a user-toggleable info box to the DOM that shows what a track will scrobble as.
Documentation: A lot of work was done on the wiki. A page was created explaining the new webhook API. Additionally, the connectors API changes page was finally updated for the first time in three years and is now fully up to date.
Improve CI: We have successfully updated and put our shared ESLint config to use. It has already caught one bug from the infobox PR that was not caught by the previous CI nor manual review, so it's already paying off! The stylelint config is merged and getting ready to be put into use on the main repo, probably over the next couple of days. After that, I think work on this will be done for now.
Other: Most of this time was spent consolidating some of our configs and documents to a new web-scrobbler/.github repo, so it applies to all of our repositories. Recently, we have added the rich presence repo, and plan to add some new repos (notably, I personally made and own the repo we use to publish to Firefox, and Malachi Soord personally made and owns the repo we use to publish to Edge. For future stability, we want to move both of these to the organization in the future.) As such, it has become more important that we create a more standardized environment across the entire organization, rather than focusing exclusively on the main web scrobbler repository. In the process, we also updated our code of conduct (it is fundamentally an extremely similar code of conduct, we just updated to a newer version of the same code of conduct basically.) Additionally, we have added a README that shows on the web scrobbler organization page (the README content itself is very much a WIP.)
Improve Webhook: We have just made some various small changes here for a better user experience logging in. Additionally, a time field has been added which helps servers sort requests, as requests don't necessarily arrive in the same order they are sent.
Core development: This were just some minor improvements to our regex matching.
As a quick recap, here is the list of things we laid out in the beginning of this month, and our progress on them:
[x] Recover after updates - seems to be finished, awaiting merge after a little more testing, but probably no more code goes into this as it seems very stable at this point.
[/] Fix CI to be stricter and more consistent - very nearly done.
[/] Improve login UX - almost done, with the functionality changes already finished. Only one or two exclusively UI-based changes remaining.
[x] Create an official discord rich presence utility - done.
[/] Add scrobble caching - core functionality done, only a couple extra convenience features and polish remaining. What is implemented seems to be very stable from my testing.
[/] Create a separate popup state for tracks skipped because of settings such as not scrobbling podcasts, not scrobbling anything except music category, etc. - Done and merged, but with some more testing and polish to be done before the next update is released, as there seems to be some flakiness especially on youtube.
Once again, thank you for your support, I hope this has been clear enough, and if not (or if there's anything else you're curious about), feel free to ask any questions you may have on here or on our discord server!
🚀 1