Hello everyone! Catching up on a million messages on the plane. Feeling relaxed and tanned 😎😎😎 Awesome MB release this week tīma!!
reosarevok: MBS-13698 makes sense to me, I sometimes find the buttons confusing too. That whole page could use a bit of work, I think it's in a different ticket somewhere... But tackling that would def help
Ah zas mentioned it too, agreed that drag and drop would be great. I think I made a mockup once? Internet is too slow to search for a ticket on my phone sorry
rimskii: I drafted a shorter playlist description for LB-1599. Maybe monkey wants to have a look and check it too? I'm not sure who wrote the original description
<aerozol[m]> "rimskii: I drafted a shorter..." <- thanks! it looks legit to me. should we completely change the description or just modify it for exporting?
zas[m] has quit
lucifer: it seems that apple doesn't allow modification or deletion of tracks/ playlists. meaning we cant change playlist titles/desc or remove tracks; we can only add new ones. this poses some issues with exports, as I'm unsure how to handle this ;( Should we stick with just creating new playlists instead of modifying the existing ones? what should we do about unplayable tracks
as one way we can keep with just creating new playlists, and check unplayable tracks before submission (just see whether apple_music_ids match with lookup ids)
lucifer[m]
rimskii: yes, creating a new one sounds fine.
rimskii[m]
ok, great!
What about the unplayable tracks?
lucifer[m]
rimskii: you can ignore that for now
aerozol[m]
Hey rimskii! I think the playlist descriptions could use some editing down anyway so I am also fine with replacing it. But I don't know who wrote it
Might have been like that for a reason, I tried to keep all the elements there though, in the edit
rimskii[m]
<aerozol[m]> "Might have been like that for..." <- yeah seems fine for me too
let’s wait for monkey opinion then
monkey[m]
I say edit it, the new one is better
pite joined the channel
pite has quit
zas, atj : Some users have reported that since last September they can't submit anything to ListenBrainz from Android 7 devices because of a LetsEncrypt certificate issue (newer P-384 elliptic curve is not supported).... (full message at <https://matrix.chatbrainz.org/_matrix/media/v3/...>)
Well, Android 7 is now (very) old, and we're quite conservative already when it comes to SSL & certificates. I'll have a look at the issue though.
monkey[m]
Thank you!
atj[m] joined the channel
atj[m]
AFAICS there's no solution aside from switching away from LE, which I don't think is really feasible.
Android 7 went EOL nearly 5 years ago.
Not that I'm a particular fan of Google's approach to Android support but there's nothing we can do about that.
zas[m]
Yes, more generally, SSL keeps evolving, and changes are often motivated by security needs, and the lack of software support leads to issues that can't really solved. Google policy improved regarding software updates (now 7 years but it wasn't the case for Android7). Not the worse among Android phones providers...
kepstinbrainz joined the channel
kepstinbrainz
an android device that old, you're probably not just missing newer root CAs, but the device probably also trusts some old CAs that should be removed because they're compromised :/
mayhem[m]
and moving away from LE is simply not an option.
ansh[m] has quit
discordbrainz
<10avamander> Maybe only the ones that have been distrusted or will be (like Entrust).
<10avamander> In any case such old Android devices probably need either a new browser (that ships it's own trust store) or a system security update in general.