Embed Notice

HTML Code

<blockquote style="position: relative; padding-left: 55px;"><section><a href="https://toot.fedilab.app/users/apps/statuses/109870406293890972">Fedilab Apps (apps@toot.fedilab.app)'s status on Thursday, 16-Feb-2023 04:30:47 JST</a><a href="https://toot.fedilab.app/@apps" title="apps@toot.fedilab.app"><img src="https://gnusocial.jp/avatar/9286-48-20220907190205.webp" width="48" height="48" alt="Fedilab Apps" style="position: absolute; left: 0; top: 0;">Fedilab Apps</a><div><a href="https://fosstodon.org/@AntennaPod/109844984567859264" rel="in-reply-to">in reply to</a><ul><li><li><a href="https://gnusocial.jp/user/3159" title="tusky@mastodon.social">Tusky</a></li><li><a href="https://gnusocial.jp/user/12220" title="keunes@mastodon.social">Keunes</a></li><li><a href="https://gnusocial.jp/user/12221" title="antennapod@fosstodon.org">AntennaPod</a></li><li><a href="https://gnusocial.jp/user/42557" title="tooot@social.xmflsct.com">tooot?</a></li></ul></div></section><article><p><a href="https://fosstodon.org/@AntennaPod">@AntennaPod</a> <a href="https://mastodon.social/@Tusky">@Tusky</a> <a href="https://mastodon.juggler.jp/@SubwayTooter">@SubwayTooter</a> <a href="https://social.xmflsct.com/@tooot">@tooot</a> <a href="https://mastodon.social/@keunes">@keunes</a> <br>We have to agree for a scheme and host names for the intent.<br>We started a discussion here: <a href="https://codeberg.org/tom79/Fedilab/issues/792" rel="nofollow noreferrer">https://codeberg.org/tom79/Fedilab/issues/792</a><br>We are ready to go further.</p></article><footer><a rel="bookmark" href="https://gnusocial.jp/conversation/1202651#notice-2557001">In conversation</a><time datetime="2023-02-16T04:30:47+09:00" title="Thursday, 16-Feb-2023 04:30:47 JST">Thursday, 16-Feb-2023 04:30:47 JST</time> <span>from <span><a href="https://gnusocial.jp/notice/2557001" rel="external" title="Sent from gnusocial.jp via ActivityPub">gnusocial.jp</a></span></span><a href="https://gnusocial.jp/notice/2557001">permalink</a><h4>Attachments</h4><ol><li><article><header><div>Domain not in remote thumbnail source whitelist: codeberg.org</div><h5><a href="https://codeberg.org/tom79/Fedilab/issues/792">Declare intent filter to open a post</a></h5><div> from <span>tom79</span></div></header><div>- [x] Mastodon
- [ ] Pleroma
- [ ] Friendica
- [ ] PixelfedThere's a new idea for podcasts: cross-app comments based on ActivityPub (https://github.com/Podcastindex-org/podcast-namespace/blob/main/docs/1.0.md#social-interact). TL:DR – each episode (of podcasts taking part) has a 'root' post. Replies can be posted to it as usual. Example: https://podcast.thelinuxexp.com/@tlenewspodcast/posts/3be3bb49-690d-4deb-84e7-66da3c4567dfIn AntennaPod, the open source podcast player for Android, we would like to make it easy to access &amp; join listener conversations. But rather than including a full interface to view and post comments, the idea is to let dedicated apps handle this. Concretely: from AntennaPod you hit a button to open an episode's root post in your favourite ActivityPub/Mastodon app. You then have all the great features you're used to. And if you don't have such app installed, we'll display a short explanation and guide you to some options.We could just link to the root post URL, but that's [not](https://issuetracker.google.com/issues/258270055) guaranteed to open the right app if installed. And we wouldn't be able to give the user an explanation if such app is not installed.So, we need an alternative. As I understand, [declaring an intent filter](https://developer.android.com/guide/components/intents-filters#Receiving) is the best alternative. AntennaPod can then send an [implicit intent](https://developer.android.com/guide/components/intents-filters#ExampleSend) in order to open a post. For example: web+activitypub://post/${encoded post uri}See also:
https://fosstodon.org/@AntennaPod/109844984567859264
https://github.com/activitypub-schema/proposal/blob/main/PROPOSAL.md
https://github.com/fedi-to/fedi-to.github.io/blob/main/webap.mdLong story short - it would be great if Fedilab could implement an intent filter to open posts, so that AntennaPod can call such intent. Curious to hear your thoughts. (Other apps should do the same for this to work well, of course. But Fedilab as a start would be a great start, but great for me to test as I us it actively.) [x] - I read the [contributing page](https://codeberg.org/tom79/Fedilab/src/branch/main/CONTRIBUTING.md)</div><footer></footer></article></li></ol></footer></blockquote>

Corresponding Notice

Embed this notice
Fedilab Apps (apps@toot.fedilab.app)'s status on Thursday, 16-Feb-2023 04:30:47 JSTFedilab Apps
in reply to
@AntennaPod @Tusky @SubwayTooter @tooot @keunes
We have to agree for a scheme and host names for the intent.
We started a discussion here: https://codeberg.org/tom79/Fedilab/issues/792
We are ready to go further.
In conversationThursday, 16-Feb-2023 04:30:47 JST from gnusocial.jppermalink
Attachments
1. Domain not in remote thumbnail source whitelist: codeberg.org
  Declare intent filter to open a post
  from tom79
  - [x] Mastodon - [ ] Pleroma - [ ] Friendica - [ ] Pixelfed There's a new idea for podcasts: cross-app comments based on ActivityPub (https://github.com/Podcastindex-org/podcast-namespace/blob/main/docs/1.0.md#social-interact). TL:DR – each episode (of podcasts taking part) has a 'root' post. Replies can be posted to it as usual. Example: https://podcast.thelinuxexp.com/@tlenewspodcast/posts/3be3bb49-690d-4deb-84e7-66da3c4567df In AntennaPod, the open source podcast player for Android, we would like to make it easy to access & join listener conversations. But rather than including a full interface to view and post comments, the idea is to let dedicated apps handle this. Concretely: from AntennaPod you hit a button to open an episode's root post in your favourite ActivityPub/Mastodon app. You then have all the great features you're used to. And if you don't have such app installed, we'll display a short explanation and guide you to some options. We could just link to the root post URL, but that's [not](https://issuetracker.google.com/issues/258270055) guaranteed to open the right app if installed. And we wouldn't be able to give the user an explanation if such app is not installed. So, we need an alternative. As I understand, [declaring an intent filter](https://developer.android.com/guide/components/intents-filters#Receiving) is the best alternative. AntennaPod can then send an [implicit intent](https://developer.android.com/guide/components/intents-filters#ExampleSend) in order to open a post. For example: web+activitypub://post/${encoded post uri} See also: https://fosstodon.org/@AntennaPod/109844984567859264 https://github.com/activitypub-schema/proposal/blob/main/PROPOSAL.md https://github.com/fedi-to/fedi-to.github.io/blob/main/webap.md Long story short - it would be great if Fedilab could implement an intent filter to open posts, so that AntennaPod can call such intent. Curious to hear your thoughts. (Other apps should do the same for this to work well, of course. But Fedilab as a start would be a great start, but great for me to test as I us it actively.) [x] - I read the [contributing page](https://codeberg.org/tom79/Fedilab/src/branch/main/CONTRIBUTING.md)

Public

Embed Notice

HTML Code

Corresponding Notice