I think it's mostly standard cache times

in other words, we aren't using cache hints to have it not be cached (not that cache hints are always adhered to either)

downloads stuff is gong up via LFS now, all seems to be working well

should keep the actual repo size pretty small (if you're not pulling down LFS files)

we should consider switching to LFS for the big files in the site repo (eg. movies)

all done

nice

Whitepaper reviews added to `monero-site`: monero-project/monero-site #1111

CI still in progress

sarang: i already opened #1109

So you did :)

yeah did it yesterday. I think i posted it here too :P

I'd recommend adding to the `pubs` directory for consistency with other PDFs

(1111 does this)

ErCiccione: can't expect me to read _everything_ now!

Lol, you are right

sure, i didn't put them there beecause they are not "official" pubblication, but if it's fine for you it's fine for me

Hooray, sarang wins!

What would be official?

The "unpublished" `ge_fromfe_frombytes_vartime` document lives there already anyway

(not sure what "unpublished" is supposed to mean there...)

I meant "published" pubblications. Those PDFs are just comments of pubblications. Don't know if i explained myself properly here

nevermind. I understood your point :P

oh ok

I'm probably rumbling nonsense right now

I see your point

There are 38 degrees (celsius) here, i'll blame that

jinkies

I don't personally care where the PDFs live, directory-wise

Merge whichever makes the most sense!

And maybe I'll check for existing PRs before writing new ones =p

I'm super fast

I moved them to pubs: monero-project/monero-site #1109

a review would be appreciated

wilco

Will it generate a new preview from the force-push?

I'll check the code, but being able to directly test links in preview would be nice

Silly question: any reason the `baseurl` is used for the `href` tags for the other papers, but not these?

yep

every force push triggers a new netlify preview

k

But yeah, the link format is different on the whitepapers apparently

That's the absolute url i used a relative url. No difference

OK, no performance diffs?

We could keep everything the same for consistency

Yeah, might as well use one format

Oh, the netlify bot just updates its original comment; neat

didn't see that :D

I'll wait until you update and then test

Or just use 1111 instead :D

pushed

approved

what's 1111 i missed that reference?

PR 1111

did the same thing as PR 1109

I just closed 1111

O yeah. Sorry man, today i am a bit off

No worries!

Looks like 1109 does the trick

and preview links work fine

Perfect

.merge + #1109

.merges

-.-

alright, i'm gonna go get a drink or something

.merge+ #1109

Added

.merges

winner

yaaay

Too bad the bot doesn't list in numerical order

Looks like it's lexicographic order

Who runs the bot?

dsc

dsc_: possible to update the bot to list merges numerically?

ErCiccione: are you waiting on review for other PRs right now that need to get in the queue?

^ thanks moneromooo

:D

And add PRs without using a # sign, it requires it for some reason. Or would it otherwise cause false positives ?

Failing that, I'll stop forgetting with time.

Usually it did list them in numerical order

sarang: checking

ErCiccione: was that when < 1000 ?

lol, looks like you're right, it's alpha.

The transition from 9xx to 1yyyy would ruin things

s/1yyyy/1yyy

I think so. the bot already freaked out in past but now seems to be that.

I wonder if its code is public

sarang: #1046 #1076 #1083 #1087 #1105 #1108 need a review or a final review

I wonder if its code is public -> it's not AFAIK

k

Reviewed 1046

ErCiccione: is there a way to force a new preview build?

1076's preview has expired

Those are the old previews made with the free accounts that now got deleted. I can force push to trigger the new barolo-time previews

sarang: numerically? hmm.. Going to have to devise an algorithm... it will be hard, but I think I can do it

Done, it's building

dsc_: really?

How is it done now?

Thanks ErCiccione

Too bad the bot doesn't update its comments after previews expire

oof sarang, it's complicated. But I will persevere

That's because they are linked to different accounts. Previews don't expire afaik

hehe sorry it's /s next update will have:

- numerical listing

- add without #

Thanks :)

.merges

.merge- 937

Removed

.merge+ 937

Added

Oh, because the octothorpes look like channel links?

dsc_: that was fast =p

Another satisfied customer!

dsc_: will it work anyway if i use #? i will 100% forget about the change

.merge+ #938

Added

Sorry. I meant for it to be optional only :)

.merge- #938

Removed

Nice.

ErCiccione: seems # still works :)

tested 1076

nice. Thanks

in fact;

.merge+ #1046

Added

.merge+ blablabla111blablabla

Added

.merge- blablabla111blablabla

Removed

`re.findall(r'[\d]+', trigger.group(2))`

:P

.merge+ not123

Added

.merge

.merge?

.merges

.merge- not123

Removed

.merge+ 1e3

...

heh

.merge+ 1e12

.merges

ha :)

.merge- 1 3 12

Removed

bad mooo stop breaking my bot

One last time, sir ?

okiii

.merge+ 1 3

Added

.merge?

.merges

.merge- 1 3

Removed

.merge+ 1076

Added

CLSAG audit PR: monero-project/monero-site #1112

Please review ASAP

on it

:D

Waiting for CI preview now

ErCiccione: making those changes now

Ok. i'm reviewing the rest

sgp wants me to use the svg instead

OK to just use that in the `img` tag? I don't know about browser support

Are you referring to the svg sgp_ is talking about or the liquid tag?

Let me test it with that svg, but shouldn't be an issue to use that instead

the one he's talking about

I'm adding it presently

and the change you requested

will push momentarily

browser support shouln't be a problem.

+1 for svg, the old image was blurry on my phone

SVG is a nice to have

almost done with new push

one sec

the svg looks good

also only 9 kB

compared to something like 100

force-pushed just now

Let me know about the logo sizing

waiting on CI preview

The logo is good

Did the preview update with the force push?

there it goes

Looks good on my browser too

Lemme check mobile

looks good on mobile too

fast loading too :D

so fast

Can someone give a thumbs-up to the updated commit?

Forcing the width wasn't necessary, but doesn't hurt either

I didn't know how it would be handled otherwise with SVG scaling

Expanding to fill that page element seems like it'd be awkward

The width in the svg is 412px

it's good tho, no worries

ah ok

updated anyway =p

:)

I know it'd bother me otherwise...

What'd be the ETA on build/deploy?

OSTIF's post is up

I happen to like my post better, but I'm obviously biased :D

I like yours better too :p

Just one minor thing sarang: could make bold "tests indicate that users will see a 20% improvement in signature verification, and at least a 10% overall improvement for typical transactions!"?

can do

would be good to have some @ links to the moneropedia for words like "transactions", but that's not really important

I'll do the bold right now

Other links could be done later?

Sure, no big deal.

done

just left my approval

sarang: About the ETA: If luigi1111 is around we can merge and fluffypony, binaryfate or pigeons could deploy

why are there so many merges

.merges

can you all calm down

.merge+ #1112

Added

get one more!

LOL

.merge+ all the things

.merge+ all the th1ngs

Added

Oops

LOL

.merge- 1

Removed

wut?

.merge+ all the things

ah ok

The blog post is the biggest thing, since OSTIF have already posted theirs

yeah luigi1111 please merge 1112, the rest can wait

done

Thanks! Let's get that deployed!

fluffypony ^

Who needs sports when you can watch this

Fluffy has pinged others for the build

Looks like no response yet :/

binaryFate pigeons

spoke to pigeons - we don't want to break binaryFate's stuff, we'll find a uniform way of doing this going forward so this doesn't happen

I see

Like a checklist :)

Anyone know if binaryFate will be online today?

Probably better to PM him. Haven't seen hin online much lately.