0x0

joined 1 year ago
 

cross-posted from: https://lemmy.world/post/19576214

Imagine your car playing you an ad based on your destination, vehicle information—and listening to your conversations.

Ford has patented a system that, per the filing, would use several different sources of information to customize ad content to play in your car. One such information stream that this hypothetical system would use to determine what sort of ads to serve could be could be the voice commands you’ve given to the car. It could also identify your voice and recognize you and your ad preferences, and those of your passengers. Finally, it could listen to your conversations and determine if it’s better to serve you a visual ad while you’re talking, or an audio ad when there’s a lull in the conversation.

If the system described in the patent knew that you were headed to the mall on the freeway based on destination information from the nav system and vehicle speed, it could consider how many ads to serve in the time you’ll be in the car, and whether to serve them on a screen or based through the audio system. If you respond more positively to audio ads, it might serve you more of those—how does every five minutes sound?

But what if the weather’s bad, traffic is heavy, and you’re chatting away with your passenger? Ford describes the system using the external sensors to perceive traffic levels and weather, and the internal microphone to understand conversational cadence, to “regulate the number (and relevance) of ads shown” to the occupants. Using the GPS, if it knows you’ve parked near a store, it might serve you ads relevant to that retail location. Got passengers? Maybe you get an audio ad, and they get a visual one.

Given how consumers feel about advertising and in-car privacy, it is difficult to imagine an implementation of this system that wouldn’t generate blowback. But again, the patent isn’t describing some imminent implementation; it just protects Ford’s IP that describes a possible system. That said, with the encroachment of subscription-based features, perhaps it’s only a matter of time before you’re accepting a $20/month discount to let your new Ford play you ads on your commute.

[–] [email protected] 3 points 1 week ago

since you now often have to implement things at two places at once.

Huh? Header files should only have declarations, unless you're screwing around with templates.

[–] [email protected] 3 points 1 week ago* (last edited 1 week ago)

The installer is the handbook.

USE flags are freakin' awesome.

It can let you install two different versions of a library.

You can install the binary versions of some big packages like firefox.

Edit: while USE flags are generic, you can also set specific per-package flags.

[–] [email protected] 2 points 2 weeks ago

Of course, you’re right xmpp evolved to get PubSub extension as an “optional feature” but because of its availability (or rather lack) - most servers didn’t support it even the client did support, xmpp didn’t win the acceptance of the end-users. It got some attention in the business world (cisco jabber) but not in the retail.

That XMPP's extensibility is in itself a strength and a weakness is indeed a valid argument, as you've exemplified. I was expecting you'd criticize OMEMO though...

Business cannot work forever without clients willing to pay or at least use, so it died off even in the business.

No, it didn't die off, it's still used. IRC is still used as well, probably more or less at the same level. But if you define usage as "used in business" well then probably just a few cases, yes.

I hadn't heard of Cisco Jabber but i've heard of Google and Facebook - both companies' messengers were, initially, based on XMPP but they EEE'd it once they got enough users and walled their gardens, dealing a major blow to the protocol.

End of story, try not to fighting with the straw men you created.

Can i fight my inner daemons at least? Please?

[–] [email protected] 6 points 2 weeks ago

Putting up with people and not murdering them.

[–] [email protected] 2 points 2 weeks ago (1 children)

I was under the impression XEP-0060 solves that.

[–] [email protected] 3 points 2 weeks ago (3 children)

XMPP is a bad match.

The X is for extensible, so are a whole bunch of other protocols and people haven't stopped using them, they get improved upon (for the most part).

[–] [email protected] 7 points 2 weeks ago (7 children)

XMPP is very old

Seriously? That's your argument? So is the wheel.

Requirement of permanent tcp ip connection doesn’t work well for mobile

I was under the impression PubSub was created for that.

Still, it's an open extensible protocol.

[–] [email protected] 7 points 2 weeks ago

Well duh...

[–] [email protected] 7 points 2 weeks ago (10 children)

There’s a reason nobody uses it anymore.

Yeah, Google and Faceebook EEE'd it.

XMPP is not a good protocol though.

Do elaborate.

[–] [email protected] 5 points 2 weeks ago (2 children)

The content of the feed depends on the content creator, not on RSS.

[–] [email protected] 10 points 2 weeks ago (23 children)

XMPP, RSS, ...

[–] [email protected] 14 points 2 weeks ago

That’s why I’d love to see more developers take another look at Linux.

I'd love to see more developers taking a look at writing portable cross-platform code.

 

cross-posted from: https://programming.dev/post/17508868

When Google, along with a consortium of other companies, announced the open-source operating system we call Android way back in 2007, the world was paying attention. The iPhone had launched the same year, and the entire mobile space was wary of the rush of excitement around the admittedly revolutionary device. AOSP (Android Open Source Project) was born, and within a few years Android swallowed up market share with phones of all shapes and sizes from manufacturers all over the globe. Android eventually found its way into TVs, fridges, washing machines, cars, and the in-flight entertainment system of the Boeing 787 Dreamliner.

 

When Google, along with a consortium of other companies, announced the open-source operating system we call Android way back in 2007, the world was paying attention. The iPhone had launched the same year, and the entire mobile space was wary of the rush of excitement around the admittedly revolutionary device. AOSP (Android Open Source Project) was born, and within a few years Android swallowed up market share with phones of all shapes and sizes from manufacturers all over the globe. Android eventually found its way into TVs, fridges, washing machines, cars, and the in-flight entertainment system of the Boeing 787 Dreamliner.

 
 

Why the second identical disk is more expensive is beyond me (tried with 1TB Samsung 970 EVO Plus NVMe PCIs).

 

You had one job...

view more: next ›