I spun up my own BoostBox last night.
-
I spun up my own BoostBox last night. I didn't want to but having my own that I can access makes this all much easier to test. I also have everything displayed on the main page and if you click on one you get the rest of the details.
I guess each app will just have its own version going forward which we were kind of against but Franco seems ok with it and he's been the reference point for apps without much backend services so I guess this is what we're testing now.
️ -
I podcastindex.social shared this topic
-
I spun up my own BoostBox last night. I didn't want to but having my own that I can access makes this all much easier to test. I also have everything displayed on the main page and if you click on one you get the rest of the details.
I guess each app will just have its own version going forward which we were kind of against but Franco seems ok with it and he's been the reference point for apps without much backend services so I guess this is what we're testing now.
️@ChadF if we can have a common server, maybe hosted by podcast index, it would be great for me. I’m not too confortable on hosting users messages. I think I'll put an expiration date so messages are purged after 1 month.
-
@ChadF if we can have a common server, maybe hosted by podcast index, it would be great for me. I’m not too confortable on hosting users messages. I think I'll put an expiration date so messages are purged after 1 month.
I'm not even sure how podcasters even read all of these coming in. Your wallet is just full of urls and that's not very helpful either.
Maybe a central server would help with that or a service that pulls that all in.
I know you mentioned you use some custom code to pull info from Alby and I've always just used Helipad to read stuff.
-
@ChadF if we can have a common server, maybe hosted by podcast index, it would be great for me. I’m not too confortable on hosting users messages. I think I'll put an expiration date so messages are purged after 1 month.
This isn't the responsibility of the Index or the apps. This is the responsibility of the podcaster. If they want their messages, they should figure out how to receive and host them or hire a host that does.
-
This isn't the responsibility of the Index or the apps. This is the responsibility of the podcaster. If they want their messages, they should figure out how to receive and host them or hire a host that does.
This whole business of having 20 different apps all hosting their own messages is stupid. The podcaster ends up needing a server anyway to go through all the invoices, fetch each message from each app, then display it in a user friendly way. If they're going to need a server to do that anyway, let's cut out the part where each app stores their metadata and the app can just send the metadata straight to the podcaster's server instead.
-
This whole business of having 20 different apps all hosting their own messages is stupid. The podcaster ends up needing a server anyway to go through all the invoices, fetch each message from each app, then display it in a user friendly way. If they're going to need a server to do that anyway, let's cut out the part where each app stores their metadata and the app can just send the metadata straight to the podcaster's server instead.
-
If we set the motion in the wrong direction, we may never actually get to where we should. In this case, it seems better to not move than to move in the wrong direction. The first host to offer metadata hosting will will be able to offer a service that no other host is, but the apps doing it for the host only allows them to drag their feet longer.
-
If we set the motion in the wrong direction, we may never actually get to where we should. In this case, it seems better to not move than to move in the wrong direction. The first host to offer metadata hosting will will be able to offer a service that no other host is, but the apps doing it for the host only allows them to drag their feet longer.
This seems like a perfect opportunity for a hosting company like Fountain or Truefans to offer a service that would entice podcasters to partner with them.
"Sign up for my hosting and we'll store all your metadata and create a sweet dashboard to display your stats and messages."
-
@ChadF if we can have a common server, maybe hosted by podcast index, it would be great for me. I’m not too confortable on hosting users messages. I think I'll put an expiration date so messages are purged after 1 month.
@francosolerio @ChadF yeah, my concern is that this is sensitive, payment metadata. I would like podcasters to declare how they want it to be handled in their RSS feed.
Common servers could be useful. We could tell podcasters "here are some common servers that are available. Provide a link to the one you want to use in a simple RSS tag."
I also think there's an opportunity here for RSS companies to offer their on dashboards for collecting and displaying metadata.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register LoginWelcome To Podcasting.Chat!
This forum is for podcasters, podcast guests, and podcast enthusiasts alike to share tips, tricks, and their love of the medium.
This forum is fully federated, so you are able to contribute to any discussion here through your own software of choice (e.g. Mastodon, Misskey, Lemmy, Piefed, etc.). So you can sign up for an account here and it federates around the Fediverse. You can also follow feeds and topics from your other Fedi-enabled accounts.
Recent Posts
-
-
-
@cathest fascinating - I didn't know any of this - thank you for finding and sharing.
-
I opened up my CashApp wallet, and see all of this ::rss stream:: gobbledygook.
What am I suppose to do with that?
Comb through it and click each one so I can get the metadata?
