Safe harbour equivalent rules should apply, no? That is, the platforms should not be held liable as long as the platform does not permit for illegal activities on the platform, offer proper reporting mechanism, and documented workflows to investigate + act against reported activity.
It feels like a slippery slope to arrest people on grounds of suspicion (until proven otherwise) of lack of moderation.
They’re keeping everything anyway, so what’s preventing them from doing a DB look up to see if it (given a large enough passage of text) exist in their output history?
What’s the resources requirements for the 405B model? I did some digging but couldn’t find any documentation during my cursory search.
You didn’t wreck the big corps. You opted yourself out of their warranty thereby saving them any money they would’ve had to spend on repairing your purchase during the defined warranty window. If anything you lined their pockets by making yourself a cheaper customer.
It is probably best to think nothing on Lemmy is private. Any instance with at least one user subscribed to a community will receive updates (messages and votes) on the community. Instance admin can go into the database to see any private message between any user on that instance.
Apple is implementing it because China requires all 5G phones to support RCS to get certified.
Apple did not do this because they suddenly have a change of heart about the green bubbles. Apple did not do this to spite regulatory bodies and ‘malice compliance’ with some interoperability mandate.
This is not a move to make messaging more secure with the green bubbles. This is not a move to make messaging better with the green bubbles. This is a move so they can continue to sell phones in China.
What kind of attacks, against what service?
DDoS? It’s cheaper to hire botnets to attack than to defend. You’d most likely still be knocked off even just by the amount of traffic that leaks through your proxy before the VM gets cut off at the data centre. Specifically: it is much more likely that data centres will give higher thresholds before null routing your VM than your residential ISP would be wiling to tolerate.
Brute force on shell? SQL injection? Remote shell execution? Deploying the extra layer will not protect you from these as your own proxy will not give you WAF.
It is always important to know why you’re doing something, before anyone can prescribe a solution.
So just because they don’t know technology like you do, they should be left behind the times instead of taking advantage of advancements? A bit elitist and gate keeping there, don’t you think?
Everyone have their own choices to make, and for most, they’ve already decided they’d rather benefit from advancements than care about what you care about.
Having seen some spicy pillows in my times… I’d hate to be onboard if any of the battery containers becomes a bouncy castle.
They do, and they’ve shared the counter measure (lockdown mode) with the world.
If a nation state will individually target someone, they don’t need to doom scroll on insta (nor do they need to). Locking down the phone to the bare minimum for these kind of people is the appropriate level of response.
"Molecular-genetic testing has been completed," it said in a statement.
"According to its results, the identities of all 10 deceased have been established, and they correspond to the list published in the flight manifest."
Not sure what’s more impressive; fact that they were able to turn the test results back so quickly, or fact that all 10 deceased, including the flight crew, have their DNA in some sort of database. Isn’t it supposed to take weeks to do the analysis?
Opening up the chip is great, but there needs to be a standard way to consolidate them all into one app/interface. Much like how HomeKit brings everything into one place, the Wallet (or some updated API based variant) needs to remain the central place, so we don't end up getting littered with vendor specific apps for different payment systems.