|
Föderation EN Fr 06.10.2023 00:43:09 not super a fan of the whole "notifications now include the entire thumbnail" thing since the 4.2.0 update. takes up a lot of space and isn't really useful. it's also kinda laggy, presumably because it's adding 20 DOM elements (incl. a large image) for every YouTube title card. |
|
Föderation EN Fr 06.10.2023 00:46:39 @gsuberland noted - might be something we can improve in a future release. Just to check, you’re referring to the default web UI right? (I’m guessing so with the references to DOM etc). I can raise an issue in the morning if it doesn’t exist already. |
|
Föderation EN Fr 06.10.2023 00:47:50 @andypiper yeah, not the advanced UI. I just tweaked it locally and removing the "expanded" class makes a whole lot of difference from a visual perspective (less sure about perf) |
|
Föderation EN Fr 06.10.2023 00:52:44 @andypiper for testing, I removed the expanded class for each notification status card with this code: document.querySelectorAll("div.notification div.status-card.expanded").forEach(e => e.classList.remove("expanded")) and here's the before and after: Medien: 2 |
|
Föderation EN Fr 06.10.2023 00:57:57 @andypiper my personal preference would be to not display title cards or images at all in like/boost notifications, like the previous behaviour. or at least have that be an option in the notifications settings. I'll end up tweaking things to my exact preferences with greasemonkey/stylus anyway, but would be nice if it was configurable by default. speaking of, is there any plan to add a client-side customisation API? I'd love it if I could hook into filtering decisions, DOM update stuff, etc. |
|
Föderation EN Fr 06.10.2023 01:01:13 @gsuberland this sounds like an interesting idea. I don’t know of a plan for this right now - and definitely not in the immediate next release - but, I’d be interested to see what something like that might look like. Are there any analogous customisation APIs elsewhere that we could learn from? Thanks for the thinking material. Will pick this up further tomorrow! |
|
Föderation EN Fr 06.10.2023 01:15:42 @andypiper someone mentioned that one of the other fediverse platforms has a local API like this. I think it was calckey? but not 100% sure. I'd love to be able to do something like this clientside (pseudocode) for more complex filtering of post content: Medien: 1 |
|
Föderation EN Fr 06.10.2023 01:25:04 @andypiper this is just one example, of course. being able to hook into the incoming/outgoing data events, UI interactions, and DOM render stuff (state change, new component instance created, callback before component DOM update/insertion, callback after component DOM update) would make it incredibly flexible and super customisable. would probably also result in a lower barrier to entry for folks proposing UI tweaks, since they wouldn't have to spin up a whole instance just for dev/test. |
|
Föderation EN Fr 06.10.2023 13:54:33 @gsuberland so, on the current notification behaviour, I’ve added this thread to a planning doc and we may have some plans to improve; on the UI hooks, nothing to share right now, but thanks for the ideas! |
|
Föderation EN Fr 06.10.2023 00:58:21 @gsuberland fab, bookmarked this for reference. Appreciated! |
|
Föderation EN Fr 06.10.2023 01:00:41 @andypiper slight bug in that testing: should be just .notification-favourite and .notification-reblog that get expanded status cards removed, otherwise media in reply notifications get quashed too (which is not desired) |
