Good Hello people of Slipmat! This week brings some long awaited upgrades to replace legacy v2 functionality.
Important! Due to migrating to a modern and secure authentication backend, you must create yourself a new password. If you were logged in, you’ll see a prompt that forces you to create one, or if you need to log in, you must reset your password. This is a one-time change due to v3 migration (and v2 security being over decade old).
Next we’ll focus on moving the domain over (current site becomes old.slipmat.io, the “next” domain will be set as the default). But for now, here’s all the things changes this week;
New Features
- The whole authentication flow is now fully migrated away from v2 platform. The social logins (via Apple and Google) are now also enabled; you can use either (with existing email) to sign in. You can manage the connections from your account page. (v2 feature parity)
- You can now manage your connected email adresses from the account page. This feature alone is a pretty big one and had to wait for the severance of v2 platform. (Note: any email tied to legacy account must be managed through that account. If you for some reason have used multiple accounts and want to add an email for your current account, you need to recover the old account first, then either change the primary email or delete the old account to free up the email to be used in another account.) (v2 feature parity)
- There’s now a full forgot/reset password flow for v3 accounts. (v2 feature parity)
- There’s now a page for changing your password. (v2 feature parity)
- The app now forces you to set a password. This is a security feature that allows you to recover your account in case you are unable to use your social account (or in case it gets disabled or deleted).
Enhancements
- The site templates for anon and authenticated users work much better now; similarily to v2, if you’re logged in, you’re automatically served the full app (no extra manual “open app” step), if you’re anonymous, you only see a generic page plus a login button.
- The music link converter library has been upgraded. The new version returns more correct conversion results and adds support for TIDAL links
- Artist: as a part of the artist profile data migration we analyzed your most used tags. Top-5 are now displayed on the event scheduling form as quick picks; instead of writing, you can just click to insert your most used tags to the event. (This will be improved soon so that you can define these yourself!
- The API deployment process has gotten a major upgrade. Previously each deployment would result in ~50s downtime where you couldn’t post chat messages or do basically anything. Now the downtime is near-zero which means that in normal circumstances you will never see any disruptions whatsoever even if bugfixes or new features are pushed mid live event. (Note that some deployments still force the browser to do a full refresh which ensures that it uses the latest version of Slipmat app.)
Bugfixes
- Artists: event scheduling form shows exactly the issue and reason if the scheduling fails instead of just generic “scheduling failed” error. Thanks to @urbanloveulcer for the report! (Typically this ever only happens if 1) you try to create an event with a slug that already exists, or 2) you try to schedule event starting in the past or less than 60 minutes from now.)
- 1Password autofills use now normal site styles so you are able to actually see what it autofilled.
- Fixed a dumb bug in static asset caching; everything is now cached for maximum amount of time instead of one day (duh!). Now you don’t need to reload everything daily
I’m excited about the next steps for Slipmat now that the new platform is slowly starting to take shape. This week was the last one of the hard migration steps