Repost, like and reply are metrics that can be used to gauge how popular posts are, by removing that they can push whatever they want as “popular” with no real way of knowing. This is like Netflix Top 10 with no insight into the metrics.
My favorite is seeing developers directly reach out to a DB of another microservice because “it’s just easier to pull the data from there”. One of the few times I’ve literally said “bruh”
My thoughts on software in general over the past 20 years. So many programs inefficiently written and in 4th level languages just eats up any CPU/memory gain. (Less soap box and more of a curious what if to how fast things would be if we still wrote highly optimized programs)
And guess what, it can be done just as easily, if not, more easily on a federated instance. You don’t gain at real additional control over your data (and no putting “covered under license X” is about as realistic as those Facebook posts saying “I don’t give anyone access to my posts”).
I’ve said this before and I’ll say it again, realistically the only way to control your data from AI is a DRM type solution which everyone fundamentally hates.
Which is slightly better than some places I’ve seen cut the staff and keep the interns on to run with what’s left
QA vs first release to customers.
People said that about Netflix and their password crackdown… their profits went up.
What’s the point then?! Update the cell bands so people at least have an option to use them.
Transitive Property: Am I a joke to you?
Does that fall under “technically correct”?
And if you were to watch it at 60Hz you would need 82+ years to watch that one second. Hope you know exactly where you’re wanting to look or can scrub it really fast!
Edit: I can’t math. It is 82,000 years.
Thank you. So this isn’t like the TPM key extraction but closer to Spectre… got it.
I’m curious, for a non-network connected lock, how could you ensure that it’s secured with time bound parameters like they list?
Now that I’m thinking about it I guess each lock would have a private key and a CMOS of sorts to keep time. The writer could then write have the public key of each room and that could have a timestamp as part of the encrypted payload. I guess to take it further you could reverse it too with that payload having a private key of the writer and the locks could verify the private key against a public key of the writer. At that point each writer would have to have the public key of all locks, and each lock would have the public key of each writer.
At that point your payload to encode would be a timestamp of expiration and any sort of “checksum” or PSK to verify it was made by a valid writer?
When they say “side channel” do they mean with some sort of physical modification/access or purely via software means?
I wanted to upvote this but it’s sitting at 9 votes which just seems right.
You can use federated SSO. The remote site never sees your credentials but only a token that you’ve been authenticated against your home instance.
That being said, that’s probably the problem, in order to do federation a small degree of trust is required between the two instances. I guess that is already done with activityPub since you’re getting content from remote instances.
It feels like we’re hitting a point similar to politics in America. 30% will hold on no matter what, and the company is going to take them for all their worth because they know they’re die hard loyalists and aren’t leaving.
Mobile apps should be fairly obvious. It’s drives use of their application which is something they want. For most everything else, everyone* already has a phone and can do SMS, though it’s being proven to be more insecure.
Both of those options meet their needs, the needs of the customer are secondary.
Cloud was never supposed to be “cheap”. It has always been a utility based model where you pay for how much you use it. The problem is, way too many people used is as a 1:1 replacement without rearchitecting their workloads, so of course it’s gonna be more expensive.