Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Post URL #11

Closed
lautarodragan opened this issue Feb 26, 2018 · 7 comments
Closed

Post URL #11

lautarodragan opened this issue Feb 26, 2018 · 7 comments
Assignees
Labels

Comments

@lautarodragan
Copy link
Member

lautarodragan commented Feb 26, 2018

Send the post's URL to Frost (along with content, etc).

This issue is blocked until url param is supported by the Frost API

@geoffturk
Copy link
Contributor

Needs poetapp/frost-api#27

@geoffturk geoffturk removed the blocked label May 17, 2018
@lautarodragan
Copy link
Member Author

@krobi64 we have a new attribute that could be used for this in verifiable claims right?

@geoffturk
Copy link
Contributor

Or just put it as an attribute inside the claim itself: canonicalUrl

@geoffturk
Copy link
Contributor

@markparolisi The idea here is to make the WP blog URL part of the work claim file data. This might be a one-liner, or not. :-)

@markparolisi
Copy link
Contributor

Not sure if we want to use the pretty URL or the GUID. Technically, we should use the GUID because it's immutable, but if services use that URL publicly to route traffic, then everybody is going to be hitting 301's from the GUID to the pretty URL.
Either way, yeah it's likely a one liner.

@geoffturk
Copy link
Contributor

@lautarodragan What do you suggest? Put the GUID in the canonicalUrl?

@geoffturk geoffturk added this to the WP v1.0.3 milestone Nov 21, 2018
@geoffturk
Copy link
Contributor

@markparolisi Just discussed this with Lautaro. We should use the pretty URL as the value for the key of canonicalUrl. Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants