12 votes

Topic deleted by author

6 comments

  1. [3]
    Comment deleted by author
    Link
    1. AlexSage
      Link Parent
      OMG this load time is why p2p databases won't work for most cases or the general public.

      OMG this load time is why p2p databases won't work for most cases or the general public.

  2. [4]
    Fantastitech
    Link
    Oh, neat. I've been daydreaming off and on for a couple years now about a P2P podcast client/service for podcasters to distribute popular podcasts with little to no hosting cost beyond the initial...

    Oh, neat. I've been daydreaming off and on for a couple years now about a P2P podcast client/service for podcasters to distribute popular podcasts with little to no hosting cost beyond the initial downloads. This would significantly reduce the amount of work needed for that.

    3 votes
    1. [4]
      Comment deleted by author
      Link Parent
      1. [3]
        Fantastitech
        Link Parent
        I've been reading through the API and one thing isn't clear to me. Is there a way to distribute on demand? i.e. a client is not considered a host of an entry until it's manually requested by their...

        I've been reading through the API and one thing isn't clear to me. Is there a way to distribute on demand? i.e. a client is not considered a host of an entry until it's manually requested by their client? Similar to torrent distribution?

        2 votes
        1. [3]
          Comment deleted by author
          Link Parent
          1. [2]
            Fantastitech
            Link Parent
            Let me back up a bit. My understanding is that when an entry is made in the database that it's synced to all connected clients immediately. Is this not the case? Does a client only get a local...

            Let me back up a bit.

            My understanding is that when an entry is made in the database that it's synced to all connected clients immediately. Is this not the case? Does a client only get a local copy of an entry when they run gun.get? My use-case would be surges of media downloads. I would want a client to only be connected to a database entry for a short period of time.

            So a podcast would be published to the web, and in this case stored as an object in a Gun database. A client wants this episode of the podcast. Instead of being download from a web URL found in an RSS feed, it would be retrieved from the database with get.once and played. The more people downloading the file, the more nodes with this data, and the more distributed the download would be? Then after listening the file would be deleted locally and the client would no longer be a node for that particular episode, which I'm guessing would be done using the undocumented lib/forget?

            Do I have that right? Is this a good application for Gun?

            EDIT: And am I crazy or did I not see a link to a Matrix channel for Gun discussion? I could have sworn I did but now I can't find it anywhere.

            1 vote