home.social

#contentdelivery — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #contentdelivery, aggregated by home.social.

  1. Going to #IBC2025? 🚀

    KenCast will be in Halls 1–3 & 8 with partners, talking:
    #broadcast · #ATSC3 · #5Gbroadcast · #ContentDelivery

    👉 Let’s connect: bit.ly/4lTn1BR

    Catch our CEO Henrik Axelsson on:
    📍 Serving the Software-Defined Satellite Market of the Future
    📅 Sept 13 | Room E105

  2. @blueghost @peertube @tilvids
    If already making videos, yes. That would be wonderful!

    Do mention that the videos are available on Fediverse in your intro or outro too. 😉

    Re #contentDelivery we notice the need to provision services. It is great that TILvids can help but there are Fediverse instances shutting down due to inability to deliver content, such as our instance. So we're exploring a #P2P proposal we're calling #GlutPlug, to help instances stay online.

    Use the tag to learn more 🙂

  3. @blueghost @peertube @tilvids
    If already making videos, yes. That would be wonderful!

    Do mention that the videos are available on Fediverse in your intro or outro too. 😉

    Re #contentDelivery we notice the need to provision services. It is great that TILvids can help but there are Fediverse instances shutting down due to inability to deliver content, such as our instance. So we're exploring a #P2P proposal we're calling #GlutPlug, to help instances stay online.

    Use the tag to learn more 🙂

  4. @volkris @Mastodon @msaunders

    Yes and no, we meant decentralised as compared to the legacy offerings.

    The way Master'don will trend is back torwards #reCentralisation, because of the #contentDelivery issue.

    iwrc, some instances don't try to serve all content and #hotLink(?) to the originating instance, but that has issues too, incl. #privacy.

    That's why we suggest servers play a #conductor's role. With a #glutPlug they'd hotlink to I2P hosted content served by fedizens who boosted it.

  5. @volkris @Mastodon @msaunders

    Yes and no, we meant decentralised as compared to the legacy offerings.

    The way Master'don will trend is back torwards #reCentralisation, because of the #contentDelivery issue.

    iwrc, some instances don't try to serve all content and #hotLink(?) to the originating instance, but that has issues too, incl. #privacy.

    That's why we suggest servers play a #conductor's role. With a #glutPlug they'd hotlink to I2P hosted content served by fedizens who boosted it.

  6. @volkris @Mastodon @msaunders

    Yes and no, we meant decentralised as compared to the legacy offerings.

    The way Master'don will trend is back torwards #reCentralisation, because of the #contentDelivery issue.

    iwrc, some instances don't try to serve all content and #hotLink(?) to the originating instance, but that has issues too, incl. #privacy.

    That's why we suggest servers play a #conductor's role. With a #glutPlug they'd hotlink to I2P hosted content served by fedizens who boosted it.

  7. @volkris @Mastodon @msaunders

    Yes and no, we meant decentralised as compared to the legacy offerings.

    The way Master'don will trend is back torwards #reCentralisation, because of the #contentDelivery issue.

    iwrc, some instances don't try to serve all content and #hotLink(?) to the originating instance, but that has issues too, incl. #privacy.

    That's why we suggest servers play a #conductor's role. With a #glutPlug they'd hotlink to I2P hosted content served by fedizens who boosted it.

  8. @hrefna

    > Unsafe

    The most unsafe part about #fediverse is master-don dominates with its #antiFeatures.

    M'don is not much decentralised as many assume (see #CDNs). We just had a little rant about it.

    We cannot protect fedizens, without protecting instances themselves. Adoption of I2P and/or at least proposals like #GlutPlug to help decentralise #contentDelivery will protect instances, but such discussions are nowhere.

    Case in point, even slow-moving #bitcoin has #I2P support now.

    #privacy

  9. @hrefna

    > Unsafe

    The most unsafe part about #fediverse is master-don dominates with its #antiFeatures.

    M'don is not much decentralised as many assume (see #CDNs). We just had a little rant about it.

    We cannot protect fedizens, without protecting instances themselves. Adoption of I2P and/or at least proposals like #GlutPlug to help decentralise #contentDelivery will protect instances, but such discussions are nowhere.

    Case in point, even slow-moving #bitcoin has #I2P support now.

    #privacy

  10. @hrefna

    > Unsafe

    The most unsafe part about #fediverse is master-don dominates with its #antiFeatures.

    M'don is not much decentralised as many assume (see #CDNs). We just had a little rant about it.

    We cannot protect fedizens, without protecting instances themselves. Adoption of I2P and/or at least proposals like #GlutPlug to help decentralise #contentDelivery will protect instances, but such discussions are nowhere.

    Case in point, even slow-moving #bitcoin has #I2P support now.

    #privacy

  11. @hrefna

    > Unsafe

    The most unsafe part about #fediverse is master-don dominates with its #antiFeatures.

    M'don is not much decentralised as many assume (see #CDNs). We just had a little rant about it.

    We cannot protect fedizens, without protecting instances themselves. Adoption of I2P and/or at least proposals like #GlutPlug to help decentralise #contentDelivery will protect instances, but such discussions are nowhere.

    Case in point, even slow-moving #bitcoin has #I2P support now.

    #privacy

  12. @hrefna

    > Unsafe

    The most unsafe part about #fediverse is master-don dominates with its #antiFeatures.

    M'don is not much decentralised as many assume (see #CDNs). We just had a little rant about it.

    We cannot protect fedizens, without protecting instances themselves. Adoption of I2P and/or at least proposals like #GlutPlug to help decentralise #contentDelivery will protect instances, but such discussions are nowhere.

    Case in point, even slow-moving #bitcoin has #I2P support now.

    #privacy

  13. @zleap
    We tend to ignore the turdsite stuff.

    Since Monday, a new interest of ours is in using the peer-to-peer network (#I2P) to #democratise fediverse #contentDelivery. So when a person positively interacts with a toot the content is retained to be served by that person (if they have not flagged content and their battery is above 50%).

    In this context moderation becomes self-fulfilling, and the use of I2P protects the users from survellance and targetting.

    #cdns #fediMeta #glutPlug #i2pfs

  14. @zleap
    We tend to ignore the turdsite stuff.

    Since Monday, a new interest of ours is in using the peer-to-peer network (#I2P) to #democratise fediverse #contentDelivery. So when a person positively interacts with a toot the content is retained to be served by that person (if they have not flagged content and their battery is above 50%).

    In this context moderation becomes self-fulfilling, and the use of I2P protects the users from survellance and targetting.

    #cdns #fediMeta #glutPlug #i2pfs

  15. @zleap
    We tend to ignore the turdsite stuff.

    Since Monday, a new interest of ours is in using the peer-to-peer network (#I2P) to #democratise fediverse #contentDelivery. So when a person positively interacts with a toot the content is retained to be served by that person (if they have not flagged content and their battery is above 50%).

    In this context moderation becomes self-fulfilling, and the use of I2P protects the users from survellance and targetting.

    #cdns #fediMeta #glutPlug #i2pfs

  16. These are essentially #baitAndSwitch attacks.

    A few days ago we brainstormed how #I2P might be able to democratise #contentDelivery in #Fediverse, in ways that protect users.

    See our #GlutPlug post.

    We hope that #Mastodon, #Akkoma, #FireFish and #Epicyon are able to seriously consider how they might do this. App developers for #Tusky and #Fedilab also.

    #i2pfs

  17. These are essentially #baitAndSwitch attacks.

    A few days ago we brainstormed how #I2P might be able to democratise #contentDelivery in #Fediverse, in ways that protect users.

    See our #GlutPlug post.

    We hope that #Mastodon, #Akkoma, #FireFish and #Epicyon are able to seriously consider how they might do this. App developers for #Tusky and #Fedilab also.

    #i2pfs

  18. My advice if you're trying to start your own #mastodon isntance: USE CLOUD STORAGE! I'm specifically using #s3, but there are other options. If you end up federated with a lot of other servers you're going to be downloading a lot of media, and that will fill up your local storage quickly. S3 is pretty cheap, and a better form of #contentdelivery anyway. #advice #gettingstarted #twittermigration #selfhosted

  19. My advice if you're trying to start your own #mastodon isntance: USE CLOUD STORAGE! I'm specifically using #s3, but there are other options. If you end up federated with a lot of other servers you're going to be downloading a lot of media, and that will fill up your local storage quickly. S3 is pretty cheap, and a better form of #contentdelivery anyway. #advice #gettingstarted #twittermigration #selfhosted

  20. My advice if you're trying to start your own #mastodon isntance: USE CLOUD STORAGE! I'm specifically using #s3, but there are other options. If you end up federated with a lot of other servers you're going to be downloading a lot of media, and that will fill up your local storage quickly. S3 is pretty cheap, and a better form of #contentdelivery anyway. #advice #gettingstarted #twittermigration #selfhosted

  21. My advice if you're trying to start your own #mastodon isntance: USE CLOUD STORAGE! I'm specifically using #s3, but there are other options. If you end up federated with a lot of other servers you're going to be downloading a lot of media, and that will fill up your local storage quickly. S3 is pretty cheap, and a better form of #contentdelivery anyway. #advice #gettingstarted #twittermigration #selfhosted