Hi everyone!
We’re gearing up to launch a Web3 multimedia platform designed specifically with the photography workflow in mind. In a nutshell, it’s IPFS pinning, image transformations and optimization, analytics, and copyright protection under one roof.
Right now, we’re in the private beta stage and looking for people willing to try it out and share their experience. Many of us on the team are photographers ourselves, so part of the inspiration was to create something to make our own workflow easier. But the ultimate goal is to make the app useful for many people, not just us, and that’s why absolutely all feedback is extremely valuable now.
If you’re interested, just leave a comment, and I’ll reach out to you with an invite to private Beta. Or if you’d like to look around yourself first, here’s more about the project: https://macula.link/
Good point, I’m with you on this one. The goal of the sharing mechanics is to be like a layer over IPFS that gives you additional features like adding on-the-fly image transformations (meaning you set
?width=100pxin the URL and the server processes the image before showing it to whoever requested it) and analytics (which gives you the ability to see from which sources your photos are being accessed. This can also be a huge help in fighting unauthorized use – if you see views coming from some shady site, you can immediately check it and file the copyright claim). And in addition to all this you also preserve full metadata, which (1) is useful to prove your ownership and (2) will help in further licensing since we also add metadata for getting a “licenseable” mark in Google Images.Here’s an example with one of my photos: https://jimpl.com/results/JLqNAwmLkEt4FayuZphK9Sq3?target=exif
Some of the fields are dummy data for now since we’re still in private beta stage but you can already see where this is going.
Hope this was useful, let me know if I answered your question or if you have anything else!
Does this mean direct linking isn’t possible?
By direct linking you mean accessing the image by its CID via any public gateway?
I mean a url ending in the file type that another site (like a forum) can display in line without a bunch of other code they may or may not support.
That’s the only thing I’m missing from other places. Everyone wants to drag you to their site with a bunch of peripheral display I have no interest in.
Ahhh, I see what you mean now. This is exactly our point too so once you have the link you can display it anywhere, be it a blog, comment section, git repo, etc.
Here’s an example link: https://u.stg.macula.link/LHIIkEFeTTOaRo1N8Pol4A-0
It looks a bit different and doesn’t have file extension but the point is the same.
If I do
it will work just like any regular image link.https://u.stg.macula.link/LHIIkEFeTTOaRo1N8Pol4A-0
Cool. I think some of the older places I use (that still use bbcode instead of markdown) break if you don’t have a file type in the actual url (I can’t check any time soon), but not hijacking the direct link is a good step.
I’d be interested in checking it out. Other things that would affect me actually using it full time would be the presence/quality of any tools to organize a library and what your pricing model eventually looks like. I’ve been flirting with self hosting my stuff but it’s just one of many projects I want to do and I never seem to have the time.
I appreciate the quick responses.
Hi, I checked the BBCode docs and examples and it seems it works with our Unified link right now,
Example: [img]https://u.stg.macula.link/LHIIkEFeTTOaRo1N8Pol4A-0?w=400[/img]. Here you can see that I am passing thewparams which stands forwidthand it renders it correctly on the playground https://codebeautify.org/bbcode-viewer