Notices by errhead (errhead@gleasonator.com)
-
errhead (errhead@gleasonator.com)'s status on Sunday, 21-Jan-2024 03:54:02 JST 
errhead
@silverpill @alex @dave That's good to know.
still don't see the upside to
https://lemmy.eus/feeds/c/informatikariak.xml?sort=Active
https://tilvids.com/feeds/podcast/videos.xml?videoChannelId=56
https://podcastindex.social/@errhead.rss
vs.
https://lemmy.eus/.well-known/rss/informatikariak
https://tilvids.com/.well-known/rss/playcontent_channel
https://podcastindex.social/.well-known/rss/errhead
though actually looking at it now, the Mastodon method has a certain elegance to it. Plus it's easier to just go with their method than trying to get them to change... -
errhead (errhead@gleasonator.com)'s status on Sunday, 21-Jan-2024 03:12:25 JST
errhead
Many Activity Pub instances provide rss feeds, but the addresses aren't standardized.
Thinking on what @dave is doing with the activitypub/podcast rss gateway inspired this insight.
Why not .well-known/rss/ ? a nice logical place to find it, or be directed to it for any Activity Pub server.
With the address easily translated to an RSS feed, modern Podcasting apps and feed readers could add the ability to subscribe by address, making it much easier for discovery to lead to subscription.
For the index itself, I think it makes more sense for
https://ap.podcastindex.org/.well-known/rss/920666
to 301 redirect to the actual address of the podcast RSS feed.
Are there downsides I'm missing in this? @silverpill @alex -
errhead (errhead@gleasonator.com)'s status on Tuesday, 24-Oct-2023 23:05:33 JST
errhead
@silverpill async function checkWebLnSupport() {
try {
await webln.enable()
if (typeof webln.keysend === 'function') {
console.log('⚡️✅ webln keysend support');
return 2;
} else {
console.log("⚡️✅ webln supported ⛔️ keysend not supported");
return 1;
}
} catch {
console.log("⚡️⛔️ webln not supported");
return 0;
}
} -
errhead (errhead@gleasonator.com)'s status on Tuesday, 24-Oct-2023 18:59:42 JST
errhead
@silverpill Mostly like this. I also search account.note and account.description for anything using the ⚡️user@host format for completeness.
apiCall = "https://" + hostAddress + "/api/v1/accounts/" + userName;
accountData = await axios.get(apiCall);
if (!accountData) {
apiCall = "https://" + hostAddress + "/api/v1/accounts/lookup?acct=" + userName
accountData = await axios.get(apiCall);
}
if (accountData) {
let account = accountData.data
if (account.fields) {
for (var field of account.fields) {
if (field.name.toLowerCase() === "lightning address" || field.name.toLowerCase() === "lud16") {
foundLightningAddress = field.value;
}
}
} -
errhead (errhead@gleasonator.com)'s status on Tuesday, 24-Oct-2023 18:33:15 JST
errhead
@silverpill They all should, debugging the federated stuff is the most complex.
Yes, It's worked so far in my Mastodon and Soapbox testing of replying to videos in the timeline -
errhead (errhead@gleasonator.com)'s status on Tuesday, 24-Oct-2023 18:09:25 JST
errhead
PeerTube plugin ways to pay v4v in the client.
- Streaming payments. Can be enabled on V4V settings page. If the video being watched has a split configured, then every minute of content sends the configured payment amount to the channel split.
- Boostagram. Sends a payment with a message to the split block.
- Patronage. Sends a regular payment to a channel's split block. Become a patron of the arts, no quid pro quo provided or implied.
- Cross App Comment Zap. PeerTube supports cross app comments natively. If the commenter has a boostback address configured, or is on Activity-pub with a lud16 address configured, zap sats directly to the commenter. Keysend if available, can fallback to lnurl, not compatible with nostr zaps.
Streaming and Boosts support Magic Wallet Switching Technology by using https://www.thesplitkit.com event integration for both Live and Pre-recorded video.
On the hosted side, the PeerTube RSS feed has the info needed to support boosts and streams including #MWST and #BoostBack for users of modern podcasting apps.
Embedded videos aren't the using the client per se, but the embedded player supports WebLN boosts with limited metadata.
All ０７６萌ＳＮＳ content and data are available under the