This is the main reason we did not support IPv6 at Winston.
Readit Newswinstonprivacy commented on One bad apple can spoil your IPv6 privacy (2022) arxiv.org/abs/2203.08946... · Posted by u/whereistimbo
Already posted.
winstonprivacy commented on Adobe is buying videos for $3 per minute to build AI model bloomberg.com/news/articl... · Posted by u/thm
Is there going to be a new term called "Data Laundering"?
You create the synthetic data, move it through 10s of entities and then buy it back cheaply from an entity.
Data Laundering is an old term... I was using in more than a decade ago in talks about how unethically gathered private data was being sold to Israeli companies, who then licensed it back to US corporations. It was (probably still is) a way to side step privacy laws.
That's true. We restrict access to Snapchat, TikTok, Instagram, FB, they can use WhatsApp, YT, iMessage, Phone and Pinterest. I'm fucking annoyed by other parents that don't set boundaries that way. I have so much discussions about other platforms. Pushing them to physically meet is hard too.
We grew up at a time where SMS was a thing when I became 16. I know that keeping up is cool, but social media is a disease. The amount of dumb and uneducated people that couldn't even listen to expert advice during a fucking pandemic is driving me up the wall.
I'm annoyed mainly because people around me make bad decisions that have an influence on my own life.
> The amount of dumb and uneducated people that couldn't even listen to expert advice during a fucking pandemic is driving me up the wall.
The amount of dumb, educated people that blindly accepted everything that was fed to them during the fucking pandemic is driving me up the wall.
"Just two weeks to flatten the curve!"
winstonprivacy commented on C++ coroutines do not spark joy (2021) probablydance.com/2021/10... · Posted by u/signa11
Regarding new/delete elision: https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2018/p09...
You can also specify custom new/delete operations for your co-routine for control. I am not sure if you are allowed to delete them to guarantee elision either happens or the program fails to compile.
Much like lambdas and ranged-based for loops, co-routines are pretty much defined as a code transformation into lower-level C++ rather than being black magic.
Regarding the "inline" keyword being used to move a function's body into the caller: that is a compiler hint and not mandatory. The actual purpose of the "inline" function is to allow the implementation of a function to appear in multiple translation units without that causing linking issues (provided the implementation is identical).
In terms of "I’m curious if anyone actually finds something useful to do with these.": the modern C++ Windows Runtime API is built upon async operations and co-routines.
Yes, they are incredibly useful and performant in real time state machines. One of the best features of the language in certain situations.
Excellent article and the methods described are accurate. I was speaking extensively about this from 2017-2020 and the usual reaction when I talked about this was disbelief. I was not surprised when In-Q-Tel came calling. I pitched them a military grade privacy protocol but my suspicion was that they were more interested in spying on our users (a non-starter).
winstonprivacy commented on How QUIC is displacing TCP for speed engineeringatscale.substa... · Posted by u/animesh371g
QUIC: let's build an application-specific protocol on top of UDP and call it a day.
So really, is it faster? Does it reduce the amount of load on network devices? Does it allow a server to serve more connections more quickly than the equivalent HTTP/2.0 stack? Does it make my web app faster?
I mean, for 99% of Wordpress sites the problem is Wordpress, not the transport protocol. For a lot of the web the problem is client-side rendering issues.
QUIC may solve a problem, but is it a problem in real life or a thought experiment that got folded into a standard?
I don't have benchmarks but I built a protocol that QUIC later turned out to be eerily similar to. It was a direct replacement for TCP and we used it to provide an additional layer of encryption for all traffic on a given network between two points.
Latency was exceptionally improved. Web pages felt like the loaded faster and at the very least, users could not tell that they were using an encrypted connection.
The protocol essentially worked using a fast-ACK protocol that would preemptively request retransmits (and was occasionally wrong). This enabled it to use connectionless UDP protocol as the underlying transport mechanism. There is, of course, a cost for reduced latency. That cost was slightly higher bandwidth utilization on the network. This was suboptimal for long-lived streams (media and other downloads) so we tried to fault over to ordinary TCP in these instances.
winstonprivacy commented on AdGuard Home: Network-wide ad- and tracker-blocking DNS server github.com/AdguardTeam/Ad... · Posted by u/kls0e
It is not a popular class of software to the masses, it is a popular class of software to a niche audience. I don't share as pessimistic attitude as OP though. I'm pretty sure the audience is in the tens of thousands!
What's funny is that I was once extremely optimistic about the potential for such a device, to the extent of having sold and delivered a few million in product.
Hard experience taught us that churn is just crazy high, no matter how compatible it easy to use you make it. Getting tens of thousands of stars is not the hard part because it's such an easy concept to like. But I would be surprised there are more than let's say ten thousand piholes in active use.
winstonprivacy commented on AdGuard Home: Network-wide ad- and tracker-blocking DNS server github.com/AdguardTeam/Ad... · Posted by u/kls0e
Sadly for the AdGuard team, there isn't much of an audience for this. It's one of those things everyone says they want but few people will actually install one, much less maintain one over time. Add to that the wife-forced uninstalls and the total long-term audience for this is (no kidding) in the thousands.