New watermark on SVG graphs.

[tarehart]

Updating the watermark:

• In the background, behind the graph data
• Larger, so you can still read it if the graph data is in front of it
• Included the logo

Related suggestions in discord:

• The watermark blocks some of the content
• I appreciate the addition of a watermark but obscuring the chart with branding is bad

There's another file, probability-needle.tsx, that has the old watermark; I haven't touched it because I think it looks fine on the probability needle.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
dev	❌ Failed (Inspect)			Aug 13, 2024 9:33pm
prod	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Aug 13, 2024 9:33pm

1 Skipped Deployment

Name	Status	Preview	Comments	Updated (UTC)
docs	⬜️ Ignored (Inspect)	Visit Preview		Aug 13, 2024 9:33pm

[vercel]

@tarehart is attempting to deploy a commit to the Manifold Markets Team on Vercel.

A member of the Team first needs to authorize it.

[tarehart]

Hard for me to guess why dev failed deployment, could someone please provide logs?

[jahooma]

It was a flaky error for our /stats page, which is unrelated!

[ingawei]

Hello! I see the vision behind this change, but am hesitant to approve because there are just too many instances where this kind of watermark will be entirely illegible, kind of defeating the purpose:

[tarehart]

Good call, that example scribbled it out worse than I imagined. Philosophically I think the data should take priority, but I guess we could explore putting the watermark left of the time range controls so they never conflict, does that sound good?

[tarehart]

It'll take me a while to experiment with a watermark near the time range controls since there are a bunch of code paths to change and test, and I'm a little less confident about what would look good. Might be a week before I make time.

Should we consider merging this in the meantime as an incremental improvement?

[tarehart]

Side note, as an outside contributor with no GOOGLE_APPLICATION_CREDENTIALS_DEV, it's hard to test the contract page. I've resorted to temporarily using a regular db here rather than an adminDb:

manifold/web/pages/[username]/[contractSlug].tsx

Lines 96 to 97 in 8d62a25

	const adminDb = await initSupabaseAdmin()
	const contract = await getContractFromSlug(adminDb, contractSlug)

What's the reason for this distinction, and is adminDb actually needed for the contract page, which appears to be read only?

[tarehart]

Looking at the mobile dimensions again, I'm skeptical that I can make the alternative placement look good in the available space.

I think this change as it stands is a clear improvement, and I suggest merging it. The people suffer https://discord.com/channels/915138780216823849/1269095533956563014/1280347805101326429

[IanPhilips]

It looks good on the binary graphs but is basically invisible on the MC graph