Hacker News new | past | comments | ask | show | jobs | submit | hgezim's comments login

Oh interesting. And yes YouTube-dl is a good comparison.

To be clear, I’ve had a few accounts on Midjourney used mostly for testing and demo purposes. At the moment I don’t have any Midjourney account hence TOS violation doesn’t apply.


I think you can make midjourney stop by using social media pressure, but you need to improve communications. For example don't start with "I'm making 16k a month" because most will think you can afford a lawyer.

Also, I repeat, consider explaining better what you do and what exactly are they accusing you of doing wrong and why they are wrong in doing so.

Also now that I see the screenshots, the way you phrased things it did look like you were the official midjourney api, so the trademark violation is there for sure.


Thanks for the feedback.

I've made some changes to help avoid the confusion: https://share.cleanshot.com/Gl1fg0gx


I hope you will find the support to overcome this. Good luck


Now this is what I’m here for!

Thanks so much for taking the time to write this

Yeah if they do release an API I’m totally done. I honestly thought I’d have 3-6 months before they did but that’s not the case.

Do you see a world where I might be able to reconcile and have a positive outcome?


Yes. Build your own midjourney and provide api access to it.


They’re huge. I’m sure their toilet paper rolls are make of $16k bills

I used to worry that the biggest threat was them releasing an API.

I’ve since learned that they won’t do that because they charge monthly fees to their customers and when a customer doesn’t use their credits, the credits don’t roll over and Midjourney pockets the cash.

Pay per use is bad for their business model.


Based on your growth rate they'll have more toilet paper in the future though. It would be interesting to try to discover a way to coexist, and I wonder if everyone at Midjourney hates you with equal passion or if some are sympathetic or even see value.


I was really hoping to build out an amazing API product and when time came where they want to release one it would make more sense to acquire us. Alas.


Being a wise and thoughtful business owner, you already ran this concept by your own corporate attorney to get a written legal opinion before circumventing their TOS, right? ... No??

IMHO, stop calling yourself a Midjourney API of any kind and stop providing a service that uses Midjourney as a backend. You are not authorized to run Midjourney jobs using other people's account credentials; that's the TOS violation. Your lawyer will explain this to you.


Yup, sure did. Just like I check with HR when I pass notes to my self on Slack where I'm the only member


lol .. I should’ve posted this autocomplete answer to start with


I’m not forcing them to provide me a service at all. I’m not using their service. My customers happen to also be their customers.


> I’m not using their service.

You're not scraping Mj results generated with other people's credentials? You're going to have fun convincing a judge of that.


Thanks! Complying means what, to you?


> Apple would have to be staffed by idiots to pay you for "noticing" that.

Do you know how quotes work? Do you work for Apple?

> Sure, it should be fixed

Glad you're on my side here! That's what I'm saying. It should be fixed.

Were you expecting this behaviour? This isn't strange to you? Again, do you work for Apple?


Hey thanks for this take. Definitely feels like the approach I should take based on their behaviour.

Besides, what’s the harm in me discussing “intended behaviour”?


I recommend waiting the industry standard 90 days before volunteering intended behavior.


Why wait? The point of the 90 days is to give them time to fix it, but if they consider it intended behavior, they aren't going to fix it.


If they don't intend to fix it, then what's the problem with waiting? The bug's still gonna be there in 90 (minus however long it's already been) days and rushing disclosure really doesn't reflect well on you as a researcher to the rest of the industry. Ofc if you have your own bug, you're welcome to disclose it whenever you want, even violating NDAs if you feel like the vendor hasn't gone far enough. There may be legal repercussions with that last bit, but again, that's up to you.


Oh that’s cool! I forgot about this!


Maybe I'm drinking my own koolaid here but I don't feel safe when I use this Apple device regularly.

How does Apple establish "prior art" if I go public with it? Can someone else claim credit for it?


> How does Apple establish "prior art" if I go public with it?

You're not going public with the HOW, only the effects. Reread my comment about asking your trusted peers, please.


And then send Apple my survey results?! Not seeing the light at the end of the tunnel here.


You're assuming your peers will agree with you. I'm gently suggesting that they may not, and you need that check.

You might be right. It might be the next Meltdown vulnerability. But it might not, and Apple already told you it isn't, and that's why you need to talk to your peers.


I initially tried DALL-E and SD but they don't compare, unfortunately.


If by "tried" you mean you tested the same prompts, then yes, I'm sure the results weren't as good. Generally speaking, the reverse is usually true too.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: