Can't help but think they are maintained by people close to Meta dev teams and were hand-picked for a malicious compliance, where they can just point to them as examples, and they make onboarding as complicated and expensive as possible for others.
They're both b2b products that are gonna try to find their first users by pitching the idea that you can use their products to spam WhatsApp users.
Haiket doesn't even try to hide its connection to Meta. All you have to do is to go to their website, click on press, and see in the only press release they've ever posted that its CEO holds patents in use by Meta. Here, let me save you a click: https://haiket.com/press/release-nov11.html
> Alex holds over 10 patents in voice and communication technologies, assigned to and used by Google and Facebook.
By the time this back-and-forth reaches its end, these two will find some shady b2b customers and are gonna be touted as "successful European startups".
- the default choice needs to be "strictly necessary cookies
- with other less prominent buttons for "allow all" and "deny all"
- a site is not allowed to force you to have the press a bunch of buttons or select a bunch of things to deny most/all cookies
The problem lies in enforcement. Unless you are a huge player, there is almost nil chance you're gonna get fined.
I think about the only thing missing is that they should have RFC'd a standard akin to Do Not Track, except this would have communicated to sites if your default is "strictly necessary", "allow all" or"deny all". With it being set to "strictly necessary" by default.
I am curious: why is that difficult? Define the fine as a percentage of the revenue of the company, have users report links, and pay someone to check the link and send the fine.
Sounds like easy money... I mean it's very profitable to pay people to check parking lots and fine drivers who don't follow the regulations. This should be even more profitable?
But admitting you are subject to the laws of a country/entity is one thing, sending them your books (when your company is not based there) is kind of on a different level
The gears are turning slowly, but they're doing really useful work.
The DoJ was trying to stop the Google search deal, trying to split them up etc. Big tech is too big and this is a problem everywhere.
How does this imply he has any connection to Meta? Companies license patents all the time.
> Before Haiket, Alex founded a number of technology start-ups and helped develop innovative voice solutions for Facebook and Google.
At the very least, I think it's safe to say he has some connections within Meta that he utilised for this purpose. He's definitely not a complete outsider whose startup (with no actual product) just happened to be picked by Meta.
My bad. I searched for “Meta” instead of “Facebook.” Quite a few other red flags in that press release.
> Haiket is launching the Beta trial from today, with a pipeline of future innovation for early adopters, including a pioneering silencing technology that will allow users to speak privately in public, with voice communication that only your device can hear.
Does anyone else think this sounds beyond ridiculous?
This is fairly straightforward - you have the device spew out noise with similar characteristics to human speech (ie. random overlapping syllables in the speaker's voice). Take a recording then subtract the random syllables.
Only your device can do the subtraction, because only your device knows the waveform it transmitted.
Obviously in a room with lots of reverb this will be a bit harder, since you will also need to subtract the reflection of what was transmitted with a room profile and deal with the phone moving in the room, but it sounds far from impossible.
Surely this only works if you're using the phone as a speakerphone (and are therefore almost certainly being an arsehole in public[0])?
[0] Because if it was an actual speakerphone situation, hiding your voice would be stupid.
The DMA will change nothing in this regard because the "many apps" approach is the most beneficial to users.
Why? I'd love to be an alternative whatsapp client with all kinds of new features that the official client doesn't have. Obviously you say you're building a compatible chat network, but the reality is users are just using your client to talk to whatsapp users.
Eg. one feature I'd love is some AI to automatically take any date and time someone mentions to me and put it as a draft event in my calendar. I miss so many events from big group chats I'm not paying proper attention to and suddenly everyone is saying "Whoa, you didn't come to Johns 50th birthday?!? Why not? We invited you months ago[in a group chat with 100 messages a day of mostly memes]"
Would love to know how it is "obviously" against my interest to make a chat app and have 3.3 billion users adressable instantly. Bad for internet health to be still tied to Meta, sure, but the damage was done and this is a way to reverse it.
You won't get enough people to pay you money to use your app to make it profitable. If you think you will, then you have a business already; go build it!
Which revenue? Whatsapp is for free, those 3.3 billion people use it for free, the revenue is the reselling of user data and showing them ads. Which they would do less with a 3rd party client, and as such Meta fights it tooth and nail.
> You won't get enough people to pay you money to use your app
It might surprise you but people build apps just for fun, free and open source for others to use, just to make the world better. Which really would be in this case, that's also the intention of this law.