[ 3 / biz / cgl / ck / diy / fa / ic / jp / lit / sci / vr / vt ] [ index / top / reports ] [ become a patron ] [ status ]
2023-11: Warosu is now out of extended maintenance.

/biz/ - Business & Finance

Search:


View post   

>> No.22395311 [View]
File: 136 KB, 559x1040, ad-requests2.png [View same] [iqdb] [saucenao] [google]
22395311

>>22395091
They would need to change the protocol imo. You see this screenshot? All you need to get an ad is to make a simple signed request to their server and the server responds to you with an OK. They need to change the whole protocol because it's way too easy to fraud

>>22395111
Open the Preferences file in notepad

>>22395143
>Doesnt each browser have a unique id or anything to know who made which call to their server?
Yes it does. If you don't use the browser method I explained above then you need to sign it yourself and send the request to the server. It's not too hard to do.
>If the same person makes too many call per hour shouldn't that get flagged?
No, as stated here, and stated by the team themselves, they remove the IP address header, so they don't even know who watches the ad. They just know someone sent a request to their server that they watched and add and it's accepted. Read this : https://github.com/brave/brave-browser/wiki/Security-and-privacy-model-for-ad-confirmations#upon-viewing-an-ad
>These confirmation token redemption events should not be linkable to the user to whom they were issued provided:
>There is a sufficient anonymity set formed by users who are creating confirmation tokens.
>The time between token issuance and confirmation is not predictable.
>The confirmation metadata does not include information unique to the user (that is not otherwise unique to this event.)
>The user is not made re-identifiable through other side channels such as IP address information. We ensure this by configuring our CDN to neither log nor forward client address information.

Navigation
View posts[+24][+48][+96]