Damn it, all those stupid hacking scenes in CSI and stuff are going to be accurate soon
- 0 Posts
- 6 Comments
That’s a bullshit explanation of cultural appropriation and the person you heard it from is an idiot. Actual cultural appropriation is when you take something from another culture and either erase or overwrite its origin, so the original culture in its original form becomes forgotten.
For example, when white artists re-recorded songs from black artists and specifically removed them from the credits and claimed them as their own, that was cultural appropriation. When movie studios chopped up Indian culture and presented it in a completely distorted and inaccurate light, so much so that the original meanings were lost, that was cultural appropriation.
Simply being a participant in someone else’s cultural celebration is not cultural appropriation.
I’m guessing the data sets they used were collected at different start times and they didn’t want to truncate it
fidodo@lemmy.worldto
Technology@lemmy.world•Nightshade, the free tool that ‘poisons’ AI models, is now available for artists to useEnglish
0·2 years agoI still wouldn’t call it stealing, but I guess “broke open source code licenses” doesn’t have the same impact, but I’d prefer accuracy.
They’re super rare. I’ve not gotten one once in decades, whereas I’ve encountered countless viruses on Windows. Linux is more secure, but also it’s just a smaller target. Best way to avoid viruses is to use an OS nobody else wants to use *taps head




It’s just not worth it until your monolith reaches a certain size and complexity. Micro services always require more maintenance, devops, tooling, artifact registries, version syncing, etc. Monoliths eventually reach a point where they are so complicated that it becomes worth it to split it up and are worth the extra overhead of micro services, but that takes a while to get there, and a company will be pretty successful by the time they reach that scale.
The main reason monoliths get a bad rap is because a lot of those projects are just poorly structured and designed. Following the micro service pattern doesn’t guarantee a cleaner project across the entire stack and IMO a poorly designed micro service architecture is harder to maintain than a poorly designed monolith because you have wildly out of sync projects that are all implemented slightly differently making bugs harder to find and fix and deployments harder to coordinate.