It is an absolutely awful thing that I can play the new Wii sports golf and be like “oh year, I remember this course!” (from the game that came out 16 years ago)
Also I have a really good spatial memory. I think it might be the only memory I have in fact
@gwil Time to organize more of your information spatially? :o
Once I can get a decent VR setup I've been wanting to migrate to @stardustxr and start storing notes and tabs in spatial corners of my workspace.
@technobaboo @gwil URLs generally don't contain mime types since browsers get them from the Content-Type header in the response (yeah, it kinda sucks). A lot of servers sniff the content and the file ending to guess the mime type. Either way you typically need to read from the resource to know what sort it is. 😅
@technobaboo For IPFS URLs, take the stuff in the PATH_GATEWAY spec, but replace `/ipfs/` with `ipfs://`.
I'm also working on a IPLD URL spec that's along the same lines.
But generally its `ipfs://CID_HERE/path/to/file.txt` and similarly `ipns://PUBLICKEY_OR_DNS_HERE/path/to/file.txt`.
@mauve so in terms of the raw data I should just have a MIME item type that contains a MIME type and its associated data in binary as well as a URL type that can hold a single string with an ipfs, https, etc. URL in that format?
@technobaboo Hmm, I'm not sure. Personally, I'd have the mime type contain either the raw buffer for the data, a file URL for the data, or a IPFS/HTTPS URL for the data.
That way you can seamlessly attach either remote, local, or syntesized data to anything that takes a mime type object. 🤷 Not sure what sort of UI you were thinking of for this though.
@technobaboo Or maybe "Mime" isn't the right word here?
It's more like a "File" where it has a mime type describing what format it is, and a way to load it's data which might be from a URL or from raw data. E.g. the File API in web browsers: https://developer.mozilla.org/en-US/docs/Web/API/File
@mauve the idea with items is that a client creates the UI around it so it really could be anything