tantek.com

t

  1. Consider new Bridgy Backfill service to import past responses

    on

    Bridgy Backfeed sends current and future silo responses to your posts as webmentions, for your posts to handle as they come in. It would be great to have the complementary service of Bridgy Backfill (feel free to bikeshed the name) to send past silo responses to your posts as webmentions, as a way of backfilling / importing old responses to your posts, including your old posts.

    The key use-case here is: help with migration away from social media.

    If you can backfill/import the comments/responses on your old social media posts into your own site, then you have fewer reasons to keep around those old social media posts, and thus fewer reasons to keep around that social media account.

    Such migration of responses to old social media posts would also enable deletion of those old social media posts, as a step towards de-activating and deleting a specific social media account.

    Since it’s likely you may only want to run this "once" and it may take a while as it will likely require crawling your silo posts history which may be throttled, this makes sense as a separate service that you authenticate, activate, and then allow it to progress back through your old posts (and old responses to your posts), perhaps with some progress indicator, and perhaps with some sort of notification when it has completed.

    This new service would be in addition to the existing Bridgy services: Bridgy Backfeed, Bridgy Publish, Bridgy for Blogs, and Bridgy Fed.

    on
  2. Rather than assuming, I checked the Bridgy source, which uses Granary for this, and verified that Granary does have an explicitly enumerated list for the reacji that GitHub allows.

    Submitted https://github.com/snarfed/granary/pull/186 to add Granary support for the new 🚀👀 reacji in GitHub, and thus in Bridgy.

    Please commit and deploy that pull request first before this one.

    Alter reality before updating the documentation about reality. Thanks!

    on
  3. > Why? It does a reasonable job at being privacy preserving - or did I miss something?

    Please ask follow-up questions of a potential eventual "harmful" evaluation like that on https://github.com/mozilla/standards-positions/issues/153, rather than asking here on a pull request to "defer".

    I’m also requesting "us to be able to actually defer rather than debate" a specific eventual evaluation.

    on
  4. I agree with https://github.com/dbaron about Marcos’s suggestion doesn’t fit with a "defer" position.

    I also strongly disagree with even hinting that we might think this API is "non-harmful" when that hasn’t even been mentioned in https://github.com/mozilla/standards-positions/issues/153 — in fact quite the opposite, I noted explicitly there that "I’m leaning towards expecting an eventual 'harmful' evaluation."

    So I’m not ok with moving it into the description, and that is unnecessary for a defer position. I’d like us to be able to actually defer rather than debate more details in the description.

    Re: "leaves their source unspecified", I’m ok with dropping that from the description, it’s not really an actionable criticism outside of a thorough evaluation. I’ll update the PR accordingly.

    on
  5. Explore support for Bridgy Publish to GitHub POSSE special responses to issues: close, re-open, lock, unlock

    on

    GitHub issues accept a set of special responses via their user interface:

    • close
    • re-open
    • lock
    • unlock

    As part of using our own websites to publish and POSSE issues instead of GitHub, it would be great if Brigy Publish to GitHub could be expanded to handle these special response types.

    As a first step, this issue is a request to explore the possibility and document any available GitHub API calls to do so, either purely as issue state change responses, or perhaps in the case of "close", the ability to close with a comment in the UI of an issue by clicking the "Close issue" button to the left of the "Comment" button (when available to the user).

    More documentation of brainstorming special responses to issues and broader considerations, e.g. issues state change special responses on other systems, see the IndieWeb wiki: issue: Special Responses

    Label: publish.

    on
  6. Thanks https://github.com/hober. I reviewed the changes in https://github.com/privacycg/privacycg.github.io/pull/5 and it all looks good. Consider this issue resolved by those changes.

    Closing issue.

    on
  7. Clear blue to orange pre-dawn gradient sky above the San Francisco skyline in the distance behind a barely visible Dolores Park, a few paths and trees lit in by lamps.Tall palm tree with the moon behind it against a bluish purple pre-dawn sky with a statue, apartment building, and a few trees in the background, a dirt bed of various succulents at the base of the palm tree.🌆🌴 Clear #preDawn skies @Nov_Project_SF yesterday at Dolores Park(1), lit by a recently full moon(2).

    #NPSF #NovemberProjectSF #NovemberProject #wakeUpTheSun #fromWhereIRun #dawn #clearSky #blue #orange #yellow #optOutside #Dolores #DoloresPark #MissionDolores #MissionDoloresPark #SanFrancisco #freeFitness #2020_041 #20200210 #laterGram #noFilter

    on