binaryfate: Please deploy master when you can.

We will also need a cache flush

cache flush after deployment right?

yep

Are there opinions about removing the "Known issues" field in the downloads page?

I added it because somebody requested it, but i feel it's kinda useless

Now we have more frequent releases and usually if there is a problem the release with the fix is released quite soon

that field is also quite annoying to maintain, because we need to change a field (issues.yes issues.no) and by the time that's done the issue is probably solved

selsta do you have an opinion on that? do you think make sense to keep that field or my points about releases make some sense?

Asking now because i was about to make some changes. I wanted to remove the dropdown and replace it warning banner, but now i'm asking myself if would just be better to remove it

.merges

Merge queue empty

.merge+ 1117

...

.merges

ErCiccione[m]: if it is annoying to maintain then we can remove it

ErCiccione[m]: deployed. fluffypony can you flush?

on it

binaryFate: do you have a handle on the CDN or must I do that too?

I can do CDN

ok

Thanks guys

cache flushed on the CF side

should be good

sarang your post about tryptich is online: getmonero.org/2020/08/22/triptych.html

fluffypony: when linking to the website in the future, should we link to getmonero.org or getmonero.org ?

either or

just don't link to web.getmonero as that's a cache-skip

ok

fluffypony: some people still link to the src.getmonero.org subdomain, would it make sense to redirect it? same for web.getmonero.org to avoid duplicated content?

src does redirect

it did not for me

web is the canonical pass-through if the CDN endpoint doesn't have a cached page

oh weird

it's supposed to

does not redirect

kk lemme fix

ok, understand web now

fixed

redirect might be cached client side

so it won't work immediately

but if you try in a different browser it should work now

it did redirect now for me

looks good

Hooray for Triptych blag post!

\o/

lol selsta. I opened the same PR to change monerooutreach.org links and didn't think of doing it for getmonero.

.merge+ 1160

Added

mmh wait a sec. i'm commenting on the PR

.merge- 1160

Removed

yeah now i remember why i didn't do it

why? :P

Because those links shouldn't be there anyway

i mean

right, jekyll supports this

they should use jekyll's format: {{ site.baseurl }}

but we can still change them for now

changing web to www does not make it less correct

it's important to have the jekyll structure, because otherwise when the onion address will be available people will be redirected to clearnet for no good reasn

*reason

so, would be good to replace all web.getmonero... to {{ site.baseurl }}...

selsta could you change those links directly to the liquid structure?

how should it look like exactly?

getmonero.org/2019/02/01/pruning.html -> {{ site.baseurl }}/2019/02/01/pruning.html

Now that i think about it we will probably need to edit a couple of things anyway to avoid linking to clearnet once the the onion address will be deployed. I will look it up.

Or maybe we can deal with that directly with nginx. Probably just better to wait for pigeons to finish with it before making conjectures

speaking of pigeons, I am in search of a host for the xmr-pr bot

nginx can replace all of the instances of getmonero.org with foobarblahhh123abc.onion in all of the responses, but it's probably better to just use relative links everywhere, if we want people to stay on the same domain

yeah, that's why it's important to have jekyll deal with all internal links

thanks selsta :)

.merge+ 1160

Added