Most of the individuals targeted by Kiwifarms are not running for office, or own prominent businesses. They are for the most part unemployed nobodies who live at home. I don't see any public interest in naming these people.
1,857 karma · joined September 3, 2020
Most of the individuals targeted by Kiwifarms are not running for office, or own prominent businesses. They are for the most part unemployed nobodies who live at home. I don't see any public interest in naming these people.
I'm not arguing that the court should ignore the law and rule otherwise, I'm arguing that the law itself should be changed.
Something can be both legal and ethically wrong. You can apply your same reasoning to Cloudflare's censorship of Kiwifarms: nothing Cloudflare did in this case was illegal, so what is your issue with it?
If Kiwifarms users can't see that what they are doing already is unethical, why should anyone believe that they truly think these other illegal actions are wrong? They just know not to talk about it out loud because then you will actually get in trouble with the law.
The only reason the site has been able to get away with it for so long is because they are targeting vulnerable people who are least well equipped to legally defend themselves.
Something can be legal and wrong. Sometimes the law is out of date with reality.
Facilitating/organizing mass harassment of mentally ill people should be against the law.
It shouldn't be up to harassed individuals to seek justice, prosecutors should be able to go after them. If the issue is with the law itself, the government needs to effectively legislate.
When the legal system fails, people turn to vigilante justice, and we get this mess instead. People feel so strongly that Kiwifarms should be taken offline that they engage in illegal behavior themselves.
I think it stands as a good example of how restrictions on certain kinds of speech that look very reasonable in a moment of crisis can in turn be judged very poorly in the long term.
I don't personally know where I stand on the free speech issue, I just want people to stop using this stupid "fire in a crowded theatre" analogy.
“Fire in a theatre” is a great example of using a reasonable sounding analogy to support behaviour (prosecuting anti-war campaigners) that today we judge very poorly.
If you want an analogy for when it's correct to place restrictions on speech this one is a very poor choice due to it's historical context.
I'm sure other social media platforms have tried to build recommendation algos that are as good as TikTok's, they just haven't succeeded. And now I'm not sure that a high quality recommendation algorithm is actually in the consumers interest.
But anecdotally for myself and anyone I know who has used TikTok, the app is just so much more addicting than any other social media has been before. I'm not a social media newcomer, I have used social media nearly all my life. I have used instagram in the past.But never before have I felt the same addiction/compulsion that exists with TikTok. I don't think this is that unusual an experience, have you tried using the app yourself?
TikTok is seriously affecting peoples quality of life en-masse in a way that social media has never achieved before. Any social media person will tell you how insane the numbers are on TikTok compared to their competitors.
If I'm being charitable, they made a mistake in their analysis, if I'm uncharitable they didn't care about the methodology and went in looking for a way to write a provocative conclusion like "86% less purchasing power". Obviously a lot of energy was spent here drawing up the pretty infographics, probably should have spent more energy getting the basic statistics correct first?
Manufacturers can't justify producing a more reliable product at a higher price point, because there isn't really a way to get consumers to trust that it really is a more reliable product worthy of the price.
And these are just amateur players. Maybe it's not 6000 calories but it is a significant increase over the base rate.
It’s impossible to find the actual image from the search results if the source is pinterest now that Google removed the direct image link from the search results.
You have to record which ports your applications listen on, which subdomains are used for what, how to access that storage bucket with the data files in it etc. somewhere. The moment you have more than a couple of individual services managing this all by hand becomes a nightmare. You need a really strong culture of good practice to make sure that the exact production config actually ends up in source control.
You can be a k8s expert, or an expert in your own home-spun configuration management/git-ops workflow. But not having any workflow here just isn't an option in my opinion. You too easily end up with spaghetti infrastructure that everybody is too scared to touch. With k8s I can take my repo of yaml and change cloud providers in an afternoon.
Graphql itself has no concept of versioning so I need to go out of my way to host a different schema at a different endpoint. And god help any client that's not consistently up to date with the latest schema in all places. You want to query for new feature X only available in api v2, but your client is on api v1? Better go back and upgrade all your existing api v1 schema queries first. Or have a separate gql client for each api version, and remember to use the correct one in the correct place.
Saying "just use better api design" isn't an answer to missing maps. Maybe I am dealing with third party data where I don't have control over the schema?
The limitations of the query language make code size explode the moment you step outside simple toy examples. It doesn't have any concept of a JOIN, or of the actual relationships between your types (graphql has no concept that me == me.parent.child). You end up writing data loaders for every type so that loops in your schema can be resolved efficiently.
Managing permissions is so much more of a pain compared to REST because exactly what data is returned is so much more dynamic. If you have some confidential data nested 10 layers deep in the query, you get two choices. Either fail the entire query with a NotAllowed based on one deeply nested field that the client maybe does not even care about, or you have to make your schema super loose and make every single field that's subject to permission management nullable. So much easier on a REST endpoint because the response is more constrained.
I bought an iphone around the launch of the Pixel 4, which is now nearing it's end of support. Meanwhile Apple has provided the latest updates to devices that launched 7 years ago.