jon
/
jk_na
Archived
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
jk.nipponalba.scot website https://jk.nipponalba.scot
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
This repo is archived. You can view files and clone it, but cannot push or open issues/pull-requests.
1752 Commits
1 Branch
0 Tags
334 MiB
 
 
 
Tree: a8794b67df
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'a8794b67df'
${ noResults }
jk_na/content/note/5f99e9e1/index.md

1.2 KiB
Raw Blame History

category date draft posttype slug visibility title
[bridgy pleroma epicyon webmentions microformats2] 2020-10-28 22:00:01 false note 5f99e9e1 public note

If I were to replace pleroma with epicyon (big IF at this stage as I haven't even installed it yet), I'd need to work out how to replace brid.gy in my indieweb process flow..

Currently, when I post a note, photo or blog post to my site the URL of the new post is sent to the brid.gy api and it maps microformats2 elements to their mastodon API equivalents and posts on my behalf to my pleroma account (via a custom OATH app that I had to create).

Direct replies and interactions are sent by brid.gy to my webmentions endpoint (and any other webmention capable sites mentioned) and a separate tool on my server outputs that to a json file and triggers a hugo site rebuild..

So, I would need to implement a method for posting to epicyon on my behalf (without an API) and then, monitor the post for interactions, convert into microformats2 compliant json messages and fire them off to my webmentions endpoint..

So.. has anyone with far more of a clue about this already created the solution that I would need?