stevenaleach,
@stevenaleach@sigmoid.social avatar

My local network doesn't let me do much in the way of hosting anything via , but I plan to use ipfs identifiers as filenames so that users of the can run ipfs locally, fetch tracks as needed from .org that aren't already available on the network through connected peers. 1/3 century of , over forty-thousand with . https://www.tapeheads.net/threads/has-jazz-on-linecom-died.106559/#post-775733672

byjp,
@byjp@hachyderm.io avatar

@stevenaleach Exciting!
I think using CIDs as filenames might be confusing tho, as different CIDs can come from the same data (eg. you use CIDv0 but some future server sharing it uses CIDv1; or if someone switches from SHA256 to Blake3; or if that server uses different settings to yours).

The has a non-functioning (storage) and (transfer) option for retrieval they’ll hopefully be fixing, perhaps uploading with human filenames would be better?

travisfw, (edited )
@travisfw@fosstodon.org avatar

@byjp @stevenaleach
Highly relevant: RFC 6920: Naming things with hashes
https://datatracker.ietf.org/doc/rfc6920/?include_text=1
IE if you don't mind creating a directory structure, you could include in a root folder "ni", directories named for the hash algorithm. Then the files in each directory will be named, obviously, the hash the algorithm produces. A few easy examples in the "Hello World" in section 8.1
https://datatracker.ietf.org/doc/html/rfc6920#section-8.1

  • All
  • Subscribed
  • Moderated
  • Favorites
  • ipfs
  • ngwrru68w68
  • DreamBathrooms
  • thenastyranch
  • magazineikmin
  • InstantRegret
  • Durango
  • Youngstown
  • everett
  • slotface
  • rosin
  • cubers
  • mdbf
  • kavyap
  • GTA5RPClips
  • JUstTest
  • cisconetworking
  • osvaldo12
  • ethstaker
  • Leos
  • khanakhh
  • normalnudes
  • tester
  • modclub
  • tacticalgear
  • megavids
  • provamag3
  • anitta
  • lostlight
  • All magazines