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.
2909 Commits
1 Branch
0 Tags
334 MiB
Tree: f969a4b5b3
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'f969a4b5b3'
${ noResults }
jk_na/content/note/604666c4/index.md

13 lines
664 B
Raw Normal View History

Scripted auto-commit on change (2021-03-08 18:02:46) by gitwatch.sh
4 years ago
​
​
​
​
Scripted auto-commit on change (2021-03-08 18:02:50) by gitwatch.sh
4 years ago
Scripted auto-commit on change (2021-03-08 18:02:46) by gitwatch.sh
4 years ago
​
​
​
​
​
​
  1. ---
  2. category:
  3. - self-hosting
  4. date: '2021-03-08 18:02:44'
  5. draft: false
  6. pleromaurl: 'https://social.nipponalba.scot/notice/A50Xs0Ur8nyzW5lXgu'
  7. posttype: note
  8. sensitive: 'false'
  9. slug: 604666c4
  10. visibility: public
  11. title: note
  12. ---
  13. As the latest pleroma update has rendered the Mastodon API instance page (on my instance) non-functional which breaks its connection with brid.gy which I use to post interactions from here back to my site.. I'm wondering if I can replicate the function with my own infrastructure.. and think it should just be a matter of monitoring my atom feed via beehive and sending the URL to a webmentions endpoint.. sounds theoretically doable.