It feels like more Lemmy apps are going to make their way on to the app stores. With more apps, comes more people. More people, more API calls. How do we scale this server and hopefully all of the others to come, financially?

There are some REALLY interesting Podcast 2.0 features in the works. Especially using “value4value” and “boosting” as a way for listeners to tip their favorite podcasts and fund them directly. I wonder if somehow we can learn from it?

For those who do not know, hopefully these Podcasting 2.0 features will help podcasters continue to thrive in world where companies like Spotify and Amazon have decided to destroy our incredible open and free podcast networks by making “exclusives” and putting them behind paywalls that don’t follow the open standards.

I’d really love to integrate Podcasting 2.0 RSS and the fediverse. How cool would it be if every podcast episode just had its own place in the fediverse with a place to chat and it all worked together somehow automatically.

I dunno. Just a thought.

Here’s some info:

https://podnews.net/article/new-podcast-apps

https://blubrry.com/podcast-insider/2023/01/25/blubrry-releases-new-podcasting-2-0-integration-value4value/

  • gkd@lemmy.ml
    3·
    2 years ago

    Developer here. I’ve been looking at the API calls made by the app, and I’ll try to give a good example of what is going on:

    To be honest, you’re probably not going to see a drastic change in API calls right now. The only things that you are calling the API for are:

    • Load items in the feed
    • Load post/comments
    • Load profiles
    • Submit votes
    • Submit comments
    • Submit posts
    • One initial call at app launch to obtain user info (subscriptions, settings, saved posts, etc, lemmy’s API gives you all of this in one call)

    This is about the same use that you’re going to see in the actual web version.

    While there may be upsides and downsides to how they are doing it right now, you can get pretty much all of the info you need through one API call. For example, if I get a post, the response will include most of the user info, most of the community info, and obviously all of the post info, plus more. I don’t need to make separate calls to retrieve all of that data.

    Same goes for user info. In just one call, I can retrieve all of the information as far as subscriptions, moderated communities, user settings, and more without having to make a separate call for each one.

    The issue is going to be mainly just the influx of traffic in general, not the apps themselves from what I can tell.

    I’m also including the app’s name in the user agent so that if something were to ever become a problem, anyone can reach out and discuss what they are seeing so that it can be corrected.