16 Matching Annotations
  1. Dec 2022
    1. https://schopie1.commons.msu.edu/2022/12/05/microblogging_with_mastodon/

      OMG! There is so much to love here about these processes and to see people in the wild experimenting with them and figuring them out.

      Scott, you are not alone! There are lots of us out here doing these things, not only with WordPress but a huge variety of other platforms. There are many ways to syndicate your content depending on where it starts its life.

      In addition to Jim Groom and a huge group of others' work on A Domain of One's Own, there's also a broader coalition of designers, developers, professionals, hobbyists, and people of all strips working on these problems under the name of IndieWeb.

      For some of their specific work you might appreciate the following:<br /> - https://indieweb.org/Indieweb_for_Education - https://indieweb.org/A_Domain_of_One%27s_Own - https://indieweb.org/academic_samizdat - https://indieweb.org/WordPress - https://indieweb.org/Category:syndication

      Incidentally, I wrote this for our friend Kathleen Fitzpatrick last week and I can't wait to see what she's come up with over the weekend and the coming weeks. Within the IndieWeb community you'll find people like Ben Werdmuller who created large portions of both WithKnown and Elgg and Aram Zucker-Scharff who helped to create PressForward.

      I'm thrilled to see the work and huge strides that Humanities Commons is making some of these practices come to fruition.

      If you're game, perhaps we ought to plan an upcoming education-related popup event as an IndieWebCamp event to invite more people into this broader conversation?

      If you have questions or need any help in these areas, I'm around, but so are hundreds of friends in the IndieWeb chat: https://chat.indieweb.org.

      I hope we can bring more of these technologies to the masses in better and easier-to-use manners to lower the technical hurdles.

    1. https://shkspr.mobi/blog/2022/12/the-ethics-of-syndicating-comments-using-webmentions/

      Not an answer to the dilemma, though I generally take the position of keeping everything unless someone asks me to take it down or that I might know that it's been otherwise deleted. Often I choose not to delete my copy, but simply make it private and only viewable to me.

      On the deadnaming and related issues, it would be interesting to create a webmention mechanism for the h-card portions so that users might update these across networks. To some extent Automattic's Gravatar system does this in a centralized manner, but it would be interesting to see it separately. Certainly not as big an issue as deadnaming, but there's a similar problem on some platforms like Twitter where people will change their display name regularly for either holidays, or lately because they're indicating they'd rather be found on Mastodon or other websites.

      The webmention spec does contain details for both editing/deleting content and resending webmentions to edit and/or remove the original. Ideally this would be more broadly adopted and used in the future to eliminate the need for making these choices by leaving the choice up to the original publisher.

      Beyond this, often on platforms that don't have character limits (Reddit for example), I'll post at the bottom of my syndicated copy of content that it was originally published on my site (along with the permalink) and explicitly state that I aggregate the replies from various locations which also helps to let people know that they might find addition context or conversation at the original post should they be interested. Doing this on Twitter, Mastodon, et al is much harder due to space requirements obviously.

      While most responses I send would fall under fair use for copying, I also have a Creative Commons license on my text in an effort to help others feel more comfortable with having copies of my content on their sites.

      Another ethical layer to this is interactions between sites which both have webmentions enabled. To some extent this creates an implicit bi-directional relationship which says, I'm aware that this sort of communication exists and approve of your parsing and displaying my responses.

      The public norms and ethics in this area will undoubtedly evolve over time, so it's also worth revisiting and re-evaluating the issue over time.

  2. Aug 2022
    1. Write once. Publish everywhere.Write in our simple editor and publish natively to Twitter, LinkedIn, Medium, and your very own Typeshare Social Blog.

      Syndication as a selling point.


    1. This is a living document. Ideas or feedback can be contributed through commenting directly using Hypothes.is which will create issues in the Github repo or you can directly create an issue: https://github.com/FAIRIslandProject/Generic-Place-based-Data-Policy/issues

      How awesome is this sort of integration? If one can use annotations to create issues within Github, it should be relatively easy for websites to do similar integrations to allow the use of Hypothes.is as a native commenting system on website pages. The API could be leveraged with appropriate URL wildcard patterns to do this.

      I have heard of a few cases of people using Github issue queues as comments sections for websites, and this dovetails well into that space.

      How might the Webmention spec be leveraged or abstracted to do similar sorts of communication work?

  3. May 2022
  4. Oct 2021
    1. a way to transparently discover related blogs that avoids hidden algorithms

      Bristly pop cultural misuse of the term "algorithm" notwithstanding, a better solution that I haven't come across anyone else mention: make them explicit, not hidden.

      When it look like Dat might've had enough steam to take off (ca. 2017–2018), I wrote a draft straw proposal for how to solve the "discovery problem" with e.g. Fritter—i.e. the problem that because you only "receive" replies and other messages by checking the feeds of the people you're following, you'll be unable to reply engage with strangers who appear (or have a stranger engage with you in their thread) unless something happens like a mutual acquaintance alerting you out of band ("hey, did you see @foo's reply dat://foo.example.net/posts/ukifxdgbh.json?").

      The idea is that there is a special kind of feed operated by some service provider that specializes in doing exactly that. If you find Facebook valuable, for example, then you are free to opt in and subscribe to the Facebook analog that pays attention to all feeds and works to surface interesting content for you. Under this model, unlike the Facebook regime, "leaving" is as simple as unsubscribing to that feed (and going with a different provider if you want).

  5. May 2021
    1. many people have attached sensors

      This differs from LDN, where the the annotation service is squarely under the control of the document author. This is also using sensor attachment in a different sense that the way it first appears above. The application is more akin to RSS. With RSS, the links exist in some other "document" (or something like it; generall can be modeled as OPML, even if it's really, say, an sqlite store).

  6. Feb 2021
  7. Oct 2020
    1. What I dwell on the most regarding syndication is the Twitter stuff. I look back at the analytics on this site at the end of every year and look at where the traffic came from — every year, Twitter is a teeny-weeny itty-bitty slice of the pie. Measuring traffic alone, that’s nowhere near the amount of effort we put into making the stuff we’re tweeting there. I always rationalize it to myself in other ways. I feel like Twitter is one of the major ways I stay updated with the industry and it’s a major source of ideas for articles.

      So it sounds like Twitter isn't driving traffic to his website, but it is providing ideas and news. Given this I would syndicate content to Twitter as easily and quickly as possible, use webmentions to deal with the interactions and then just use the Twitter timeline for reading and consuming and nothing else.

    1. As someone who writes social media for work, I am deeply rooted in the practice of writing a unique intro when I share a post to Twitter, not directly syndicating it with whatever text I started the article with. For me that feels good enough (not saving that unique share to my site) since including the link means any likes and comments about the article come back to my blog thanks to Bridgy, but maybe someone will convince me otherwise ;)

      I'll often share articles to Twitter and don't necessarily do a 1-to-1 match of the syndicated copy on Twitter. Usually I'll excerpt a piece that ends up appearing on Twitter with a link back to the article. I generally presuppose that if they're interested, they'll click through and read otherwise they're bookmarking it or sharing the link with others, so those interactions coming back to the original are always fine with me.