2. In reply to a post on waterpigs.co.uk


    Figure out how you want to fit into the network.

    POSSE iconPOSSE icon

    320px-POSSE-2012-312.jpeg

    POSSE is an abbreviation for Publish (on your) Own Site, Syndicate Elsewhere, the practice of posting content on your own site first, then publishing copies or sharing links to third parties (like social media silos) with original post links to provide viewers a path to directly interacting with your content.

    ▶️ watch Zach’s 1min* video intro to POSSE

    Why

    Let your friends read your posts, their way. POSSE lets your friends keep using whatever they use to read your stuff (e.g. social media silos like Instagram, Tumblr, Twitter, Neocities, etc.).

    Stay in touch with friends now, not some theoretical future. POSSE is about staying in touch with current friends now, rather than the potential of staying in touch with friends in the future.

    Friends are more important than federation. By focusing on relationships that matter to people rather than architectural ideals, from a human perspective, POSSE is more important than federation. Additionally, if federated approaches take a POSSE approach first, they will likely get better adoption (everyone wants to stay in touch with their friends), and thereby more rapidly approach that federated future.

    POSSE is beyond blogging. It’s a key part of why and how the IndieWeb movement is different from just “everyone blog on their own site”, and also different from “everyone just install and run (YourFavoriteSocialSoftware)” etc. monoculture solutions.

    Why In General

    POSSE is considered a robust and preferable syndication model for the following reasons:

    • Reduce 3rd party dependence. By posting directly to your own site, you’re not dependent on 3rd Party services to do so — if you can access your site, you can publish your content. On the contrary with PESOS, when the 3rd party site is down, you are unable to add content.
    • Ownership. By posting first on your own site, you create a direct ownership chain that can be traced back to you without any intervening 3rd party services (silos) TOS’s getting in the way (which is a vulnerability of PESOS).
    • Own canonical URLs to your content. Canonical URLs to your content are on your domain.
    • Copies can cite the original. By posting content first to your own site (and thus creating a permalink for it), copies that you post on 3rd Party services can link or cite the original on your site (see syndication_formats and POSSE Notes to Twitter)
    • Better search. Searching public content on your own domain (with any web search engine of your choice) works better than depending on silos exclusively to search your posts (e.g. Twitter for a while only showed recent tweets in search results. Facebook still has very poor search results).
    • backfeed can be used to pull in (reverse syndicate) responses from other services
    • allows taking advantage of other services’ social layers and aggregation features while storing the canonical copy of your content on your own site
    • …

    Why Link To Your Original

    Common POSSE practice is to link from POSSE copies to your original, using a permashortlink. Here are a few reasons why:

    • Discovery of your original content. discovery of your original content from the copies on 3rd party services is enabled by the permashortlinks to your originals posted on said services
    • Subvert spammers who copy your posts. When spammers (e.g. @sin3rss) mindlessly copy from your POSSE copies and repost, they also copy the link back to the original, and thus provide more distribution for people to find and view your original post. “2011-01-09 internet aikido” of a sort.
    • Better ranking for your original posts. If/when your POSSE copies are themselves copied by others and (re)posted elsewhere (e.g. manual retweets, RSS bots etc.), when the copies link to your original posts, search engines figure that out by following those links back to the original and ranking it higher.

    How to

    How to implement

    This section is for web developers implementing POSSE.

    In General

    In general, when your content posting software posts something, it should also post a copy to the silo destinations of your choice, with an original post link (e.g. permashortlink or permashortcitation) back to your original.

    The details of how to do so vary per destination. See the silo-specific sections below.

    Once you have posted the copy to the silo, you should:

    • link to the syndicated copy from the original in a posts-elsewhere section on your post.

    User Interface

    The best user interface (UI) is automatic, dependable, and invisible. If you can implement POSSEing in a way that always does exactly what you want, predictably, then no explicit UI is needed.

    Preview

    One way to provide more predictability and inspire confidence is to show what will be POSSEd (within the limitations of the destination) as a preview before publishing

    (needs screenshot)

    Twitter

    Twitter is perhaps the most popular POSSE destination and a good place to start.

    If you can start posting notes (tweets) to your own site and POSSEing to Twitter, instead of posting directly to Twitter, you have taken a big step towards owning your data.

    Details:

    • API Access – posting new tweets works nicely due to permanent API tokens, and the return value contains a URL to the posted
      • As of 2022-11, Twitter is rejecting new API access for applications used to POSSE/backfeed on the grounds that they may violate twitter’s rules and/or policies — Barnaby Walters
    • Supports very complete web action endpoints, so semi-manual posting is easy to implement
      • What are these endpoints? Is this still the case in 2022? — Barnaby Walters

    See POSSE to Twitter for details on how to POSSE both notes and articles (blog posts) to Twitter.

    Facebook

    There are two options for POSSEing to Facebook currently:

    Medium

    WordPress

    • How does veganstraightedge.com do it? (all his articles are manually POSSEd to WordPress.com)
    • Chris Aldrich uses a WordPress plugin WordPress Crosspost to POSSE from a self-hosted WordPress install to WordPress.com.

    Ghost

    • a community developed open source tool is available on GitHub; the tool uses Ghost webhooks to receive latest published post in JSON format and syndicates the posts to Mastodon and Bluesky accounts

    Plain Text Notes

    Some destinations (e.g. SMS or push notifications) may require a pure plain text representation.

    Software

    Software and libraries to implement POSSE:

    • PHP
      • The POSSE namespace in php-helpers (might be moved to a separate package) contains various truncation, preparation and syndication functions including HTML => plaintext µblog syntax converter
    • Python
      • SiloRider is a command-line tool, implemented in Python, that lets you implement POSSE to various services (Twitter and Mastodon as of 2018-08-01).
      • Feed2Toot is another command-line python tool that parses any number of RSS feeds and posts their content on ActivityPub based services (tested with: Mastodon, Pleroma). Contains some neat bells and whistles like advanced post filtering, numerous options for feed parsing and toot formatting.
    • Docker

    Services

    Publishing Flows

    There’s at least two ways to implement a POSSE content posting flow:

    Client to site to silo
    • The user writes a piece of content using a publishing client
      • Optional: client provides UI for selecting which 3rd party services to push to if it knows about them, with optional customizations for per service
    • Having finished the content, the user publishes content to their server (optionally: with metadata of which 3rd party services and any customizations thereof)
      • Optional: client can generate a permalink knowing the state of the server, and publish to that permalink
    • The server publishes the content, generates a permalink and summary (and/or customized content suited to 3rd party services) if necessary
    • The server posts copies with permalinks to 3rd party services

    Advantages:

    • User only has to interact with one site over the internet, their own
    • Syndication can be done fully automatically by the server

    Disadvantages:

    Client to site and silo
    • The user writes a piece of content using a publishing client
    • Having finished the content, the user publishes it to their server
    • The client queries the server for the URL of the content it just pushed
    • The publishing client presents the user with an interface for selecting:
      • Which 3rd party services to publish to
      • The exact content published to the services, pre-filled with a summary based on the produced content
    • The user selects the services and submits the form
    • The publishing client posts the content summaries out to the 3rd party services

    Advantages:

    • More user control over timing and editing of copies of content to 3rd party services

    Disadvantages:

    • Syndication requires a manual step each time
    • Dependent on client connectivity directly to 3rd party services (problematic in flakey mobile situations, or when client is publishing using domain-censored internet access).

    IndieWeb Examples

    The following IndieWebCamp participants’ sites support a POSSE architecture. If you have an implementation, add it, make screenshots or a screencast or blog about it and post the details/link here. In date order (earliest first) :

    Tantek

    Tantek.com as of 2010-01-01[1] (2010-01-26 Twitter syndication started[2] and caught up[3][4]). Tantek Çelik implemented POSSE in Falcon on tantek.com.

    • all self-hosted posts are openly with PuSH v0.4 + h-feed and Atom real-time syndicated with a PubsubHubbub hub to StatusNet, other subscribers etc. (also to Google Buzz til it shutdown)
    • note (and article titles), reply, RSVP posts are snowflake copied by the personal site server to Twitter with permashortlink citation links/references (see Whistle for details) back to the original. Copies of notes to Twitter are also automatically recopied from there to Facebook.
      • RSVPs to Facebook events are “copied” (more like propagated) to Facebook using Bridgy publish
    • likes of tweets are “copied” (more like propagated) to Twitter using Bridgy publish

    Barnaby Walters

    Waterpigs.co.uk as of 2012-03-12. Barnaby Walters implemented POSSE over at waterpigs.co.uk

    • as of 2012-09-25 all collections (notes, articles, activity) are PuSH-subscribable feeds.
    • Using the Client to Server to 3rd Parties flow —Waterpigs.co.uk 06:08, 25 September 2012 (PDT)
    • Syndicating to Twitter + Facebook
    • As of 2014-06-19 Taproot can now optionally post additional POSSE tweets when updating a note or article — example of updated note and POSSE tweet for the update. Note that Bridgy successfully backfeeds silo interactions from the update tweet as well as the original POSSE tweet

    Brennan Novak

    brennannovak.com as of 2012-07-01[5][6]. Brennan Novak implemented POSSE on his site brennannovak.com with copies posted to Twitter and Facebook

    Aaron Parecki

    aaronparecki.com as of 2012-08-19[7][8]. Aaron Parecki implemented POSSE on his site aaronparecki.com with copies posted to Twitter containing permashortlinks back to originals on his own site.

    Sandeep Shetty

    User:Sandeep.io First post POSSE’d on 2012-11-05. I primarily syndicate to Twitter using a very lo-fi solution of adding silo (Facebook, Twiiter, Google+) provided share links to each post that I can manually click to prefill content, edit and post. I’ve avoided API integration because of the extensive experience I’ve had using Facebook API and dealing with it’s random changes. “Integration” has high costs sometimes so I keep it as simple as possible.

    Ben Werdmuller

    werd.io as of 2013-05-31 [9]. Ben Werdmuller implemented POSSE in his idno platform via plugins. New content has an associated Activity Streams object type; POSSE plugins listen for post events associated with those object types and syndicate appropriately.

    • Notes and articles are syndicated to Twitter and Facebook
    • Images are syndicated to Facebook, Flickr and Twitter
    • Places are syndicated to Foursquare
    • More plugins are very easily possible; the Foursquare plugin took about an hour to build

    Shane Becker

    • Shane Becker using Dark Matter on veganstraightedge.com (since 2013-07-17[10]) with automatic rel-syndication markup on manual POSSEing:

    Glenn Jones

    glennjones.net as of 2014-01-14 Glenn Jones The blog implemented POSSE using a new version of transmat.io system. New content added to transmat is associated with objects types. A POSSE twitter plugins listens for post events syndicating content. At moment only notes are syndicated.

    Jeremy Keith

    adactio.com as of 2014-05-27 Jeremy Keith has implemented POSSE using his own custom CMS.

    Shane Hudson

    shanehudson.net as of 2014-09-19 Shane Hudson has implemented POSSE to Twitter for Craft CMS.

    • Previously working on WordPress but he was not keen on the UX.
    • Has reply contexts working but has to manually copy the ID.
    • Not yet POSSEing photos but plans to.
    • Currently he has to manually copy the tweet from the main text box to a 140 character limit tweet text box. He plans to make that automatic.

    Ravi Sagar

    http://www.ravisagar.in/blog/implementing-posse-my-site Implementing POSSE on my site as of 2018-02-21.

    • The new blogs and notes are posted on Drupal
    • http://www.ravisagar.in/rss-social.xml RSS Feed is generated for the blogs and notes tagged with “Share” keyword
    • Using Rebrandly to create shortlinks for the RSS Feed
    • Using Zapier to share the newly created rebrandly links to Twitter and Linkedin

    Ludovic Chabant

    ludovic.chabant.com as of 2018-07-30 Ludovic Chabant has implement POSSE to Twitter and Mastodon from PieCrust CMS, using SiloRider

    • SiloRider is CMS independent — it only relies on Microformats found in the published markup.
    • New articles are posted as title and link.
    • New microblogging updates are mostly copied verbatim (if the fit the external service’s character limits), and support photo posts, including multi-photo posts.

    Adam Dawkins

    adamdawkins.uk as of 2019-01-16 Adam Dawkins has implemented POSSE using his own custom CMS.

    • Notes have been POSSEd since he first started posting them on his own site, on 2019-01-16

    Examples

    Shaun Ewing

    shaun.net as of 2020-01-16 Shaun Ewing has implemented POSSE using Jekyll, and custom APIs.

    capjamesg

    capjamesg has been syndicating his notes from his own site to:

    • Twitter using brid.gy
    • micro.blog using micro.blog’s feed polling system
    • The fediverse using fed.brid.gy

    This syndication happens automatically whenever James posts a note using his Micropub client or his Microsub feed reader.

    Wojtek Powiertowski

    behindtheviewfinder.com as of 2026-01-12 has been syndicating his posts from his Ghost blog to:

    This syndication happens automatically whenever Wojtek publishes a new posts using his self-hosted posse client.

    … add more here …

    … Add a link to your POSSE–enabled site and the date you started syndicating copies of your content out to 3rd party social sharing/publishing services.

    Partial POSSE sites

    Sites which only POSSE some of their content, and still post directly to the same silo they POSSE to.

    Other partial POSSE sites:

    • User:Hupili.net implements a partial POSSE with the following setups:
      • SNSAPI is a lightweight middleware to unify the data structure and interfaces of different social networking services. It gives the scripting flexibility for developer users to manipulate social silos.
      • SNSRouter is a web UI built upon SNSAPI where one can read an aggregated timeline from different sites, mass forward messages, and update statuses on all channels.
      • As is said in one of the description paragraph above, this model is not truly POSSE. One can not (hardly) distinguish original/ syndicated status. I’m planning to put a page with permlink on my site upon each status update and then use SNSAPI to syndicate to other silos.

    Other Approaches

    COPE

    COPE is short for Create Once, Publish Everywhere (COPE), which explicitly lacks a first “Publish Once” step, and thus is more about duplicating the content across various destinations.

    Without a first “Publish Once” step on a site you “Own”, and thus lacking original post permalinks, the COPE strategy fails to actually draw people to any one canonical place to read/view your stuff, and thus all it does is grow (likely) disjoint audiences across other people’s sites.

    Articles:

    POSE

    POSE, Publish Once Syndicate Everywhere, was a broader predecessor of POSSE that also included publishing once on one particular silo, and then syndicating out to other silos.

    PESOS

    A similar but opposite approach is PESOS where content is posted first to 3rd party services and then copied/syndicated into a personal site.

    If exact copies of content are posted on both a personal site and 3rd party services, there’s no way to tell (short of comparing possibly non-existent sub-second accurate published dates) whether a site is using POSSE or PESOS. Sites can provably support POSSE by including perma(short)links in syndicated copies that link/reference back to published originals.

    PESETAS

    PESETAS is like PESOS but copying/syndicating everything to a particular silo (without any involvement of a personal site).

    For example, most silos support cross-posting to Twitter, thus you could connect everything to your Twitter account and always (auto-)cross-post there to keep a copy.

    E.g. Tumblr has a UI for cross-posting to Twitter. See Webapps StackExchange post for documentation and screenshots of UI.

    Tumblr is a better PESETAS destination however, since it is well established, allows for a wider variety of content, and allows more text, and links to URLs directly instead of linkwrapping them like Twitter does.

    Brainstorming

    CRUD

    All of the above, and to date (2013-222), POSSE has solely described syndicating the Creation of content on your site (publishing) to other sites. This model has been quite successful and perhaps may be sufficient.

    However, it is worth exploring the potential utility of a full CRUD protocol for POSSE.

    Create

    Create is the POSSE default. You create content on your site, you POSSE your creates to other sites. All of this is described above, and in silo-specific details on silo pages.

    Read

    Read as a verb is interesting when applied to POSSE.

    At a minimum, it’s useful to implement storing links to syndicated copies of your content to provide for the future possibility of reading from downstream POSSE copies.

    See:

    Actual direct uses of Reading from downstream POSSE copies:

    • reverse-syndication / backfeed of activity around the POSSE copy onto your original:

    In addition, keeping a u-syndication link to the POSSE copy enables deleting it to perform an Update or a Delete action, as described in the following sections.

    Update

    If a POSSE destination allows updates/edits, then when you edit your post, you could propagate that update to the downstream POSSE copy as well.

    • E.g. Facebook allows editing the text of a post (including any links in the text), person tags, but not the image of a photo post

    If the destination disallows updates/edits, like Twitter, it is still possible to virtually POSSE updates by deleting the POSSE tweet and reposting, i.e.:

    Consider only POSSEing updates to Twitter:

    • if no one has replied to it yet (otherwise you’d break a threaded conversation on Twitter)
    • if your changes would be shown in the truncated copy on Twitter (i.e. if your changes are past the 140 (more like 120) character horizon, no point in churning the Twitter copy).
    • within a very short time window, maybe like 2-5 minutes, because otherwise the update will be seen as a duplicate to people who are reading you on Twitter.

    All of these concerns are regarding the experience that you provide to your friends reading your tweets on Twitter, which of course should be the whole (design) reason you’re bothering to POSSE to Twitter in the first place.

    For details, see silo-specific POSSE sections:

    • Facebook: POSSE to Facebook (to-do: needs details re: edit text ok, but no photo editing, photo posts need delete/repost to simulate POSSE update)
    • Flickr: (UI supports manually updating the image of a photo post, but is that available in the API? and if so, file a Bridgy Publish feature request GitHub issue to support POSSE Update to Flickr (including the image of a photo post)
    • Twitter: POSSE to Twitter (to-do: copy the above delete/repost strategy to there)
    • …

    Delete

    Deletes seem fairly straightforward to POSSE, especially to services which themselves propagate deletes to clients.

    E.g. one can delete a note on Twitter at any point.

    Similar to updates, consider:

    • if there are already replies to a POSSE copy (or activity like favorites/retweets), consider keeping it to keep conversation threading (and others’ favorites/retweets).

    However, if you really feel like deleting the content from your site and POSSE copies (e.g. on Twitter), go ahead and do so.

    Perhaps this is an opportunity for the UI for the deletion of a post to check to see if there’s been any activity (replies, favorites, retweets) on the POSSE copy before performing the delete. One possible implementation could involve the UI informing the user of this activity (or lack of it) and reconfirming the delete request on a per-service basis.

    IndieWeb Examples

    • Grant Richmond supports POSSE deletes on twitter as of 2018-10-10, by checking if a post on his site has been unpublished / deleted and sending the appropriate api request for likes, reposts and notes.

    FAQ

    Worry about search engines and duplicates

    Q: Do we need to worry about search engines penalizing apparently duplicate posts?

    A: That’s why the POSSE copies SHOULD always link back to the originals. So that search engines can infer that the copies are just copies. Ideally POSSE copies on silos should use rel-canonical to link back to the originals, but even without explicit rel-canonical, the explicit link back to the original is a strong hint that it is an original.

    This is also an advantage of POSSE over PESOS. With PESOS – there’s no way to tell what’s the original and what’s the copy – so they do look like duplicates.

    POSSE-post-discovery and backlinks

    Q: Brid.gy can use posse-post-discovery to find the relationship between a syndicated post and the original when there is not explicit link. Does this mean I should stop adding backlinks to syndicated copies?

    A: POSSEing without a backlink is considered a last resort, and has some costs associated with it. See posse-post-discovery#Tradeoffs for more details.

    POSSE or Send Webmentions First

    In short, POSSE first, then send webmentions.

    See: Webmention FAQ: POSSE or Send Webmentions First for details and reasoning.

    Background

    Related conceptually:

    • sometime before 2014-06-21[11]: POSE (Publish Once Syndicate Everywhere) term defined at some point prior to POSSE. Conceptually it was looser than POSSE, as “once” could be interpreted as on a silo rather than your “own site”, which POSSE (and the conceptual predecessors) made explicit.

    Articles

    Articles and blog posts about POSSE, especially implementing it:

    POSSE as methodology for non-web scenarios

    POSSE git repositories

    As discussed #indieweb it is also possible POSSE your git repositories to git “silos”, such as GitHub or GitLab. An easy way of doing this was described by Christian Weiske at [12].

    Sessions

    See Also






    Source link

  3. In reply to a post on waterpigs.co.uk

    HackTech

    Share This Article
    Share Post
    Newsletter

    Sed ut perspiciatis unde.

    Subscribe
    hn.jpg
    Send to HN

    Figure out how you want to fit into the network.

    POSSE iconPOSSE icon

    320px-POSSE-2012-312.jpeg

    POSSE is an abbreviation for Publish (on your) Own Site, Syndicate Elsewhere, the practice of posting content on your own site first, then publishing copies or sharing links to third parties (like social media silos) with original post links to provide viewers a path to directly interacting with your content.

    ▶️ watch Zach’s 1min* video intro to POSSE

    Why

    Let your friends read your posts, their way. POSSE lets your friends keep using whatever they use to read your stuff (e.g. social media silos like Instagram, Tumblr, Twitter, Neocities, etc.).

    Stay in touch with friends now, not some theoretical future. POSSE is about staying in touch with current friends now, rather than the potential of staying in touch with friends in the future.

    Friends are more important than federation. By focusing on relationships that matter to people rather than architectural ideals, from a human perspective, POSSE is more important than federation. Additionally, if federated approaches take a POSSE approach first, they will likely get better adoption (everyone wants to stay in touch with their friends), and thereby more rapidly approach that federated future.

    POSSE is beyond blogging. It’s a key part of why and how the IndieWeb movement is different from just “everyone blog on their own site”, and also different from “everyone just install and run (YourFavoriteSocialSoftware)” etc. monoculture solutions.

    Why In General

    POSSE is considered a robust and preferable syndication model for the following reasons:

    • Reduce 3rd party dependence. By posting directly to your own site, you’re not dependent on 3rd Party services to do so — if you can access your site, you can publish your content. On the contrary with PESOS, when the 3rd party site is down, you are unable to add content.
    • Ownership. By posting first on your own site, you create a direct ownership chain that can be traced back to you without any intervening 3rd party services (silos) TOS’s getting in the way (which is a vulnerability of PESOS).
    • Own canonical URLs to your content. Canonical URLs to your content are on your domain.
    • Copies can cite the original. By posting content first to your own site (and thus creating a permalink for it), copies that you post on 3rd Party services can link or cite the original on your site (see syndication_formats and POSSE Notes to Twitter)
    • Better search. Searching public content on your own domain (with any web search engine of your choice) works better than depending on silos exclusively to search your posts (e.g. Twitter for a while only showed recent tweets in search results. Facebook still has very poor search results).
    • backfeed can be used to pull in (reverse syndicate) responses from other services
    • allows taking advantage of other services’ social layers and aggregation features while storing the canonical copy of your content on your own site
    • …

    Why Link To Your Original

    Common POSSE practice is to link from POSSE copies to your original, using a permashortlink. Here are a few reasons why:

    • Discovery of your original content. discovery of your original content from the copies on 3rd party services is enabled by the permashortlinks to your originals posted on said services
    • Subvert spammers who copy your posts. When spammers (e.g. @sin3rss) mindlessly copy from your POSSE copies and repost, they also copy the link back to the original, and thus provide more distribution for people to find and view your original post. “2011-01-09 internet aikido” of a sort.
    • Better ranking for your original posts. If/when your POSSE copies are themselves copied by others and (re)posted elsewhere (e.g. manual retweets, RSS bots etc.), when the copies link to your original posts, search engines figure that out by following those links back to the original and ranking it higher.

    How to

    How to implement

    This section is for web developers implementing POSSE.

    In General

    In general, when your content posting software posts something, it should also post a copy to the silo destinations of your choice, with an original post link (e.g. permashortlink or permashortcitation) back to your original.

    The details of how to do so vary per destination. See the silo-specific sections below.

    Once you have posted the copy to the silo, you should:

    • link to the syndicated copy from the original in a posts-elsewhere section on your post.

    User Interface

    The best user interface (UI) is automatic, dependable, and invisible. If you can implement POSSEing in a way that always does exactly what you want, predictably, then no explicit UI is needed.

    Preview

    One way to provide more predictability and inspire confidence is to show what will be POSSEd (within the limitations of the destination) as a preview before publishing

    (needs screenshot)

    Twitter

    Twitter is perhaps the most popular POSSE destination and a good place to start.

    If you can start posting notes (tweets) to your own site and POSSEing to Twitter, instead of posting directly to Twitter, you have taken a big step towards owning your data.

    Details:

    See POSSE to Twitter for details on how to POSSE both notes and articles (blog posts) to Twitter.

    Facebook

    There are two options for POSSEing to Facebook currently:

    Medium

    WordPress

    • How does veganstraightedge.com do it? (all his articles are manually POSSEd to WordPress.com)
    • Chris Aldrich uses a WordPress plugin WordPress Crosspost to POSSE from a self-hosted WordPress install to WordPress.com.

    Plain Text Notes

    Some destinations (e.g. SMS or push notifications) may require a pure plain text representation.

    Software

    Software and libraries to implement POSSE:

    • PHP
      • The POSSE namespace in php-helpers (might be moved to a separate package) contains various truncation, preparation and syndication functions including HTML => plaintext µblog syntax converter
    • Python
      • SiloRider is a command-line tool, implemented in Python, that lets you implement POSSE to various services (Twitter and Mastodon as of 2018-08-01).
      • Feed2Toot is another command-line python tool that parses any number of RSS feeds and posts their content on ActivityPub based services (tested with: Mastodon, Pleroma). Contains some neat bells and whistles like advanced post filtering, numerous options for feed parsing and toot formatting.
    • Docker

    Services

    Publishing Flows

    There’s at least two ways to implement a POSSE content posting flow:

    Client to site to silo
    • The user writes a piece of content using a publishing client
      • Optional: client provides UI for selecting which 3rd party services to push to if it knows about them, with optional customizations for per service
    • Having finished the content, the user publishes content to their server (optionally: with metadata of which 3rd party services and any customizations thereof)
      • Optional: client can generate a permalink knowing the state of the server, and publish to that permalink
    • The server publishes the content, generates a permalink and summary (and/or customized content suited to 3rd party services) if necessary
    • The server posts copies with permalinks to 3rd party services

    Advantages:

    • User only has to interact with one site over the internet, their own
    • Syndication can be done fully automatically by the server

    Disadvantages:

    • any?
    Client to site and silo
    • The user writes a piece of content using a publishing client
    • Having finished the content, the user publishes it to their server
    • The client queries the server for the URL of the content it just pushed
    • The publishing client presents the user with an interface for selecting:
      • Which 3rd party services to publish to
      • The exact content published to the services, pre-filled with a summary based on the produced content
    • The user selects the services and submits the form
    • The publishing client posts the content summaries out to the 3rd party services

    Advantages:

    • More user control over timing and editing of copies of content to 3rd party services

    Disadvantages:

    • Syndication requires a manual step each time
    • Dependent on client connectivity directly to 3rd party services (problematic in flakey mobile situations, or when client is publishing using domain-censored internet access).

    IndieWeb Examples

    The following IndieWebCamp participants’ sites support a POSSE architecture. If you have an implementation, add it, make screenshots or a screencast or blog about it and post the details/link here. In date order (earliest first) :

    Tantek

    Tantek.com as of 2010-01-01[1] (2010-01-26 Twitter syndication started[2] and caught up[3][4]). Tantek Çelik implemented POSSE in Falcon on tantek.com.

    • all self-hosted posts are openly with PuSH v0.4 + h-feed and Atom real-time syndicated with a PubsubHubbub hub to StatusNet, other subscribers etc. (also to Google Buzz til it shutdown)
    • note (and article titles), reply, RSVP posts are snowflake copied by the personal site server to Twitter with permashortlink citation links/references (see Whistle for details) back to the original. Copies of notes to Twitter are also automatically recopied from there to Facebook.
      • RSVPs to Facebook events are “copied” (more like propagated) to Facebook using Bridgy publish
    • likes of tweets are “copied” (more like propagated) to Twitter using Bridgy publish

    Barnaby Walters

    Waterpigs.co.uk as of 2012-03-12. Barnaby Walters implemented POSSE over at waterpigs.co.uk

    • as of 2012-09-25 all collections (notes, articles, activity) are PuSH-subscribable feeds.
    • Using the Client to Server to 3rd Parties flow —Waterpigs.co.uk 06:08, 25 September 2012 (PDT)
    • Syndicating to Twitter + Facebook
    • As of 2014-06-19 Taproot can now optionally post additional POSSE tweets when updating a note or article — example of updated note and POSSE tweet for the update. Note that Bridgy successfully backfeeds silo interactions from the update tweet as well as the original POSSE tweet

    Brennan Novak

    brennannovak.com as of 2012-07-01[5][6]. Brennan Novak implemented POSSE on his site brennannovak.com with copies posted to Twitter and Facebook

    Aaron Parecki

    aaronparecki.com as of 2012-08-19[7][8]. Aaron Parecki implemented POSSE on his site aaronparecki.com with copies posted to Twitter containing permashortlinks back to originals on his own site.

    Sandeep Shetty

    User:Sandeep.io First post POSSE’d on 2012-11-05. I primarily syndicate to Twitter using a very lo-fi solution of adding silo (Facebook, Twiiter, Google+) provided share links to each post that I can manually click to prefill content, edit and post. I’ve avoided API integration because of the extensive experience I’ve had using Facebook API and dealing with it’s random changes. “Integration” has high costs sometimes so I keep it as simple as possible.

    Ben Werdmuller

    werd.io as of 2013-05-31 [9]. Ben Werdmuller implemented POSSE in his idno platform via plugins. New content has an associated Activity Streams object type; POSSE plugins listen for post events associated with those object types and syndicate appropriately.

    • Notes and articles are syndicated to Twitter and Facebook
    • Images are syndicated to Facebook, Flickr and Twitter
    • Places are syndicated to Foursquare
    • More plugins are very easily possible; the Foursquare plugin took about an hour to build

    Shane Becker

    Glenn Jones

    glennjones.net as of 2014-01-14 Glenn Jones The blog implemented POSSE using a new version of transmat.io system. New content added to transmat is associated with objects types. A POSSE twitter plugins listens for post events syndicating content. At moment only notes are syndicated.

    Jeremy Keith

    adactio.com as of 2014-05-27 Jeremy Keith has implemented POSSE using his own custom CMS.

    Shane Hudson

    shanehudson.net as of 2014-09-19 Shane Hudson has implemented POSSE to Twitter for Craft CMS.

    • Previously working on WordPress but he was not keen on the UX.
    • Has reply contexts working but has to manually copy the ID.
    • Not yet POSSEing photos but plans to.
    • Currently he has to manually copy the tweet from the main text box to a 140 character limit tweet text box. He plans to make that automatic.

    Ravi Sagar

    http://www.ravisagar.in/blog/implementing-posse-my-site Implementing POSSE on my site as of 2018-02-21.

    • The new blogs and notes are posted on Drupal
    • http://www.ravisagar.in/rss-social.xml RSS Feed is generated for the blogs and notes tagged with “Share” keyword
    • Using Rebrandly to create shortlinks for the RSS Feed
    • Using Zapier to share the newly created rebrandly links to Twitter and Linkedin

    Ludovic Chabant

    ludovic.chabant.com as of 2018-07-30 Ludovic Chabant has implement POSSE to Twitter and Mastodon from PieCrust CMS, using SiloRider

    • SiloRider is CMS independent — it only relies on Microformats found in the published markup.
    • New articles are posted as title and link.
    • New microblogging updates are mostly copied verbatim (if the fit the external service’s character limits), and support photo posts, including multi-photo posts.

    Adam Dawkins

    adamdawkins.uk as of 2019-01-16 Adam Dawkins has implemented POSSE using his own custom CMS.

    • Notes have been POSSEd since he first started posting them on his own site, on 2019-01-16

    Examples

    Shaun Ewing

    shaun.net as of 2020-01-16 Shaun Ewing has implemented POSSE using Jekyll, and custom APIs.

    Read More

  5. In reply to a post on waterpigs.co.uk

    Back on my blog, I started a rolling list of WebMention blogs. I’ve not maintained that series, but this list started from that blog post series. I’ve marked a few in bold – these are specifically general-purpose conversation starters and topic ideas.

    A

    B

    C

    D

    E

    F

    G

    H

    • Have ideas?

    I

    J

    K

    L

    M

    N

    • Nick Jordan

    O

    P

    Q

    • Quick think of something to go here

    R

    S

    T

    U

    • Under construction

    V

    • Very good reason to add more

    W

    X

    • Xenagogues wanted

    Y

    • You are here

    Z

    I’m open to suggested additions, title corrections, ideas, and anything else related you might want to share. Comments, suggestions, praise, and other feedback by WebMention or ActivityPub only.

    Additions and subtractions

    I will periodically review this list. Sites that seem inactive, I will prune, while new sites I find will be added. To talk about this list, there is a meta page.

    Notes

    This page had some problems (repeating pings). I hope I’ve stopped it now.

  6. In reply to a post on waterpigs.co.uk

    Back on my blog, I started a rolling list of WebMention blogs. I’ve not maintained that series, but this list started from that blog post series. I’ve marked a few in bold – these are specifically general-purpose conversation starters and topic ideas.

    A

    B

    C

    D

    E

    F

    G

    H

    • Have ideas?

    I

    J

    K

    L

    M

    N

    O

    P

    Q

    • Quick think of something to go here

    R

    S

    T

    U

    • Under construction

    V

    • Very good reason to add more

    W

    X

    • Xenagogues wanted

    Y

    • You are here

    Z

    I’m open to suggested additions, title corrections, ideas, and anything else related you might want to share. Comments, suggestions, praise, and other feedback by WebMention or ActivityPub only.

    Additions and subtractions

    I will periodically review this list. Sites that seem inactive, I will prune, while new sites I find will be added. To talk about this list, there is a meta page.

    Notes

    This page had some problems (repeating pings). I hope I’ve stopped it now.

  9. In reply to a post on waterpigs.co.uk

    rubenwardy

    The collapse of Twitter last year got me thinking about closed platforms and reducing the hold that privately owned platforms have over the Internet.

    I’ve been blogging for nine years now on my personal website. I like owning my own domain as it allows me to retain control and stay independent of particular services. Private platforms have a tendency to be bought out and/or ruined by commercial interests, especially now with tech growth slowing down and investors getting uneasy.

    However, there are some benefits to closed blogging platforms. Medium provides a network effect that small blogs don’t have. It has an algorithm that promotes posts that users may find interesting. This allows the blogs to organically gain new readers. Additionally, Medium makes it super easy to like, comment, and reply to a post, resulting in a platform that feels a lot more like a social network than your standard cloud blogging service.

    Last year, I started looking into ways independent blogs could communicate, just like on Medium. I considered making my blog ActivityPub-compatible, as that would allow users on Mastodon and the Fediverse to like, share, and comment on articles. And then, I stumbled upon the IndieWeb.

    Table of contents

    What is IndieWeb?

    IndieWeb.org describes the IndieWeb as:

    The IndieWeb is a community of independent & personal websites connected by simple standards, based on the principles of: owning your domain & using it as your primary identity, publishing on your own site (optionally syndicating elsewhere), and owning your data.

    — IndieWeb.org

    To phrase it another way, IndieWeb is about posting the things you make on your personal website and domain, to keep control of your data and stay independent from private platforms (aka silos). You may still post to silos but you should post to your personal website first.

    IndieWeb isn’t just about blogging. You might post Twitter-like microposts, photos, location check-ins, reviews, replies to other sites, and more.

    POSSE and Backfeeding

    An important concept is “Publish on your Own Site; Syndicate Elsewhere” (POSSE). This means that you should post the original version on your own website and then share links or copies of your content with relevant social media communities. This is simpler and more flexible than adding ActivityPub support to my blog, and is so obvious that I’ve already been doing it without realising it.

    You may be thinking that POSSE is pretty obvious and a bit of a cop-out. But where POSSE truly shines is when combined with backfeeding. A Backfeed is a list of replies, likes, and mentions for the current page. Combined with POSSE, this allows you to see replies to the current page across all different private silos. For example, you might see comments from Mastodon and Reddit at the bottom of a blog post, as well as replies from other IndieWeb websites.

    Together, POSSE and backfeeding strike a good compromise between owning your own presence and participating in silos. They improve discoverability and allow for reader interaction.

    Webmentions

    The IndieWeb community has authored several standards that allow IndieWeb websites to communicate.

    Webmentions allow websites to be notified when another site links to them. By receiving a notification, a site can know about replies and mentions without having to maintain impractical web crawlers or subscribe to a backlinking service.

    Receiving Webmentions

    I started by implementing support for receiving Webmentions. This was super easy, I just needed to add a couple of link tags to the top of all pages:

    <link rel="webmention" href="https://webmention.io/example.com/webmention">
<link rel="pingback" href="https://webmention.io/example.com/xmlrpc">

    WebMention.io is a cloud service for receiving Webmentions. You might think it’s odd to use a cloud service for this, but it’s not a problem as I’m still using my own domain for the pages and could switch the Webmentions service at any time. IndieWeb isn’t about self-hosting, it’s about owning your identity and data.

    Sending Webmentions

    I currently send Webmentions manually using Telegraph or IndieWebify.

    My blog is statically hosted and is built using GitLab CI. As the site is only published when CI finishes, it would be impossible to include sending web mentions as part of the same CI pipeline. In the future, I’ll probably look into using Brid.gy or some other tool to send Webmentions by monitoring my web feeds.

    Microformats2

    Personal websites can contain a variety of content. Long-form articles, Twitter-like notes, location check-ins, reviews, and replies. Microformats2 is a way of marking up the content of web pages so that machines can understand it better. This is a powerful thing when combined with Webmentions as it allows the receiving website to understand what is linking to it and why.

    Microformats2 works by adding classes to elements representing content:

    <article class="h-entry">
    <h2 class="p-name">Hello world!</h2>
    <a href="/tags/a-tag/" class="p-category">
        A tag
    </a>
    <div class="e-content">
        This is the article's content.
    </div>
</article>

    Implementing support for Microformats2 (mf2) was a huge pain, I cannot overstate how much so. The documentation was very fragmented and inconsistent, and the tools I found to test mf2 didn’t match the documentation.

    The most extreme problem I had was with authorship - authorship is how you find out who is the author of a piece of content. The documentation says that you should be able to just include a link to the homepage in each piece of content, and tools should fetch the author info:

    <article class="h-entry">
    <div class="e-content">This is an example note</div>
    <a href="https://rubenwardy.com" class="u-author"></a>
</article>

    However, this did not work at all. Most of the tools I found didn’t make further requests and only looked at the current page. This makes sense I guess, but it’s annoying that the documentation said it was possible.

    The next thing I looked at was including the authorship information in the footer of each page, and then referencing it from each piece of content like so:

    <article class="h-entry">
    <div class="e-content">This is an example note</div>
    <a href="/" class="u-author"></a>
</article>
<footer>
    <a href="/" class="h-card">
        <img class="u-photo" src="/me.jpg">
        <span class="p-name">Author Name</span>
    </a>
</footer>

    Unfortunately, this didn’t work with any of the tools either. The only thing I found that worked was to include the authorship information in full in every single piece of content.

    <article class="h-entry">
    <div class="e-content">This is an example note</div>
    <div class="p-author h-card d-none">
        <a class="u-url p-name" href="https://rubenwardy.com/">rubenwardy</a>
        <img class="u-photo" src="/me.jpg">
    </div>
</article>

    Thank you to users on the IndieWeb IRC channels for pointing towards useful tools and documentation, and asking my newbie questions. Without them, I wouldn’t have been able to implement support at all. I believe that they have improved the documentation a bit based on my feedback, although the authorship page still mentions the methods I tried that didn’t work.

    The three main tools I used for testing Microformats2 were IndieWebify, pin13.net mf2, Waterpigs mf2.

    Backfeeding

    A Backfeed is a list of replies, likes, and mentions for the current page. For example, you might see comments from Mastodon and Reddit at the bottom of a blog post, as well as replies from other IndieWeb websites.

    Backfeeding likes

    My blog shows likes from Mastodon and other social platforms using Brid.gy and Webmentions. When I post a link to my blog on social media, Brid.gy monitors activity and sends Webmentions. JavaScript on my blog fetches Webmentions and updates the counter. My blog also caches like counts at build time. In the future, I’ll make it so that the JS only fetches activity since the blog was last built, reducing the amount of work the Web Mentions API needs to do.

    Backfeeding replies

    I decided not to implement the backfeeding of comments from social media as I’m concerned about the privacy implications. Just because someone decides to reply publicly on social media silos doesn’t mean that they want their post and their profile picture to appear on my website. Additionally, Webmentions can’t be deleted meaning that the comment may continue to appear on my website even after the author deletes it on the silo.

    Two good articles discussing the ethics and privacy challenges of backfeeding include “The ethics of syndicating comments using WebMentions” and “The IndieWeb privacy challenge”.

    I may reconsider this in the future. I’d need to make it sufficiently clear to commenters and allow them to opt-out. I’d also need to make sure that deleting the comment on the silo also deletes it from my website.

    Comment form

    I added a comment form to the bottom of posts on my blog. My blog is statically hosted. To collect comments, I have a service running on another subdomain that collects any comments and sends them to me. Users can also choose to send comments by email or another method. All comments are moderated before showing on my blog.

    To avoid spam, the comment form has a “username” form hidden using CSS. Most spam bots don’t bother applying the CSS so will see the field and fill it in. This is called a honeypot field and is surprisingly effective - I was receiving multiple spam comments a day, but since adding the field I’ve only received a single spam comment.

    <style>
    input[name="username"] {
        display: none;
    }
</style>
<input type="text" name="username">

    You can find the source code behind commenting on GitLab.

    Thoughts on the IndieWeb

    IndieWeb standards are fairly obscure and don’t seem to have been adopted much yet. Of all the posts I’ve made since adding IndieWeb support, this is probably the only one that will actually find websites linked to that can receive Webmentions. If a popular Content Management System, like WordPress, added built-in support for Webmentions and mf2, I could see it suddenly becoming a lot more popular.

    Whilst Webmentions are pretty cool, Microformats2 is pretty complicated and was pretty annoying to implement. I know that the IndieWeb crowd will have strong opinions on this, but I quite like how simple JSON-LD was to add support for and that it’s JSON.

    As for the community side of IndieWeb, personal websites have seen a big resurgence since the fall of Twitter. I think we’re in a new golden age for RSS and personal websites. I’ve been encouraging a lot of my friends to take up blogging.

    Conclusion

    I’m certainly a more technical user than the average blogger. I don’t mind being an early adopter of technology and appreciate the goals of IndieWeb. I like how they try to focus on the people before the technology, even though Microformats2 leaves much to be desired.

    I currently only post blog posts on my website. I don’t plan to post notes on my website as I prefer to use Mastodon directly. But I might start posting my photography here.

    I’m undecided as to whether I’ll stick with IndieWeb technology in the long term, but I’ll certainly continue to own and publish on my own domain.

  11. In reply to a post on waterpigs.co.uk

    Tantek Çelik

    10 years ago today the first #federated #IndieWeb comment thread was published and collected peer-to-peer IndieWeb replies across websites without any intermediary, silo or otherwise¹.

    2013-04-19 @eschnou.com posted a brief note on his personal site with #atMentions of a few domains (putting an '@' sign immediately before a domain name to indicate an explicit cross-web @-mention), which itself was also a first²

    "Testing #indieweb federation with @waterpigs.co.uk, @aaronparecki.com and @indiewebcamp.com !"

    When @aaronpk.com was notified and replied from his site within minutes³, it became the first peer-to-peer federated IndieWeb comment thread, at the time using h-entry and Pingback. I blogged about it a few days later⁴.

    Earlier this year I blogged more observations of all the user interactions that happened on that day and shortly thereafter to make this all work: https://tantek.com/2023/014/t4/domain-first-federated-atmention

    Unfortunately Laurent Eschnou’s original post is no longer up, and we only have the Internet Archive copy. However most of the IndieWeb reply posts are still up including Barnaby’s: https://waterpigs.co.uk/notes/1334/

    The oldest still working federated post and comment thread was second overall, unsurprisingly from @aaronparecki.com⁵, a whole 40 days after Laurent’s first.

    This is day 37 of #100DaysOfIndieWeb. #100Days #OpenWeb #federation #fediverse

    ← Day 36: https://tantek.com/2023/100/t1/auto-linked-hashtags-federated
    → Day 38: https://tantek.com/2023/110/t2/beyond-mastodon-indieweb-own-domain


    Glossary

    federation
    https://indieweb.org/federation
    h-entry
    https://microformats.org/wiki/h-entry
    Pingback
    https://indieweb.org/Pingback
    reply post
    https://indieweb.org/reply

    References

    ¹ https://web.archive.org/web/20130427010301/http://eschnou.com/entry/testing-indieweb-federation-with-waterpigscouk-aaronpareckicom-and--62-24908.html
    ² https://tantek.com/2023/014/t4/domain-first-federated-atmention
    ³ https://aaronparecki.com/2013/04/19/3/indieweb
    ⁴ https://tantek.com/2013/113/b1/first-federated-indieweb-comment-thread
    ⁵ https://aaronparecki.com/2013/05/21/4/xkcd
  12. In reply to a post on waterpigs.co.uk

    Tantek Çelik

    10 years ago today the first #federated #IndieWeb comment thread was published and collected peer-to-peer IndieWeb replies across websites without any intermediary, silo or otherwise¹.

    2013-04-19 @eschnou.com posted a brief note on his personal site with #atMentions of a few domains (putting an '@' sign immediately before a domain name to indicate an explicit cross-web @-mention), which itself was also a first²

    "Testing #indieweb federation with @waterpigs.co.uk, @aaronparecki.com and @indiewebcamp.com !"

    When @aaronpk.com was notified and replied from his site within minutes³, it became the first peer-to-peer federated IndieWeb comment thread, at the time using h-entry and Pingback. I blogged about it a few days later⁴.

    Earlier this year I blogged more observations of all the user interactions that happened on that day and shortly thereafter to make this all work: https://tantek.com/2023/014/t4/domain-first-federated-atmention

    Unfortunately Laurent Eschnou’s original post is no longer up, and we only have the Internet Archive copy. However most of the IndieWeb reply posts are still up including Barnaby’s: https://waterpigs.co.uk/notes/1334/

    The oldest still working federated post and comment thread was second overall, unsurprisingly from @aaronparecki.com⁵, a whole 40 days after Laurent’s first.

    This is day 37 of #100DaysOfIndieWeb. #100Days #OpenWeb #federation #fediverse

    ← Day 36: https://tantek.com/2023/100/t1/auto-linked-hashtags-federated
    → Day 38: https://tantek.com/2023/110/t2/beyond-mastodon-indieweb-own-domain


    Glossary

    federation
    https://indieweb.org/federation
    h-entry
    https://microformats.org/wiki/h-entry
    Pingback
    https://indieweb.org/Pingback
    reply post
    https://indieweb.org/reply

    References

    ¹ https://web.archive.org/web/20130427010301/http://eschnou.com/entry/testing-indieweb-federation-with-waterpigscouk-aaronpareckicom-and--62-24908.html
    ² https://tantek.com/2023/014/t4/domain-first-federated-atmention
    ³ https://aaronparecki.com/2013/04/19/3/indieweb
    ⁴ https://tantek.com/2013/113/b1/first-federated-indieweb-comment-thread
    ⁵ https://aaronparecki.com/2013/05/21/4/xkcd
  14. In reply to a post on waterpigs.co.uk

    Tantek Çelik

    10 years ago today the first #federated #IndieWeb comment thread was published and collected peer-to-peer IndieWeb replies across websites without any intermediary, silo or otherwise¹.

    2013-04-19 @eschnou.com posted a brief note on his personal site with #atMentions of a few domains (putting an '@' sign immediately before a domain name to indicate an explicit cross-web @-mention), which itself was also a first²

    "Testing #indieweb federation with @waterpigs.co.uk, @aaronparecki.com and @indiewebcamp.com !"

    When @aaronpk.com was notified and replied from his site within minutes³, it became the first peer-to-peer federated IndieWeb comment thread, at the time using h-entry and Pingback. I blogged about it a few days later⁴.

    Earlier this year I blogged more observations of all the user interactions that happened on that day and shortly thereafter to make this all work: https://tantek.com/2023/014/t4/domain-first-federated-atmention

    Unfortunately Laurent Eschnou’s original post is no longer up, and we only have the Internet Archive copy. However most of the IndieWeb reply posts are still up including Barnaby’s: https://waterpigs.co.uk/notes/1334/

    The oldest still working federated post and comment thread was second overall, unsurprisingly from @aaronparecki.com⁵, a whole 40 days after Laurent’s first.

    This is day 37 of #100DaysOfIndieWeb. #100Days #OpenWeb #federation #fediverse

    ← Day 36: https://tantek.com/2023/100/t1/auto-linked-hashtags-federated
    → 🔮


    Glossary

    federation
    https://indieweb.org/federation
    h-entry
    https://microformats.org/wiki/h-entry
    Pingback
    https://indieweb.org/Pingback
    reply post
    https://indieweb.org/reply

    References

    ¹ https://web.archive.org/web/20130427010301/http://eschnou.com/entry/testing-indieweb-federation-with-waterpigscouk-aaronpareckicom-and--62-24908.html
    ² https://tantek.com/2023/014/t4/domain-first-federated-atmention
    ³ https://aaronparecki.com/2013/04/19/3/indieweb
    ⁴ https://tantek.com/2013/113/b1/first-federated-indieweb-comment-thread
    ⁵ https://aaronparecki.com/2013/05/21/4/xkcd
  15. In reply to a post on waterpigs.co.uk

    Tantek Çelik

    10 years ago today the first #federated #IndieWeb comment thread was published and collected peer-to-peer IndieWeb replies across websites without any intermediary, silo or otherwise¹.

    2013-04-19 @eschnou.com posted a brief note on his personal site with #atMentions of a few domains (putting an '@' sign immediately before a domain name to indicate an explicit cross-web @-mention), which itself was also a first²

    "Testing #indieweb federation with @waterpigs.co.uk, @aaronparecki.com and @indiewebcamp.com !"

    When @aaronpk.com was notified and replied from his site within minutes³, it became the first peer-to-peer federated IndieWeb comment thread, at the time using h-entry and Pingback. I blogged about it a few days later⁴.

    Earlier this year I blogged more observations of all the user interactions that happened on that day and shortly thereafter to make this all work: https://tantek.com/2023/014/t4/domain-first-federated-atmention

    Unfortunately Laurent Eschnou’s original post is no longer up, and we only have the Internet Archive copy. However most of the IndieWeb reply posts are still up including Barnaby’s: https://waterpigs.co.uk/notes/1334/

    The oldest still working federated post and comment thread was second overall, unsurprisingly from @aaronparecki.com⁵, a whole 40 days after Laurent’s first.

    This is day 37 of #100DaysOfIndieWeb. #100Days #OpenWeb #federation #fediverse

    ← Day 36: https://tantek.com/2023/100/t1/auto-linked-hashtags-federated
    → 🔮


    Glossary

    federation
    https://indieweb.org/federation
    h-entry
    https://microformats.org/wiki/h-entry
    Pingback
    https://indieweb.org/Pingback
    reply post
    https://indieweb.org/reply

    References

    ¹ https://web.archive.org/web/20130427010301/http://eschnou.com/entry/testing-indieweb-federation-with-waterpigscouk-aaronpareckicom-and--62-24908.html
    ² https://tantek.com/2023/014/t4/domain-first-federated-atmention
    ³ https://aaronparecki.com/2013/04/19/3/indieweb
    ⁴ https://tantek.com/2013/113/b1/first-federated-indieweb-comment-thread
    ⁵ https://aaronparecki.com/2013/05/21/4/xkcd
  16. In reply to a post on waterpigs.co.uk

    The Real Housewives of Salt Lake City’s owned dozens of phony luxury items including bags and jewelry federal autho to federal charges that she had put together a $5 million telemarketing scam targeted to swindle older people.

    The latest: The Real Housewives of Salt Lake City’s Jen Shah, 49, owned dozens of phony luxury items including bags and jewelry federal authorities seized during a raid of her Utah residence last year

    Among the fraudulent items of merchandise, which were mostly manufactured in China, included fake purses aimed to resemble products from high-end brands including Balenciaga, Chanel, Fendi, Gucci, Hermes, Jimmy Choo, Louis Vuitton and Valentino.

    The jewelry collection included counterfeit pieces made to resemble designers such as Bulgari, Chanel, Cartier, eVDeN EVE nAKLiyaT Dior, Gucci, Hermes, Louis Vuitton and Tiffany & Co.

    RELATED ARTICLES

    Share this article

    48 shares

    Mixed in with the phony items were actual pieces of luxury accessories and jewelry from brands such as Yves Saint Laurent, Versace, Gucci, evDEn eve nakLiYat Louis Vuitton and Prada, as well as pieces from her castmate Meredith Marks’ brand.

    Federal authorities took possession of all of the items amid a raid on the Bravo personality’s home in March of 2021 in the probe into her fraud case.

    After the holidays: Jen Shah’s trial date has been pushed back until next year, after she plead guilty to charges of organizing a $5million telemarketing scam that targeted hundreds of elderly people

    Approved: The Real Housewives of Salt Lake City star’s new court date is set for January 6, 2023

    Shah’s sentencing date has been pushed back until next year, after she that targeted hundreds of elderly people.

    The star’s new court date is set for , 2023, after the holidays.

    In court documents, obtained by , it was revealed that ‘Judge Sidney H.Stein approved the rescheduling on Wednesday, November 23.’

    In July, Shah plead guilty to conspiracy to commit wire fraud, with the US attorney dropping her second count of conspiracy to commit money laundering.

    Shah’s assistant Stuart Smith previously admitted his part in the same scam, and had been due to testify against his former employer, until her guilty plea.

    The US attorney’s office says Shah faces the maximum sentence of 30 years in prison, but NBC Connecticut reports that a plea deal will actually see her serve a maximum of 14 years.

    A few extra months of freedom: In court documents, obtained by Us Weekly , it was revealed that ‘Judge Sidney H.Stein approved the rescheduling on Wednesday, November 23’