reading-am / reading

The dreams! The dreams! It's all just absurdity in the light of day but the dreams!
MIT License
10 stars 0 forks source link

Handle Google Docs' three different URL schemes #303

Open leppert opened 12 years ago

leppert commented 12 years ago

From Casey Gollan caseygollan@gmail.com:

I think you're aware of this bug, but Google Docs automatically shuttles people between three URLs depending on how they're set up, which can really fragment readings/conversations and make the same thing show up in the feed in a redundant way. I have no way of seeing what comments Max wrote on his reading because GDocs won't let me visit the docs for his domain form which he shared it, instead redirecting me to either of the other two urls.

thebyrd commented 12 years ago

The first link is under Max's docs account (see /a/maxfenton.com in the url). If I'm logged in then the url will change to my account (/a/byrdhou.se). The second and third links are for when you're not logged in. They all have the same key(0Am32b0H2bOCCdFgwRDh6UVIxVzI4ajdadEJVTEZkX0E`), so it would be pretty straight forward to write a parser that looks for the key parameter and combines the urls into the same post. On Oct 8, 2012, at 2:20 PM, Greg Leppert wrote:

From Casey Gollan caseygollan@gmail.com:

I think you're aware of this bug, but Google Docs automatically shuttles people between three URLs depending on how they're set up, which can really fragment readings/conversations and make the same thing show up in the feed in a redundant way. I have no way of seeing what comments Max wrote on his reading because GDocs won't let me visit the docs for his domain form which he shared it, instead redirecting me to either of the other two urls.

https://docs.google.com/a/maxfenton.com/spreadsheet/ccc?key=0Am32b0H2bOCCdFgwRDh6UVIxVzI4ajdadEJVTEZkX0E#gid=0 https://docs.google.com/spreadsheet/ccc?key=0Am32b0H2bOCCdFgwRDh6UVIxVzI4ajdadEJVTEZkX0E https://docs.google.com/spreadsheet/ccc?key=0Am32b0H2bOCCdFgwRDh6UVIxVzI4ajdadEJVTEZkX0E#gid=0 — Reply to this email directly or view it on GitHub.