I found the update 404 media article, this article is based on: https://www.404media.co/heres-the-pitch-deck-for-active-listening-ad-targeting/
It’s behind a paywall, and I couldn’t found a way to remove it. But from the top screenshot it seems like it’s the same bullshit from the same company… We know from the past that they lie about this, why is it a news that they did the same thing again?
Better article about this story:
This is nearly a year old news, and noone ever could prove it.
CMG is simply lying. Also originally it was not “leaked” it was published on their website, it’s just the same bullshit from different source.
It was not just a “leak” this was literally on their website a year ago: https://arstechnica.com/gadgets/2023/12/no-a-marketing-firm-isnt-tapping-your-device-to-hear-private-conversations/
Marketing people bullshitting to get investor money. Anyone can imagine non existent technology and lie on the internet, you don’t have to believe everything
Yeah, maybe “working on” was too generous, “aware of the issue and some preliminary work was already done” would have been more correct
Here is some recent discussion if it’s feasible at all: https://github.com/microg/GmsCore/pull/2077
MicroG devs are working on fakeing play integrity api since 2023: https://github.com/microg/GmsCore/issues/2050
it seems that play integrity continue to change internally day to day… He is waiting that google stabilize it. Then will be a pull request.
Is snapchat still a thing? Never used that but I thought from screenshots and memes that tiktok killed it (never used that either)
But it’s a Friendica post, not from Mastodon. You can’t write such a long posts on mastodon
Easer is not perfect, but really close:
Redmis usually have a good 3rd party rom support, if you can open the bootloader. Literally any rom is a better experience than MIUI or whatever they call that nowadays.
There is already a crdroid official available: https://xdaforums.com/f/xiaomi-redmi-note-13-pro-5g-poco-x6-5g.12860/
That video is till up: https://www.youtube.com/watch?v=Vj04MKykmnQ
She went there, because in the support forum the manufacturer replied that they can only give the source code in person.
Actually that’s acceptable, and does not violate GPL, they just expected that noone will show up in their sweatshop. GPL does not define how you should make the source available.
Since I stopped using mainstream socialmedia I can’t follow musicians I’m interested in. Some have a bandcamp page and rss works there, but they just upload their albums there, nothing else. At least I get notified about new releases. I tried to follow facebook and instagram pages via rss-bridge, but it’s not working for years now. My selfhosted bibliogram sometimes work, but it’s unmaintained so it will die at some point if instagram changes something. (I just found there is a maintained fork, yess) My ip usually gets blocked, so I get all posts once a week only in batch.
So I’m interested, unfortunately none of them enabled fedi integration yet, (afaik it’s a settings for them in threads) so I’m waiting when they will enable it for everyone.
I don’t want to debate about politics or whatever you are afraid of.
There was a vote about it in !meta@lemm.ee : https://lemm.ee/post/851217
I wanted to vote against defederation (edit: i was offline that week or something, I can see I didn’t vote) I liked on this instance that we are treated as adults, and the admin let us decide what we want to see. You can block instances if you want. Defederating with Threads even before we can see how it would work goes against this philosophy.
Afaik there is no way to see anything from threads on lemmy yet, connection with mastodon like services work only, so we are again debating about a not yet existing thing.
If it will work between threads and lemmy I will look for another instance where I can devide what I want to see.
I’m not familar with shelly, but they don’t use MQTT autodiscovery? If they use it you should have a corresponding HA entity or device of each switch. Then you can use built in tools or templates in automations, and don’t directly mess with MQTT. That’s much easier and stable.
If they don’t use autodiscovery you can create HA entites via configuration.yaml manually
It’s a strange diagram but shows what you have to know. If you ever seen different keyed m.2 cards, you should understand this. The important thing is the location of the keys, the notch. All m.2 cards has an ‘up’ and ‘down’ side, it shows only the ‘up’ side. You have to look inside the receptor to see the pins, that’s why it shows both sides, it’s not possible to see one side only on the receptor as they are in a plastic casing. Usually you can’t see the pins on the mobo, only the key.
You can see a similar diagram on wikipedia, both sides of receptor, top side of card:
The offset you were writing about doesn’t matter, it actually helps. You can’t accidentally insert the card upside down. The location of notches also help with this, as not all possible notches used yet, but in the future it could change.
These connectors are really small. The receptor is similar how sodimm connector works, but smaller. Are you also afraid about inserting a ram in an laptop? It’s basically the same.
Read more about the connector in wikipedia, I’m really happy this slowly replaces sata, msata, mpcie and even pcie in current pcs.
You are right. The user you are replying to has no idea what they write about, as they confessed in another comment.
You seem to love spreading misinformation on the web. Why are you commenting 4 times if you are not familiar with the topic?
This is an m.2 connector. You have to secure it with a screw on the other side. It’s nearly impossible to mess it up.
Apple frequently uses proprietary connectors, I don’t know which one you are reffering to. I won’t guess because I’m not very familiar with all apple connectors.
You don’t have to comment on a topic if you are not familiar with. Please stop.
How this photo related to the fediverse? c/lostlemmings?
Nice, I have a similar one. Things I also do there:
flatpak updatetldr -uto update tldr pages