-
Notifications
You must be signed in to change notification settings - Fork 1
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
Feature: notes/comments field #16
Comments
Would the content only include the notes, or would it also include the book name? If it's just the notes, it probably would break Micro.blog slightly, but I can work around it. Micro.blog takes the current summary + metadata and adds it to the blog post content. Might be worth discussing, though. I feel like this would be confusing for any Micropub endpoint that wasn't set up to understand |
My initial thought is the notes would only be in the content. Here's an example of what that request would look like. {
"type": [
"h-entry"
],
"properties": {
"summary": [
"Want to read: Title by Author, ISBN: ISBN"
],
"content": [
"I am really enjoying this book"
],
"read-status": [
"to-read"
],
"read-of": [
{
"type": [
"h-cite"
],
"properties": {
"name": [
"Title"
],
"author": [
"Author"
],
"uid": [
"isbn:ISBN"
]
}
}
]
}
} The I can see this causing problems if a micropub server uses only |
Micro.blog looks for book name and ISBN in Unless I'm missing something, the problem is that most Micropub endpoints are going to discard summary if content is present. So you'll end up with published blog posts like "This is a great book" without any reference to what the book actually is. |
I was thinking about this again and realized that indieweb/micropub-extensions#8 could help. IndieBookClub could query a Micropub server for whether it supported the |
Add a notes/comments field which would be set as the
e-content
of the post and micropub request.@manton I wanted to check in with you to make sure this wouldn't unexpectedly break anything for micro.blog users.
The text was updated successfully, but these errors were encountered: