jaller94

joined 3 years ago
[–] jaller94@discuss.tchncs.de 1 points 3 weeks ago

Lots of No Man's Sky and a bit of Paralives. Formerly I also enjoyed a ton of Euro Truck Sim 2 and Deep Rock Galactic on the Steam Deck. And some 11/10 story exploration games that sadly can only be played once: Outer Wilds and Tacoma.

[–] jaller94@discuss.tchncs.de 1 points 1 month ago

I have not tried it via the network, only on my local Kubo node. That worked decently well but is probably just a kind of overhead when reading it from local storage.

Chunked files should work well for video streaming of static video files, yes. Given that you have a reliable node to fetch from, it would probably be fast enough and support seeking (skipping to a certain timestamp).

Your real benefit is probably going to be the caching, immutability, and potential pinning as well as redistribution.

For most live streams, it would probably not be a good fit. But maybe with good signaling for a client to receive IPFS addresses and a very reliable and fast node to fetch from, it might be an option to stream a video in small chunks. But maybe your use cases favours completeness and immutability over stream stability and low latency.

[–] jaller94@discuss.tchncs.de 1 points 1 month ago

Glad to see more support for IPFS. What makes you like it? What have you tried so far?

[–] jaller94@discuss.tchncs.de 1 points 1 month ago

As you mentioned, IPFS addresses link to a specific content that cannot change.

For changing content, there is IPNS which stays native to the IPFS ecosystem but requires you to host an IPFS node (or find and trust an IPNS provider). An IPNS key can link to one folder (or file). A kubo node can host multiple IPNS keys.

Another option is using a different protocol to distribute the latest IPFS address to your content, e.g. HTTP, Matrix, RSS, E-Mail, ActivityPub, ATProto, Git (HTTPS or SSH).