09:41:18 wut, is that on mobile selsta? 09:41:39 desktop 09:42:24 O yeah, just checking. something clearly happened there :P 09:45:22 i haven't touched that section or the css tho. Not sure of what happened. Opening an issue, i'll take a better look this evening 09:51:35 I just built master locally and everything looks as it should be. I'm not sure of what could have messed that up. 09:52:05 Binaryfate if you updated the server, could you clear all caches and see if that's the issue? 09:54:34 CSS looks the same locally and online 09:56:35 I'm just throwing guesses, buti think the problem is either related to some caching problem or to the new nginx configs. I mean, those are the two things that changed 09:59:30 I think i quick fix would be to just resize thos logos and make them all the same, but still worth to inspect what happened. 10:03:48 oh no wait, the CSS is indeed different. the "style" parameter in the img tag is missing in the deployed version. 10:07:30 Yep, missing in the deployed website but present in the source: https://repo.getmonero.org/monero-project/monero-site/blob/master/downloads/index.md#L261 10:09:36 binaryfate pigeons: could you check if the 'style' attribute of the line linked above is present in the source you have on the server? 10:09:58 and now i stop talking to myself 10:11:30 I did not do anything, just reading now 10:12:15 Ah ok. Then it's even weirder 10:12:40 Should I still do it or? 10:12:48 for some reason the style attribute of those logos is empty,but it's correct in master 10:13:01 and wasn't touched before 10:13:21 at this point i think would be better to just update the server 10:13:40 but something definitely went wrong there 10:21:58 binaryfate please ping me after the server is updated so i can take a look. I think i have to go afk soon 10:45:53 ErCiccione[m] done 12:17:23 still looks borken 12:17:26 broken* 12:18:50 `[Error] Refused to apply a stylesheet because its hash, its nonce, or 'unsafe-inline' appears in neither the style-src directive nor the default-src directive of the Content Security Policy. (downloads, line 853)` 12:19:25 appears to be related to the recent server changes done by pigeons 17:45:35 yeah, matomo might be broken as well. 17:49:17 matomo? 17:51:44 The self hosted analytics server we have. Firefox's console tell me that it's bloking a resource because of the security policy and links to the matomo script on the download page. 17:54:13 s/server/service 17:55:25 ah ok 17:55:31 looks like the site got locked down too hard :P 17:57:40 :) 17:58:15 I might be wrong about matomo tho. I don't remember if that error was there before.