this post was submitted on 18 Jan 2024
790 points (98.6% liked)
Technology
59374 readers
7834 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Anyone know how the plugin developer responded?
Would be dope if the response was 'Fuck you, prove it'
e. Well, the response was in the article, big disappointment "gotta take down the plugin".
It's haier's responsibility to prove damages
Would you risk going into massive legal debt for project you make no money from? Or would you continue to develop it for yourself and no longer post it publicly.
Again, it's the pursuers responsibility to prove damages.
Pro se and wait.
And the dev might have to pay a lawyer to defend himself in court while the company tries to prove their point.
Sure, he might get it back. Maybe. But he also would likely end up in debt defending himself, even if there's no real merit to the case.
taking pro se forces the company to provide evidence and pay for lawyers while you just wait for their case to build, if they don't have a case, then there's no problem, if it gets to trial they have to prove damages, since there aren't any, that will be difficult to prove.
Taking pro se is not recommended in most situations but in this one, where the damages are entirely made up, taking pro se would not be overly tumultuous