I would like to know if it is possible to have a decentralized iptv-org/iptv database in nostr and ipfs.
IPFS: The advantage of this is that we can distribute the data and avoid having a single point of failure or censorship.
But if you run IPFS locally: Your computer contributes to the public network, but your IP address and any content you are requesting or making available may be exposed. Content you request via IPFS is verified before being offered to you. Network requests may not use your browser's proxy and DNS settings.
And if you run IPFS remotely: Protects your IP address and content you are requesting from potential third-party observers, but not from the public gateway operator. The gateway operator is responsible for ensuring that the content offered to you via the gateway is the content you requested. Additionally, your computer does not contribute to the IFPS (Interplanetary File System) network.
But the main concern: The main concern is the URL contains the hash and it changes with each update. The goal of this project is to have a static URL that always returns updated url. If you have the IPFS URL, it will get out of date quickly. See this here: https://hatthieves.es/ipfs-upload/ or https://share.ipfs.io/#/
However, this doesn't mean you need to remember a long string of CIDs — IPFS can find the latest version of your file using the IPNS decentralized naming system, and DNSLink can be used to map CIDs to human-readable DNS names.
Nostr: We can have a means or channel for distributing IPTV links instead of having our own server. The disadvantage is that the relays do not communicate with each other, they have their own rules and conditions. According to the Amethyst app documentation (nostr client), it can be bad in this context: "Relays know your IP address, your name, your location (guessed from IP), your pub key, all your contacts, and other relays, and can read every action you do (post, like, boost, quote, report, etc) except for Private Zaps and Private DMs. While the content of direct messages (DMs) is only visible to you and your DM counterparty, everyone can see when you and your counterparty DM each other. If you want to improve your privacy, consider utilizing a service that masks your IP address (e.g. a VPN or Tor) from trackers online. The relay also learns which public keys you are requesting, meaning your public key will be tied to your IP address. Information shared on Nostr can be re-broadcasted to other servers and should be assumed permanent for privacy purposes. There is no way to guarantee the deletion of any content once posted."
@Alstruit Edit:Could you re-evaluate or reopen my issue and give me some feedback if what I wrote here makes sense?
Hi @Alstruit
I would like to know if it is possible to have a decentralized iptv-org/iptv database in nostr and ipfs.
IPFS: The advantage of this is that we can distribute the data and avoid having a single point of failure or censorship.
But if you run IPFS locally: Your computer contributes to the public network, but your IP address and any content you are requesting or making available may be exposed. Content you request via IPFS is verified before being offered to you. Network requests may not use your browser's proxy and DNS settings.
And if you run IPFS remotely: Protects your IP address and content you are requesting from potential third-party observers, but not from the public gateway operator. The gateway operator is responsible for ensuring that the content offered to you via the gateway is the content you requested. Additionally, your computer does not contribute to the IFPS (Interplanetary File System) network.
But the main concern: The main concern is the URL contains the hash and it changes with each update. The goal of this project is to have a static URL that always returns updated url. If you have the IPFS URL, it will get out of date quickly. See this here: https://hatthieves.es/ipfs-upload/ or https://share.ipfs.io/#/
From the official page: https://ipfs.tech/
Nostr: We can have a means or channel for distributing IPTV links instead of having our own server. The disadvantage is that the relays do not communicate with each other, they have their own rules and conditions. According to the Amethyst app documentation (nostr client), it can be bad in this context: "Relays know your IP address, your name, your location (guessed from IP), your pub key, all your contacts, and other relays, and can read every action you do (post, like, boost, quote, report, etc) except for Private Zaps and Private DMs. While the content of direct messages (DMs) is only visible to you and your DM counterparty, everyone can see when you and your counterparty DM each other. If you want to improve your privacy, consider utilizing a service that masks your IP address (e.g. a VPN or Tor) from trackers online. The relay also learns which public keys you are requesting, meaning your public key will be tied to your IP address. Information shared on Nostr can be re-broadcasted to other servers and should be assumed permanent for privacy purposes. There is no way to guarantee the deletion of any content once posted."
@Alstruit Edit: Could you re-evaluate or reopen my issue and give me some feedback if what I wrote here makes sense?