So I'm keeping this as a fairly general, high level topic.
I'm a member of the W3C Social Web Working Group and the Social Web Incubator Community Group. And there are a number of specs the Working Group has come out with. There are various bits an pieces that can be used separately but I figured it would be good to give some background on them and some of the discussion that is happening. Would love feedback.
First off, the specs from the Working Group.
ActivityStreams 2 https://w3.org/TR/activitystreams-core/
This is essentially a way of expressing activities that happened as a JSON feed. It covers just about anything you could want and has an extension mechanism to allow for custom things outside of it. Currently it doesn't have a lot of usage, but there is certainly interest in it.
Webmention https://w3.org/TR/webmention/ A much simpler version of linkback, its essentially a method to just notify a specific URL that you have an update for it. Usually this is for letting URLs know of a reply to them. Currently used by indieweb, Known, Micro.blog, and a handful of other implementations. It also has a Salmention extension that is effectively a much simpler implementation of the salmon protocol
Micropub https://w3.org/TR/micropub/ This is a client to server API, Again, heavily used in the indieweb and some others. It uses microformats vocabulary to post and optionally update and delete, posts.
ActivityPub https://w3.org/TR/activitypub/ This is a new spec developed within the working group and getting heavily reviewed within the community group now which does include several projects. It has two parts, both a client to server and server to server part.
WebSub https://w3.org/TR/websub/ This is a cleaned up version of PubSubHubbub 0.4. PuSH was never specified under the W3C so it has been an effort to not break any existing PuSH 0.4 implementation but still provide some clearer specification to it. Mastodon should already be compliant.
Outside of the WG, there are other parts
Microformats http://microformats.org/wiki/microformats2 this is sort of the counterpart to ActivityStreams. It involves adding classes to the displayed content on the page, so you don't repeat yourself. This is already in place on every mastodon post and is on Friendica, Hubzilla, pump.io, gnu social, Known, micro.blog, and the growing list of indieweb implementations. Pretty much everyone except diaspora.
Webfinger this is what sort of led me here today as it seems to be the first place to work on future endeavors. As I understand it there were some issues with needing to rate limit the webfinger endpoint, and many dislike the amount of indirection needed for it. The biggest issue has been getting this to work for the other half of the social world that doesn't use acct:// for user identities. The indieweb uses just URLs for identitiy. So aaron.pk or ben.thatmustbe.me. One option is to add some fake bit to the beginning, like aaronpk@aaron.pk, or ben.thatmustbe.me@ben.thatmustbe.me. Gets pretty redundant. And then the issue is that a person has two different ways to refer to them, if you telling someone using Known how to refer to you, it has to be your URL, if its someone on Mastodon, its another way. The other issue is that some people don't even have access to the .well-known folder on their server. This can be a huge limitation for them sadly.
So I was hoping to start here. Can everyone give some general feedback of webfinger.
-
Does it do everything you need?
-
Why did you have to rate limit it?
-
Are there any problems you have with it?
-
Do you have any ideas on alternative ways this could work? For example, I could see being able to look up users by either @user@domain.com, @domain.com (if its a single user domain, or @domain.com/user, etc. Then as long as the account is fetched in the same way (either parsing out the microformats from that page, or use content negotiation to get an alternative formats), you would be good to go.
Sorry for the long post, just wanted to get anyone who cares up to speed.
Originally Posted at https://discourse.joinmastodon.org/t/federation-with-social-web-in-general/352
{
"type": "entry",
"published": "2017-06-06T23:01:29-0400",
"url": "https://ben.thatmustbe.me/article/2017/6/7/1/",
"content": {
"text": "So I'm keeping this as a fairly general, high level topic.\n\nI'm a member of the W3C Social Web Working Group and the Social Web Incubator Community Group. And there are a number of specs the Working Group has come out with. There are various bits an pieces that can be used separately but I figured it would be good to give some background on them and some of the discussion that is happening. Would love feedback.\n\nFirst off, the specs from the Working Group.\n\nActivityStreams 2 https://w3.org/TR/activitystreams-core/\n\nThis is essentially a way of expressing activities that happened as a JSON feed. It covers just about anything you could want and has an extension mechanism to allow for custom things outside of it. Currently it doesn't have a lot of usage, but there is certainly interest in it.\n\nWebmention https://w3.org/TR/webmention/ A much simpler version of linkback, its essentially a method to just notify a specific URL that you have an update for it. Usually this is for letting URLs know of a reply to them. Currently used by indieweb, Known, Micro.blog, and a handful of other implementations. It also has a Salmention extension that is effectively a much simpler implementation of the salmon protocol\n\nMicropub https://w3.org/TR/micropub/ This is a client to server API, Again, heavily used in the indieweb and some others. It uses microformats vocabulary to post and optionally update and delete, posts.\n\nActivityPub https://w3.org/TR/activitypub/ This is a new spec developed within the working group and getting heavily reviewed within the community group now which does include several projects. It has two parts, both a client to server and server to server part.\n\nWebSub https://w3.org/TR/websub/ This is a cleaned up version of PubSubHubbub 0.4. PuSH was never specified under the W3C so it has been an effort to not break any existing PuSH 0.4 implementation but still provide some clearer specification to it. Mastodon should already be compliant.\n\nOutside of the WG, there are other parts\nMicroformats http://microformats.org/wiki/microformats2 this is sort of the counterpart to ActivityStreams. It involves adding classes to the displayed content on the page, so you don't repeat yourself. This is already in place on every mastodon post and is on Friendica, Hubzilla, pump.io, gnu social, Known, micro.blog, and the growing list of indieweb implementations. Pretty much everyone except diaspora.\n\nWebfinger this is what sort of led me here today as it seems to be the first place to work on future endeavors. As I understand it there were some issues with needing to rate limit the webfinger endpoint, and many dislike the amount of indirection needed for it. The biggest issue has been getting this to work for the other half of the social world that doesn't use acct:// for user identities. The indieweb uses just URLs for identitiy. So aaron.pk or ben.thatmustbe.me. One option is to add some fake bit to the beginning, like aaronpk@aaron.pk, or ben.thatmustbe.me@ben.thatmustbe.me. Gets pretty redundant. And then the issue is that a person has two different ways to refer to them, if you telling someone using Known how to refer to you, it has to be your URL, if its someone on Mastodon, its another way. The other issue is that some people don't even have access to the .well-known folder on their server. This can be a huge limitation for them sadly.\n\nSo I was hoping to start here. Can everyone give some general feedback of webfinger.\n\n\n\tDoes it do everything you need?\n\t\n\t\n\tWhy did you have to rate limit it?\n\t\n\t\n\tAre there any problems you have with it?\n\t\n\t\n\tDo you have any ideas on alternative ways this could work? For example, I could see being able to look up users by either @user@domain.com, @domain.com (if its a single user domain, or @domain.com/user, etc. Then as long as the account is fetched in the same way (either parsing out the microformats from that page, or use content negotiation to get an alternative formats), you would be good to go.\n\t\nSorry for the long post, just wanted to get anyone who cares up to speed.\n\nOriginally Posted at https://discourse.joinmastodon.org/t/federation-with-social-web-in-general/352",
"html": "<p>So I'm keeping this as a fairly general, high level topic.</p>\n\n<p>I'm a member of the W3C Social Web Working Group and the Social Web Incubator Community Group. And there are a number of specs the Working Group has come out with. There are various bits an pieces that can be used separately but I figured it would be good to give some background on them and some of the discussion that is happening. Would love feedback.</p>\n\n<p>First off, the specs from the Working Group.</p>\n\n<p><strong>ActivityStreams 2</strong> <a href=\"https://w3.org/TR/activitystreams-core/\">https://w3.org/TR/activitystreams-core/</a><br />\nThis is essentially a way of expressing activities that happened as a JSON feed. It covers just about anything you could want and has an extension mechanism to allow for custom things outside of it. Currently it doesn't have a lot of usage, but there is certainly interest in it.</p>\n\n<p><strong>Webmention</strong> <a href=\"https://w3.org/TR/webmention/\">https://w3.org/TR/webmention/</a> A much simpler version of linkback, its essentially a method to just notify a specific URL that you have an update for it. Usually this is for letting URLs know of a reply to them. Currently used by indieweb, Known, Micro.blog, and a handful of other implementations. It also has a Salmention extension that is effectively a much simpler implementation of the salmon protocol</p>\n\n<p><strong>Micropub</strong> <a href=\"https://w3.org/TR/micropub/\">https://w3.org/TR/micropub/</a> This is a client to server API, Again, heavily used in the indieweb and some others. It uses microformats vocabulary to post and optionally update and delete, posts.</p>\n\n<p><strong>ActivityPub</strong> <a href=\"https://w3.org/TR/activitypub/\">https://w3.org/TR/activitypub/</a> This is a new spec developed within the working group and getting heavily reviewed within the community group now which does include several projects. It has two parts, both a client to server and server to server part.</p>\n\n<p><strong>WebSub</strong> <a href=\"https://w3.org/TR/websub/\">https://w3.org/TR/websub/</a> This is a cleaned up version of PubSubHubbub 0.4. PuSH was never specified under the W3C so it has been an effort to not break any existing PuSH 0.4 implementation but still provide some clearer specification to it. Mastodon should already be compliant.</p>\n\n<p>Outside of the WG, there are other parts<br /><strong>Microformats</strong> <a href=\"http://microformats.org/wiki/microformats2\">http://microformats.org/wiki/microformats2</a> this is sort of the counterpart to ActivityStreams. It involves adding classes to the displayed content on the page, so you don't repeat yourself. This is already in place on every mastodon post and is on Friendica, Hubzilla, pump.io, gnu social, Known, micro.blog, and the growing list of indieweb implementations. Pretty much everyone except diaspora.</p>\n\n<p><strong>Webfinger</strong> this is what sort of led me here today as it seems to be the first place to work on future endeavors. As I understand it there were some issues with needing to rate limit the webfinger endpoint, and many dislike the amount of indirection needed for it. The biggest issue has been getting this to work for the other half of the social world that doesn't use acct:// for user identities. The indieweb uses just URLs for identitiy. So aaron.pk or ben.thatmustbe.me. One option is to add some fake bit to the beginning, like aaronpk@aaron.pk, or ben.thatmustbe.me@ben.thatmustbe.me. Gets pretty redundant. And then the issue is that a person has two different ways to refer to them, if you telling someone using Known how to refer to you, it has to be your URL, if its someone on Mastodon, its another way. The other issue is that some people don't even have access to the .well-known folder on their server. This can be a huge limitation for them sadly.</p>\n\n<p>So I was hoping to start here. Can everyone give some general feedback of webfinger.</p>\n\n<ul><li>\n\t<p>Does it do everything you need?</p>\n\t</li>\n\t<li>\n\t<p>Why did you have to rate limit it?</p>\n\t</li>\n\t<li>\n\t<p>Are there any problems you have with it?</p>\n\t</li>\n\t<li>\n\t<p>Do you have any ideas on alternative ways this could work? For example, I could see being able to look up users by either @user@domain.com, @domain.com (if its a single user domain, or @domain.com/user, etc. Then as long as the account is fetched in the same way (either parsing out the microformats from that page, or use content negotiation to get an alternative formats), you would be good to go.</p>\n\t</li>\n</ul><p>Sorry for the long post, just wanted to get anyone who cares up to speed.</p>\n\n<p>Originally Posted at <a href=\"https://discourse.joinmastodon.org/t/federation-with-social-web-in-general/352\">https://discourse.joinmastodon.org/t/federation-with-social-web-in-general/352</a></p>"
},
"_id": "81",
"_source": "9",
"_is_read": true
}
Hi! I saw your like and your re-webmention (because the picture is broken). I think I should've found the right author using all the steps on /authorship – XRay does find it and I'm thinking about switching to using that for my mentions.
What I did see on your side, however, is that you have a p-author outside of any h-*.
I think my site would've found your h-card if it was the first thing on your homepage, or if you would've extended your h-entry to include that p-author h-card. But that only makes your site easier to parse, I should've found it with this already :)
{
"type": "entry",
"published": "2017-06-02T13:23:38+0000",
"url": "https://seblog.nl/2017/06/02/4/reply",
"in-reply-to": [
"https://j4y.co/p/20170601171210_59304aeaad63f"
],
"content": {
"text": "Hi! I saw your like and your re-webmention (because the picture is broken). I think I should've found the right author using all the steps on /authorship \u2013 XRay does find it and I'm thinking about switching to using that for my mentions.\nWhat I did see on your side, however, is that you have a p-author outside of any h-*.\nI think my site would've found your h-card if it was the first thing on your homepage, or if you would've extended your h-entry to include that p-author h-card. But that only makes your site easier to parse, I should've found it with this already :)",
"html": "<p>Hi! I saw your like and your re-webmention (because the picture is broken). I think I should've found the right author using all the steps on <a href=\"http://indieweb.org/authorship\">/authorship</a> \u2013 XRay does find it and I'm thinking about switching to using that for my mentions.</p>\n<p>What I did see on your side, however, is that you have a <code>p-author</code> outside of any <code>h-*</code>.</p>\n<img src=\"https://aperture-proxy.p3k.io/c4773a9dbf34c15db20d3b4815287c634da96197/68747470733a2f2f7365626c6f672e6e6c2f636f6e74656e742f323031372f3135332f3133323333382d342f6a34792d6d66322e6a7067\" alt=\"\" /><p>I think my site would've found your h-card if it was the first thing on your homepage, or if you would've extended your <code>h-entry</code> to include that <code>p-author h-card</code>. But that only makes your site easier to parse, I should've found it with this already :)</p>"
},
"post-type": "reply",
"_id": "1367162",
"_source": "1366",
"_is_read": true
}
Comparing Aaron Parecki's flight on his website to the one on Flight24, during breakfast with @calum_ryan #indieweb #returninghome
{
"type": "entry",
"published": "2017-05-22T07:06:05+0000",
"url": "https://seblog.nl/2017/05/22/1/comparing-flights",
"category": [
"indieweb",
"returninghome"
],
"photo": [
"https://aperture-proxy.p3k.io/7b0b4c6dc3547870c5dc8434aba3197966cb1148/68747470733a2f2f7365626c6f672e6e6c2f7468756d62732f323031372f3134322f312f70687079627a6469362d31303030783735302d626c75722e6a7067"
],
"syndication": [
"https://twitter.com/Sebsel/status/866551236878839808"
],
"content": {
"text": "Comparing Aaron Parecki's flight on his website to the one on Flight24, during breakfast with @calum_ryan #indieweb #returninghome",
"html": "<p>Comparing <a href=\"https://aaronparecki.com/\">Aaron Parecki</a>'s flight on his website to the one on Flight24, during breakfast with <a href=\"http://twitter.com/calum_ryan\">@calum_ryan</a> <a href=\"https://seblog.nl/category/indieweb\">#indieweb</a> <a href=\"https://seblog.nl/category/returninghome\">#returninghome</a></p>"
},
"post-type": "photo",
"_id": "1367163",
"_source": "1366",
"_is_read": true
}
I'm at #IndieWebCamp Nuremberg! Demoing Micropub :)
I later demo'ed the update query with external pictures. This picture is made by Aaron Parecki.
{
"type": "entry",
"published": "2017-05-20T09:23:49+0000",
"url": "https://seblog.nl/2017/05/20/3/i-m-at-indiewebcamp",
"category": [
"IndieWebCamp"
],
"photo": [
"https://aperture-proxy.p3k.io/01b284fff795fc7b57b710981bc685c06f355de4/68747470733a2f2f7365626c6f672e6e6c2f7468756d62732f323031372f3134302f332f70686f746f2d31303030783735302d626c75722e6a7067"
],
"syndication": [
"https://twitter.com/Sebsel/status/865860618661892096"
],
"content": {
"text": "I'm at #IndieWebCamp Nuremberg! Demoing Micropub :)\nI later demo'ed the update query with external pictures. This picture is made by Aaron Parecki.",
"html": "<p>I'm at <a href=\"https://seblog.nl/category/IndieWebCamp\">#IndieWebCamp</a> Nuremberg! Demoing Micropub :)</p>\n<p><em>I later demo'ed the update query with external pictures. This picture is made by <a href=\"https://aaronparecki.com/2017/05/20/11/\">Aaron Parecki</a>.</em></p>"
},
"post-type": "photo",
"_id": "1367164",
"_source": "1366",
"_is_read": true
}
{
"type": "entry",
"published": "2017-02-01T22:23:59+0000",
"summary": "Micro.blog Project Surges Past $65K on Kickstarter, Gains Backing from DreamHost \n \nWP Tavern \u00fcber Micro.blog, WordPress und das IndieWeb\u2026",
"url": "https://notiz.blog/2017/02/01/wp-tavern-ueber-micro-blog/",
"content": {
"text": "Micro.blog Project Surges Past $65K on Kickstarter, Gains Backing from DreamHost\n\nWP Tavern \u00fcber Micro.blog, WordPress und das IndieWeb\u2026",
"html": "<blockquote><p><a href=\"https://wptavern.com/micro-blog-project-surges-past-65k-on-kickstarter-gains-backing-from-dreamhost\">Micro.blog Project Surges Past $65K on Kickstarter, Gains Backing from DreamHost</a></p></blockquote>\n<p></p>\n<p><a href=\"https://wptavern.com/micro-blog-project-surges-past-65k-on-kickstarter-gains-backing-from-dreamhost\">WP Tavern \u00fcber Micro.blog, WordPress und das IndieWeb\u2026</a></p>"
},
"author": {
"type": "card",
"name": "Matthias Pfefferle",
"url": "https://notiz.blog/author/matthias-pfefferle/",
"photo": "https://secure.gravatar.com/avatar/75512bb584bbceae57dfc503692b16b2?s=40&d=mm&r=g"
},
"_id": "100365",
"_source": "206",
"_is_read": true
}
{
"type": "entry",
"published": "2017-01-16T10:09:03Z",
"url": "https://jeena.net/notes/803",
"name": "Jeena,\n\t\t\t\t\n\t\t\t\t\tabout 1 year ago2017-01-16 10:09:03\n\t\t\t\t\t(4)\n\t\t\t \n\t\t\t Webmention is now a W3C recommendation: https://www.w3.org/blog/news/archives/6052",
"content": {
"text": "Webmention is now a W3C recommendation: https://www.w3.org/blog/news/archives/6052",
"html": "<p></p>\n<p>Webmention is now a W3C recommendation: <a href=\"https://www.w3.org/blog/news/archives/6052\">https://www.w3.org/blog/news/archives/6052</a></p>"
},
"author": {
"type": "card",
"name": "Jeena",
"url": "https://jeena.net/",
"photo": "https://jeena.net/avatar.jpg"
},
"_id": "99955",
"_source": "201",
"_is_read": true
}
{
"type": "entry",
"published": "2016-12-01T07:10:36Z",
"url": "https://jeena.net/notes/789",
"name": "Jeena,\n\t\t\t\t\n\t\t\t\t\tover 1 year ago2016-12-01 09:33:49\n\t\t\t \n\t\t\t I like the idea of IndieWeb commitments: https://indieweb.org/2017-01-01-commitments \n\nTherefor I commit to implementing and hardening salmentions https://indieweb.org/Salmentions on my website during 2017. I also have a issue in my bugtracker for that: https://github.com/jeena/jeena.net/issues/24",
"content": {
"text": "I like the idea of IndieWeb commitments: https://indieweb.org/2017-01-01-commitments\n\nTherefor I commit to implementing and hardening salmentions https://indieweb.org/Salmentions on my website during 2017. I also have a issue in my bugtracker for that: https://github.com/jeena/jeena.net/issues/24",
"html": "<p></p>\n<p>I like the idea of IndieWeb commitments: <a href=\"https://indieweb.org/2017-01-01-commitments\">https://indieweb.org/2017-01-01-commitments</a></p>\n\n<p>Therefor I commit to implementing and hardening salmentions <a href=\"https://indieweb.org/Salmentions\">https://indieweb.org/Salmentions</a> on my website during 2017. I also have a issue in my bugtracker for that: <a href=\"https://github.com/jeena/jeena.net/issues/24\">https://github.com/jeena/jeena.net/issues/24</a></p>"
},
"author": {
"type": "card",
"name": "Jeena",
"url": "https://jeena.net/",
"photo": "https://jeena.net/avatar.jpg"
},
"_id": "99961",
"_source": "201",
"_is_read": true
}
{
"type": "entry",
"published": "2016-11-26T09:05:19Z",
"url": "https://bear.im/bearlog/2016/331/my-2017-indieweb-commitment.html",
"category": [
"indieweb,code"
],
"name": "My 2017 IndieWeb Commitment",
"content": {
"text": "Each year some of the IndieWeb folk make a commitment to launch a new feature or item on their personal sites by the start of the new year, here is the current 2017 list.\n\nMy list this year will be to close the loop for posts-replies by implementing a simple Twitter feed page where I can view my Twitter feed and then POSSE replies or new posts.\n\nThis will need me to do:\n\nCreate a python-twitter agent that gathers the twitter feed and generates a Kaku event\nCreate a template for the twitter posts that allow for replies to be created for a Twitter post\nCreate a new post event in kaku that allows for POSSE\nThe good thing is that most of this may be implementable using the micropub endpoint work I was working on earlier!\n\ntime to get coding!",
"html": "<p>Each year some of the IndieWeb folk make a commitment to launch a new feature or item on their personal sites by the start of the new year, <a href=\"https://indieweb.org/2017-01-01-commitments\">here is the current 2017 list</a>.</p>\n\n<p>My list this year will be to close the loop for posts-replies by implementing a simple Twitter feed page where I can view <a href=\"https://twitter.com/codebear/\">my Twitter feed</a> and then POSSE replies or new posts.</p>\n\n<p>This will need me to do:</p>\n\n<ul><li>Create a <a href=\"https://github.com/bear/python-twitter\">python-twitter</a> agent that gathers the twitter feed and generates a <a href=\"https://github.com/bear/kaku\">Kaku</a> event</li>\n<li>Create a template for the twitter posts that allow for replies to be created for a Twitter post</li>\n<li>Create a new post event in <a href=\"https://github.com/bear/kaku\">kaku</a> that allows for POSSE</li>\n</ul><p>The good thing is that most of this may be implementable using the micropub endpoint work I was working on earlier!</p>\n\n<p>time to get coding!</p>"
},
"author": {
"type": "card",
"name": "Mike Taylor",
"url": "https://bear.im/",
"photo": "https://bear.im/images/bear_145x145.jpg"
},
"_id": "99744",
"_source": "190",
"_is_read": true
}
{
"type": "entry",
"published": "2016-10-06T06:36:11Z",
"url": "https://jeena.net/notes/770",
"name": "Jeena,\n\t\t\t\t\n\t\t\t\t\tover 1 year ago2016-10-06 06:36:11\n\t\t\t\t\t(12)\n\t\t\t \n\t\t\t Today I will be speaking about IndieWeb at the PHP meetup in Gothenburg https://www.meetup.com/PHP-Goteborg/events/234196466/",
"content": {
"text": "Today I will be speaking about IndieWeb at the PHP meetup in Gothenburg https://www.meetup.com/PHP-Goteborg/events/234196466/",
"html": "<p></p>\n<p>Today I will be speaking about IndieWeb at the PHP meetup in Gothenburg <a href=\"https://www.meetup.com/PHP-Goteborg/events/234196466/\">https://www.meetup.com/PHP-Goteborg/events/234196466/</a></p>"
},
"author": {
"type": "card",
"name": "Jeena",
"url": "https://jeena.net/",
"photo": "https://jeena.net/avatar.jpg"
},
"_id": "99970",
"_source": "201",
"_is_read": true
}
{
"type": "entry",
"published": "2016-08-23T17:34:38Z",
"url": "https://bear.im/bearlog/2016/236/micropub-accepted-as-a-candidate-recommendation.html",
"category": [
"indieweb,code"
],
"name": "Micropub accepted as a Candidate Recommendation",
"content": {
"text": "Congratulations to Aaron on getting Micropub as a CR (Candidate Recommendation)!\n\nIt makes me very happy to see something that came from the Indieweb community start to become a standard, it means the community is working together to ensure implementations are functional and useful!",
"html": "<p>Congratulations to <a href=\"https://aaronparecki.com\">Aaron</a> on getting <a href=\"https://aaronparecki.com/2016/08/23/2/micropub-cr\">Micropub as a CR (Candidate Recommendation)!</a></p>\n\n<p>It makes me very happy to see something that came from the <a href=\"https://indieweb.org\">Indieweb</a> community start to become a standard, it means the community is working together to ensure implementations are functional and useful!</p>"
},
"author": {
"type": "card",
"name": "Mike Taylor",
"url": "https://bear.im/",
"photo": "https://bear.im/images/bear_145x145.jpg"
},
"_id": "99745",
"_source": "190",
"_is_read": true
}
{
"type": "entry",
"published": "2016-08-03T06:10:16Z",
"rsvp": "yes",
"url": "https://bear.im/bearlog/2016/216/indiewebcamp-nyc2.html",
"category": [
"indieweb"
],
"in-reply-to": [
"http://2016.indieweb.org/nyc2"
],
"name": "IndieWebCamp NYC2",
"content": {
"text": "The second New York City IndieWebCamp is fast approaching and i'm hoping I will be able to make it but i'm still going to RSVP yes to IndieWeb NYC2",
"html": "<p>The second New York City IndieWebCamp is fast approaching and i'm hoping I will be able to make it but i'm still going to RSVP yes to <a href=\"http://2016.indieweb.org/nyc2\" class=\"u-in-reply-to\">IndieWeb NYC2</a></p>"
},
"author": {
"type": "card",
"name": "Mike Taylor",
"url": "https://bear.im/",
"photo": "https://bear.im/images/bear_145x145.jpg"
},
"_id": "99746",
"_source": "190",
"_is_read": true
}
{
"type": "entry",
"published": "2016-07-31T03:30:43Z",
"url": "https://bear.im/bearlog/2016/213/kaku-now-supports-micropub-via-json.html",
"category": [
"indieweb,code"
],
"name": "Kaku now supports Micropub via JSON",
"content": {
"text": "I was in need of some serious distracting today and I also wanted to get my Micropub handling within Kaku cleaned up and further tested because I just know that Aaron will soon have Micropub Rocks! active soon.\n\nSo yea, after about 6 hrs of refactoring and thinking and testing... Kaku now supports:\n\nMicropub CREATE using old-school params\nMicropub CREATE using JSON\nMicropub UPDATE (replace) using JSON for content\nSoon I'll have UPDATE (replace) working with other fields and also UPDATE (add|delete).\n\nAlso need to look into DELETE now - gotta go read the specs...",
"html": "<p>I was in need of some serious distracting today and I also wanted to get my <a href=\"https://www.w3.org/TR/micropub\">Micropub</a> handling within <a href=\"https://github.com/bear/kaku\">Kaku</a> cleaned up and further tested because I just know that <a href=\"https://aaronparecki.com/\">Aaron</a> will soon have <a href=\"https://micropub.rocks\">Micropub Rocks!</a> active soon.</p>\n\n<p>So yea, after about 6 hrs of refactoring and thinking and testing... Kaku now supports:</p>\n\n<ul><li>Micropub CREATE using old-school params</li>\n<li>Micropub CREATE using JSON</li>\n<li>Micropub UPDATE (replace) using JSON for content</li>\n</ul><p>Soon I'll have UPDATE (replace) working with other fields and also UPDATE (add|delete).</p>\n\n<p>Also need to look into DELETE now - gotta go read the specs...</p>"
},
"author": {
"type": "card",
"name": "Mike Taylor",
"url": "https://bear.im/",
"photo": "https://bear.im/images/bear_145x145.jpg"
},
"_id": "99747",
"_source": "190",
"_is_read": true
}
{
"type": "entry",
"published": "2016-06-27T07:35:25Z",
"url": "https://bear.im/bearlog/2016/179/thoughts-on-a-distributed-indieweb-chat.html",
"category": [
"code,indieweb"
],
"name": "Thoughts on a distributed Indieweb chat",
"content": {
"text": "The other night while talking to some of the Indieweb community I had one of those aha! moments you think only happen in movies :)\n\nI was describing how I use XMPP to have a lot of different streams of data flow to a terminal client that I pretty much use as a dashboard - different bots and agents listen to Twitter feeds, poll the few atom feeds I still follow and other sources of notifications and then they are sent to different Multi-User-Chat (MUC) rooms on my XMPP server (Prosody) based on filters.\n\nThis type of setup is something i've been working on for decades and i've always had a few different iterations going as I learn about new tech or even new languages: the first version of it was in Perl and now most of it is in Python. I have tried to envision what this would require before but always got bogged down in the translations required to move messages from one service (silo) to another.\n\nThen it struck me that we could now use some of the core Indieweb protocols to enable a distributed chat environment that doesn't (necessarily) require a central server or hub.\n\nNow I'm wondering if we couldn't use simple text with some HTML+MF2 for the required metadata - this would allow a lot of the things that we in the Indieweb community have been working to be used to handle the publication (micropub, syndicate-to), notification (webmention, PuSH) and consumption (h-feed)!\n\nEncouraged by Tantek I captured on the Indieweb Wiki most of the brainstorming from that night and I started to work getting my own site to syndicate notes to a prototype distribution hub that will allow me to see if it's realistic to have many people syndicate their own chat messages to a topic and then enable consumption of that topic in a way that feels like a chat room.\n\nPretty cool stuff!",
"html": "<p>The other night while talking to some of the <a href=\"http://indiewebcamp.com/irc\">Indieweb community</a> I had one of those aha! moments you think only happen in movies :)</p>\n\n<p>I was describing how I use <a href=\"https://xmpp.org\">XMPP</a> to have a lot of different streams of data flow to a terminal client that I pretty much use as a dashboard - different bots and agents listen to Twitter feeds, poll the few atom feeds I still follow and other sources of notifications and then they are sent to different <a href=\"http://xmpp.org/about/technology-overview.html#muc\">Multi-User-Chat (MUC)</a> rooms on my XMPP server (<a href=\"https://prosody.im\">Prosody</a>) based on filters.</p>\n\n<p>This type of setup is something i've been working on for decades and i've always had a few different iterations going as I learn about new tech or even new languages: the first version of it was in Perl and now most of it is in Python. I have tried to envision what this would require before but always got bogged down in the translations required to move messages from one service (silo) to another.</p>\n\n<p>Then it struck me that we could now use some of the core Indieweb protocols to enable a distributed chat environment that doesn't (necessarily) require a central server or hub.</p>\n\n<p>Now I'm wondering if we couldn't use simple text with some HTML+MF2 for the required metadata - this would allow a lot of the things that we in the Indieweb community have been working to be used to handle the publication (<a href=\"http://indiewebcamp.com/micropub\">micropub</a>, syndicate-to), notification (<a href=\"http://indiewebcamp.com/webmention\">webmention</a>, <a href=\"http://indiewebcamp.com/push\">PuSH</a>) and consumption (<a href=\"http://indiewebcamp.com/h-feed\">h-feed</a>)!</p>\n\n<p>Encouraged by <a href=\"http://tantek.com/\">Tantek</a> I captured on the Indieweb Wiki <a href=\"http://indiewebcamp.com/chat\">most of the brainstorming from that night</a> and I started to work getting my own site to syndicate <a href=\"http://indiewebcamp.com/note\">notes</a> to a prototype distribution hub that will allow me to see if it's realistic to have many people syndicate their own chat messages to a topic and then enable consumption of that topic in a way that feels like a chat room.</p>\n\n<p>Pretty cool stuff!</p>"
},
"author": {
"type": "card",
"name": "Mike Taylor",
"url": "https://bear.im/",
"photo": "https://bear.im/images/bear_145x145.jpg"
},
"_id": "99750",
"_source": "190",
"_is_read": true
}
{
"type": "entry",
"published": "2016-06-04T18:51:10Z",
"url": "https://bear.im/bearlog/2016/156/bearbones.html",
"category": [
"indieweb"
],
"name": "bearbones",
"content": {
"text": "so GWG named his design bearbones\nthanks David!",
"html": "<p>so GWG named his <a href=\"https://david.shanske.com/\">design bearbones</a>\nthanks David!</p>"
},
"author": {
"type": "card",
"name": "Mike Taylor",
"url": "https://bear.im/",
"photo": "https://bear.im/images/bear_145x145.jpg"
},
"_id": "99752",
"_source": "190",
"_is_read": true
}
{
"type": "entry",
"published": "2016-06-04T18:46:13Z",
"url": "https://bear.im/bearlog/2016/156/replying-to-will-norris.html",
"category": [
"indieweb"
],
"name": "replying to will norris",
"content": {
"text": "this is a reply to Will",
"html": "<p>this is a reply to <a href=\"https://willnorris.com/2016/06/indieweb-demo\">Will</a></p>"
},
"author": {
"type": "card",
"name": "Mike Taylor",
"url": "https://bear.im/",
"photo": "https://bear.im/images/bear_145x145.jpg"
},
"_id": "99753",
"_source": "190",
"_is_read": true
}
{
"type": "entry",
"author": {
"name": "Will Norris",
"url": "https://willnorris.com/",
"photo": null
},
"url": "https://willnorris.com/2016/06/indieweb-demo",
"published": "2016-06-04T11:44:49-07:00",
"content": {
"html": "<p>Demoing my simple publishing workflow at IndieWeb Summit 2016.</p>",
"text": "Demoing my simple publishing workflow at IndieWeb Summit 2016."
},
"name": "IndieWeb Summit 2016 Demo",
"_id": "124199",
"_source": "248",
"_is_read": true
}
{
"type": "entry",
"published": "2016-05-26T14:19:33Z",
"url": "https://jeena.net/notes/693",
"name": "Jeena,\n\t\t\t\t\n\t\t\t\t\talmost 2 years ago2016-05-26 14:19:33\n\t\t\t\t\t(3)\n\t\t\t \n\t\t\t @bagder we in the IndieWebCamp community use the word 'curlable' http://indiewebcamp.com/curlable",
"content": {
"text": "@bagder we in the IndieWebCamp community use the word 'curlable' http://indiewebcamp.com/curlable",
"html": "<p></p>\n<p><a href=\"https://twitter.com/bagder\">@bagder</a> we in the IndieWebCamp community use the word 'curlable' <a href=\"http://indiewebcamp.com/curlable\">http://indiewebcamp.com/curlable</a></p>"
},
"author": {
"type": "card",
"name": "Jeena",
"url": "https://jeena.net/",
"photo": "https://jeena.net/avatar.jpg"
},
"_id": "99989",
"_source": "201",
"_is_read": true
}
{
"type": "entry",
"author": {
"name": "Will Norris",
"url": "https://willnorris.com/",
"photo": null
},
"url": "https://willnorris.com/2016/05/indieweb-summit",
"published": "2016-05-25T12:44:41-07:00",
"content": {
"html": "<img src=\"https://willnorris.com/indiewebcamp-logo-lockup-color.svg\" alt=\"\" /><p>I\u2019ll be attending <a href=\"http://2016.indieweb.org/\">IndieWeb Summit</a> in Portland next week, probably working on the\n<a href=\"https://willnorris.com/go/microformats\">go microformats library</a> which I started focusing on a few weeks ago as part of a\nwebmention service I\u2019ve been thinking about lately. As I\u2019ve been working on that library though,\nI\u2019ve found a few discrepancies between the different popular microformat libraries, so there\u2019s a\npretty good chance I\u2019ll spend at least a little time building a little service to compare the\nresults from those.</p>",
"text": "I\u2019ll be attending IndieWeb Summit in Portland next week, probably working on the\ngo microformats library which I started focusing on a few weeks ago as part of a\nwebmention service I\u2019ve been thinking about lately. As I\u2019ve been working on that library though,\nI\u2019ve found a few discrepancies between the different popular microformat libraries, so there\u2019s a\npretty good chance I\u2019ll spend at least a little time building a little service to compare the\nresults from those."
},
"name": "Attending IndieWeb Summit 2016",
"_id": "124200",
"_source": "248",
"_is_read": true
}
{
"type": "entry",
"published": "2016-05-09T00:01:18Z",
"url": "https://jeena.net/notes/650",
"name": "Jeena,\n\t\t\t\t\n\t\t\t\t\talmost 2 years ago2016-05-09 00:01:18\n\t\t\t\t\t(2)\n\t\t\t \n\t\t\t Watching some of the streamed stuff from the IndieWebCamp in Duesseldorf this weekend, one of the good things is that you can fast forward stuff which are slow or you're not interested in :D \n\nhttps://www.youtube.com/watch?v=qc1sG6eu0So",
"content": {
"text": "Watching some of the streamed stuff from the IndieWebCamp in Duesseldorf this weekend, one of the good things is that you can fast forward stuff which are slow or you're not interested in :D\n\nhttps://www.youtube.com/watch?v=qc1sG6eu0So",
"html": "<p></p>\n<p>Watching some of the streamed stuff from the IndieWebCamp in Duesseldorf this weekend, one of the good things is that you can fast forward stuff which are slow or you're not interested in :D</p>\n\n<p><a href=\"https://www.youtube.com/watch?v=qc1sG6eu0So\">https://www.youtube.com/watch?v=qc1sG6eu0So</a></p>"
},
"author": {
"type": "card",
"name": "Jeena",
"url": "https://jeena.net/",
"photo": "https://jeena.net/avatar.jpg"
},
"_id": "100002",
"_source": "201",
"_is_read": true
}
{
"type": "entry",
"published": "2016-05-03T05:42:19Z",
"url": "https://jeena.net/notes/644",
"name": "Jeena,\n\t\t\t\t\n\t\t\t\t\talmost 2 years ago2016-05-03 05:45:32\n\t\t\t\t\t(6)\n\t\t\t \n\t\t\t Using decentralised IndieWeb technologies looks much more like an option now, doesn't it? \n\n\"WhatsApp, Used by 100 Million Brazilians, Was Shut Down Nationwide Today by a Single Judge\" \n\nhttps://theintercept.com/2016/05/02/whatsapp-used-by-100-million-brazilians-was-shut-down-nationwide-today-by-a-single-judge/",
"content": {
"text": "Using decentralised IndieWeb technologies looks much more like an option now, doesn't it?\n\n\"WhatsApp, Used by 100 Million Brazilians, Was Shut Down Nationwide Today by a Single Judge\"\n\nhttps://theintercept.com/2016/05/02/whatsapp-used-by-100-million-brazilians-was-shut-down-nationwide-today-by-a-single-judge/",
"html": "<p></p>\n<p>Using decentralised IndieWeb technologies looks much more like an option now, doesn't it?</p>\n\n<p>\"WhatsApp, Used by 100 Million Brazilians, Was Shut Down Nationwide Today by a Single Judge\"</p>\n\n<p><a href=\"https://theintercept.com/2016/05/02/whatsapp-used-by-100-million-brazilians-was-shut-down-nationwide-today-by-a-single-judge/\">https://theintercept.com/2016/05/02/whatsapp-used-by-100-million-brazilians-was-shut-down-nationwide-today-by-a-single-judge/</a></p>"
},
"author": {
"type": "card",
"name": "Jeena",
"url": "https://jeena.net/",
"photo": "https://jeena.net/avatar.jpg"
},
"_id": "100003",
"_source": "201",
"_is_read": true
}