this post was submitted on 12 Oct 2023
7 points (100.0% liked)

Photography

1 readers
1 users here now

Cover: https://pixelfed.social/arkadiusz

founded 2 years ago
7
Making a Simple Self-Hosted Photo Gallery With IPFS (medium.com)
submitted 1 year ago* (last edited 1 year ago) by alxwnth@kbin.social to c/photography@kbin.social
8 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[โ€“] Elena-Von-Tsss@kbin.social 2 points 1 year ago* (last edited 1 year ago) (1 children)

What somewhat discourages me from responding to the above is not so much your tone of voice, but rather seeing that you're not paying much attention to what you're reading.

So, I'll be brief.

  1. The current ToS indeed fall short, as I mentioned earlier, and they will be changed. I appreciate you highlighting this issue and your frustration about this is entirely justified. The current template doesn't align with our approach to data handling and is, quite frankly, not up to the mark.

  2. The rest of your comments seem to be rooted in your subjective take on what you generalize as "crypto" and appear to have little to do with the project at hand. You are simply dismissing the facts I clearly laid out in my initial response.

Of course, you have every right to be a snarky asshole, and the internet is filled with such individuals, mostly anonymous, with plenty of time on their hands and, perhaps, a lack of better things to do. So, go ahead and have fun.

[โ€“] hiddengoat@kbin.social 1 points 1 year ago

Your utterly dismissive tone should indicate to everyone precisely what kind of shit-tier company you're involved with.

I have more than paid attention which is why I can see what your scam-ass bullshit company is doing.

  • Get people onboard with Macula, a gateway to a distributed file hosting network that lets you do oh-so-amazing things like send basic transform information in a link. You know, like HTML from a server but on a lot of servers like a torrent. (yes, I'm doing Star Trek explanations here)
  • Integrate that usage with Kelp, your method of creating a unique identifier for an image to ostensibly serve as a copyright notice.
  • Take said notice to Anagolay, your NFT platform. Because that's what it is. It's an NFT platform. But don't trust me on that, trust their own whitepaper that directly compares it to NFTs but then goes to great pains to disassociate from NFTs: https://kelp.notion.site/Anagolay-White-Paper-v_0-3-fd9ca46a2f524e83b46ed8a0242d618d

Anagolay is a peer-to-peer network that stores records of Rights, Restrictions, and Proofs of any digital content. It empowers the users to store, claim, sell, and rent their work with the correct transfer of Rights and usage of Licenses.

In other words, NFT horseshit with a veil of "not an NFT, bro."

  • Profit at every step of the way, which is fine. That's what business do.

At no point have you clearly laid out anything that contradicts what I have said. Your statements have been deliberate obfuscation of the actual questions I have asked.

For example, I'm still waiting on an answer to what exactly you intend to do with OUR FUCKING DATA. Just saying your ToS "doesn't align with our approach to data handling" does not fucking cut it when YOU ALREADY HAVE A BETA PRODUCT PEOPLE ARE USING. Literally everything you have said and done indicates you do not actually give a shit about any portion of your company except the part that will be generating your NFT trash market.

Your company is supposed to be entirely about rights management and you can't even clearly define how you are managing our data.

Is it hard to walk in clown shoes, or do you get used to it?