[tor-bugs] #25985 [Obfuscation/Snowflake]: Add AMP cache as another domain fronting option with Google

[Tor Bug Tracker & Wiki]

#25985: Add AMP cache as another domain fronting option with Google
-----------------------------------+------------------------
 Reporter:  twim                   |          Owner:  (none)
     Type:  project                |         Status:  new
 Priority:  Medium                 |      Milestone:
Component:  Obfuscation/Snowflake  |        Version:
 Severity:  Normal                 |     Resolution:
 Keywords:                         |  Actual Points:
Parent ID:                         |         Points:
 Reviewer:                         |        Sponsor:
-----------------------------------+------------------------

Comment (by twim):

 Replying to [comment:12 dcf]:
 > Do you have the infrastructure you need for testing? It looks like you
 have a way to make your own subdomains. The broker has automatic Let's
 Encrypt certificate support, but it requires you to have ports 443 and 80
 free. If you don't have a spare server set up, I may be able to get you
 one.

 Yes, I do. Thanks a lot, I guess I am fine with that.

 > I'm thinking about the
 [https://www.ampproject.org/docs/fundamentals/spec#the-amp-html-format
 <script type="application/ld+json">] block. Perhaps we can stuff arbitrary
 data in there and the AMP cache won't touch it. But realistically
 speaking, base64 in the page body is likely good enough.

 Probably it will work out. Though it looks like a premature optimization
 for me because AMP cache may strip "unsupported data" from this
 JSON/whatever. It should never strip words and links and Base64 is more
 like them.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/25985#comment:13>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online