tekato

joined 4 months ago
[–] tekato 4 points 2 months ago

But I want to know what is AMD working on, specially if it has to do with the RT / HDR / color management areas.

HDR/Color Management is not really AMD’s job. That’s between the Wayland and Mesa guys (I guess you could say AMD belongs in the “Mesa guys” umbrella).

Also, I’m pretty sure AMD already supports ray tracing through Mesa, and is enabled by default since version 23.2 on the radv driver:

radv: Enable ray tracing pipelines by default

[–] tekato 7 points 2 months ago (3 children)

You can literally monitor where the data is being transmitted. There is no need to trust anyone. If it was sending data to anything that isn’t your relay server, you’d be able to easily prove it.

[–] tekato 12 points 2 months ago (1 children)

I guess the fact that the last release was in April. Some people refuse to compile their apps even though it’s better.

[–] tekato 3 points 2 months ago (13 children)

You can self-host your own relay, what is there to worry about?

[–] tekato 7 points 2 months ago

They don’t support new technologies (Wayland), why would they drop support for old ones?

[–] tekato 3 points 2 months ago

Yes, looks like the actual advantage (or disadvantage , depending on who you are) is ensuring that you don’t send a false location to a third party.

[–] tekato 5 points 2 months ago

Where does CUDA come into play for screen tearing?

[–] tekato 1 points 2 months ago

You then execute that SNARK on your local device with your current exact GPS coordinates

No, that’s what I’m suggesting. The proposed method in the paper makes no use of GPS, instead it’s some peer-to-peer network.

[–] tekato 1 points 2 months ago (1 children)

You mean the hexagon? What prevents you from mapping your GPS output to a hexagon?

[–] tekato 5 points 2 months ago (2 children)

It is better, just not on NVIDIA GPUs.

[–] tekato 6 points 2 months ago (8 children)

How is this better than just mapping GPS data to a hexagon and sending that to the third-party?

view more: ‹ prev next ›