GWGsnarfed: The faces in a facepile. Are they supposed to link to the url or the author url? I remember some discussion about this, but I can't remember what was said.
mblaneygRegorLove were you still logged in when you clicked that link? The idea with that comment is that it appears in my feed (since I'm the recipient) and then I can click the link to create the reply.
mblaneyyeah I should word that better. I don't want it to say "paid" because if I now pay you back $5, saying that you've only paid me $5 wouldn't make sense either.
skippyI want to post retweets on my site, but want to preserve line breaks and formatting. So I *think* I want <blockquote class="p-content><pre>Some tweet content here</pre></blockquote>. I have CSS declarations for each of pre and blockquote, so the previous example seems to be getting the padding of BOTH of those.
skippyinteresting! thanks for the pointer. Mostly, I don't want to (overly) mangle some of the more clever tweets people post involving specific formatting...
skippywhen i try that, it still seems to be inheriting one of the other padding declarations. If I remove blockquote, but leave blcokquote>pre, then I get zero padding.
oodanii'm curious: micropub uses essentially one endpoint, with the request body deciding whether it creates, updates, or deletes. was a more restful design considered? something like POST /micropub/entries, PATCH /micropub/entries/5, DELETE /micropub/entries/32
oodanithat of course only works for h-entry, but that's no showstopper: GET /micropub could return something like {"h-entry": "/micropub/entries", "h-event": "/micropub/events"} to advertise both the supported microformats and where they're located
mblaneygRegorLove moving here from meta: thanks again! looks like not having categories published in your post has stopped it from completing the process though...
mblaneythis is all a bit goldberg-esque, but the flow is: if my site picks up the in-reply-to it will publish it as a comment, when it publishes a comment it salmentions the original links, then indiepay.me picks up on the whole thing.... so without the markup it doesn't make it!
mblaneyyour reply doesn't have to link to indiepay.me but it indiepay.me will check that it's in-reply-to the original post (and that you as the author of the reply are person-tagged in the original post)
Zegnat!tell GWG re facepiles and where to link them, have a look at sebsel’s implementation: https://indieweb.org/facepile#Sebastiaan_Andeweg it shows author portraits as links to people, and then reply-type-icons as links to posts.
sknebelheh, at IWC Düsseldorf someone also asked about why Micropub is like it is. I guess if you use a "full-featured" web framework like Ruby on Rails or Django the REST-y approach is fairly natural to implement, and the one-endpoint design actually more confusing to implement., vs in other environments the one endpoint is easier in various ways
loicm, plindner and [kevinmarks] joined the channel
[kevinmarks]It needs you to replace the whole resource, which means you should read it all, change it and write it back. Now you have both a "did I parse it right?" problem and a possible race condition.
ZegnatBut PUT always overwrites the whole thing right? So no parsing should be neccessary? Surely taking the HTTP request body and writing it to a file wholesale is actually less error prone than POST where you have to take the request body and parse it?
myfreeweb, schmarty, zoglesby, eli_oat[m], grantcodes and mindB joined the channel
ZegnatIt is just as hard for a server to interpret structure send as the body of an HTTP POST as it is to interpret the exact same structure in the body of an HTTP PUT. I do not see a technical difference there in the slightest.
ZegnatThe only question is, what does the PUT method mean and what sets it apart from the POST method. And that is where the RESTful design people come in ;)
ZegnatNot sure I follow. PHP’s server only knows what to do with a very specific POST request. It will try and parse a form-encoded HTTP request body on a POST request and give it to the user in a specified variable. Any other POST request it doesn’t do anything with it, just like with any PUT request.
jgmac1106so [kimberlyhirsh] sent me a link that I was able to follow here: http://schema.org/Course been getting a lot of push back from folks saying schema.org rdf and JSON-LD is the future and nobody will ever mark up their courses to make microformats2
jgmac1106I disagree their big argument is always, “Well that is what Google wants.” I kind of see that as an exact reason to choose an alternative with greater control of the content creators.
ZegnatWell, if there is a big presedent for using an already documented vocabulary in JSON-LD, I am not super sure what the argument is for copying it to microformats?
ZegnatThere are arguments for why to use one data format over the other, if you are starting out. But if there is already an existing format that people agree on, why introduce a competing one? That’s an important question to answer.
jgmac1106part of my reason is where the control ends up falling. If those in higher ed are going to control what we publish and how we publish keeping things as simple as possible is better in the long run. Common markup hard to implement stuck behind proprietary software leaves us still beholden to the publishers and platforms IMHO
jgmac1106Looking at the schema.org spec for example their are more classes for protecting copyright and institutions than their are for the actual learning the object contained. I guess thats, “My Why?” but I am wondering if I am trying to create a groundswell for a battle that may have been over for some time
ZegnatYes. If you are talking to folks who already know how to author HTML (or even already publish it!) it might be a lot easier to get them to add microformats than JSON-LD (which will be a choir to author by hand, IMHO).
ZegnatBut if the people you are talking with are going to use specialised tools anyway. Whether those tools output HTML+Schema or HTML+mf2 isn’t really an issue, right?
jgmac1106[zegnat] probably right. Need to remember the indie in indieweb and that this might be a small niche who reject the large corporate learning solutions
ZegnatYou could actually mark-up the p-name of h-cite with a <cite> element. But thanks to the multiple properties of h-cite, you can also add a p-author outside of that <cite> and it is still part of the same citation.
skippykind of. thanks. the h-cite wiki entry says "If you are displaying the entire entry, then it does not need an h-cite." which confuses me a bit on how to display reposts...
LoqiA repost on the indieweb is a post that is purely a 100% re-publication of another post. The act of reposting is an umbrella term that covers the general practice of republishing another post typically on the same service or silo, but more and more across sites https://indieweb.org/repost
jgmac1106[skippy] my succint reason is because I can. It is easier and more useable for an individual teacher. I could quickly throw up a template site and get people to remix it. I don’t knwo how to do that with JSON-LD. I guess that is my reason. And isn’t the phrase “large corporate’ enough motivation to go against?
Zegnatskippy? Oh? I mean, it is up to you. I would use e-content for reposts. Because if I repost something with an image or links in it, I want that to be kept
Zegnatp- = plain text, e- = embedded HTML. So p-* extract only the plain text value of the element you put it on, while e-* will also return a copy of the verbatim HTML markup
Zegnatjgmac1106, if the individual teachers you are targetting are comfortable authoring HTML, it makes a lot of sense to give them remixable HTML snippets, yeah.
skippyok... so for a repost, e-contnet might make sense. but then on a reply, in which i blockquote the post to which i am replying, does it make sense to have two e-contents?
ZegnatThe reply context blockquote can use the exact same mark-up as the repost. It can be an h-cite within a u-in-reply-to. So completely fine to use e-content on that h-cite, and have a separate e-content on your h-entry
[kevinmarks][jgmac1106] looking at the Course schema, there is a case there for a microformat with h-events for the instances. The value you cold potentially offer is RSVPs
jeremycherfasSkippy++ zegnat and I have been working our way through getting it to work for me. And we're getting there, slowly, although I won't be able to do more until next tuesday at the earliest.
Zegnatdgold, the promised PR is finally sent. Sorry for the slow down. It got through all my testing but obviously you should also test before merging.
Zegnatjeremycherfas was testing your endpoint and had to do some code changes to get it to work with a self-hosted token endpoint. (Mintoken in that case.)
ZegnatThe function still uses the $configs variable as a global, dgold. Because I wanted to keep my changes the least invasive. So no changes to the function signature
ZegnatProbably doing the Mintoken security update this weekend, then I only have issues about error reporting left to tackle. And those shouldn’t be breaking.
skippyfor myself, I see only a small number of authenticated clients connecting to my micropub target. Quill, Omnibear, Indigenous, Android Micropub. DB seems a littel overkill; but I'm quite sure I'm missing somethign fundamentally important.
skippyPHP Notice: Use of undefined constant SODIUM_BASE64_VARIANT_URLSAFE_NO_PADDING - assumed 'SODIUM_BASE64_VARIANT_URLSAFE_NO_PADDING' in Command line code on line 1
skippy"Based on the German legal literature I have assessed, this would make the GDPR applicable to a personal website as soon as its content has any connection to professional or commercial activity, hence not only applying to freelancers, who undoubtedly are affected, but e.g. to any web professional who discusses web technology on their personal site "
Loqi[Daniel Goldsmith] Sebastian, first of all, thank you for your detailed write up on this issue. I think much of your roadmap is worthwhile, and of great interest.
I cannot, however, say that I am convinced by your contentions regarding the effect of GDPR and indieweb ...
LoqiIt looks like we don't have a page for "indiepay.me" yet. Would you like to create it? (Or just say "indiepay.me is ____", a sentence describing the term)
KartikPrabhu I unpiled my faces for that reason
GWG So, I just did this... https://tiny.n9n.us/2015/06/27/lights/
gRegorLove mblaney, I saw the notification on indiepay too
skippy I want to post retweets on my site, but want to preserve line breaks and formatting. So I *think* I want <blockquote class="p-content><pre>Some tweet content here</pre></blockquote>. I have CSS declarations for each of pre and blockquote, so the previous example seems to be getting the padding of BOTH of those.
oodani i'm curious: micropub uses essentially one endpoint, with the request body deciding whether it creates, updates, or deletes. was a more restful design considered? something like POST /micropub/entries, PATCH /micropub/entries/5, DELETE /micropub/entries/32
Zegnat !tell GWG re facepiles and where to link them, have a look at sebsel’s implementation: https://indieweb.org/facepile#Sebastiaan_Andeweg it shows author portraits as links to people, and then reply-type-icons as links to posts.
sknebel heh, at IWC Düsseldorf someone also asked about why Micropub is like it is. I guess if you use a "full-featured" web framework like Ruby on Rails or Django the REST-y approach is fairly natural to implement, and the one-endpoint design actually more confusing to implement., vs in other environments the one endpoint is easier in various ways
[kevinmarks] also PUT and PATCH are very hard to implement well
@scottmallinson Trying to work out a publishing strategy that combines the benefits of POSSE, captures engagement through webmentions, and importantly makes sense.
https://scottmallinson.com/blog/2018/05/10/1919/ (twitter.com/_/status/994538265532395520)
jgmac1106 so [kimberlyhirsh] sent me a link that I was able to follow here: http://schema.org/Course been getting a lot of push back from folks saying schema.org rdf and JSON-LD is the future and nobody will ever mark up their courses to make microformats2
Loqi A repost on the indieweb is a post that is purely a 100% re-publication of another post. The act of reposting is an umbrella term that covers the general practice of republishing another post typically on the same service or silo, but more and more across sites https://indieweb.org/repost
jeremycherfas Skippy++ zegnat and I have been working our way through getting it to work for me. And we're getting there, slowly, although I won't be able to do more until next tuesday at the earliest.
