kitchenkarma

You are unable to tell whether any service uses E2E. It is best to assume we don't have E2E services and adjust own opsec accordingly.

Assume these services are being tapped. If you want ultimate privacy exchange keys with your contacts offline and you PGP over any messaging service.

But but Microsoft is goood! Look GitHub! Linux! Open Souwce! I only use Windows because software I need doesn't work on Linux.

Can someone explain to me what is so special in those photos? These look like snapped on the phone...

It's a bit naive thinking that employees would store their electronics in the lockers. Even if you have spot searches (including cavity search) it still doesn't exclude rogue employee just "forgetting" to store his or hers camera in the locker.

Do they go through phased entry system. For example phase 1 metal detector arch and a 3d scanner like in the airport. Phase 2 strip naked for body and cavity search and then phase 3 - wear company uniform with attached camera and microphones? If not then I can't see how they couldn't take a pendrive in.

This is the future of electronic money. Companies will decide for you what you can or cannot buy.

Shouldn't you also show intermediate page with a privacy warning and a cancel / continue buttons? Otherwise user can click it by mistake and compromise his data.

Move fast break things kind of doesn't work well with planes.

Also too big to fail (fall) doesn't apply here.

Typically CS degree means that you can finish something regardless if it makes sense or not. That skill is in demand in large corporations that require people to follow stupid processes and complete tasks that don't reflect on what are the actual needs. Of course there are good CS degrees, but these are not as common as one thinks. The purpose of universities was to gather knowledge and pass it on where it was not possible otherwise to do so. These days people have open access to all kind of knowledge and universities are not as much important as they were. If company lists CS degree as a job requirement, that for me is a good indication of a place I don't want to work in.

It doesn't matter if it is an IP or another identifier e.g. a hash. Person can be identified by behaviour and this is not anonymised.

You are conflating identification of a person by behaviour analysis with matching an ID. What is the ID is irrelevant here - may as well be a hash. That just proves my point that this project is not compliant.

I don't believe you have understanding what personal data and GDPR is. You are capturing user behaviour and that is very personal regardless if it is "anonymised" or not - and that is without clear need for doing that. That is pretty much against GDPR.

This is very weak reasoning, because you cannot identify an individual by IP either. This project looks like trying to exploit loopholes. The idea behind GDPR is to make sure companies log only data they need. This project looks into logging the data but without expressing why this is even necessary. Therefore I don't think this is compliant with GDPR.

Every generation has problems like this. I remember my friend become addicted to calling premium phone numbers when when he was a teenager. When his parents went to work, he would have stayed home and just keep calling all day instead of going to school. Only when the bill came through post his parents went mad and started to blame everyone but themselves. Eventually they got premium numbers blocked, but his son was spending all the money he could get his hands on on call cards. It was a phase for him, he stopped doing that after few months. When he talked about it years later, he couldn't believe that he did this. He says he wishes his parents gave him more attention and explained to him what it is about and why it makes no sense to do something like this. Fascist love such stories, because they can use them to tell people how they should live and create more regulations.

I don't think Microsoft is doing incredible things. They are baiting the developers and just use the strategy of locking people into their constellation of spying services. Acquiring GitHub they got access to all private repositiories and insight to what other companies are doing. This is despicable.

Windows is just a spyware at this point. Never use it for anything serious. Microsoft having more money that they can ever spend, play the "good person" and seduce developers with shiny things, but the underlining strategy to f*ck everyone hard is in play at all times. Don't be a fool.

What do you do if e.g. Instagram ignores your GDPR requests? I have sent them multiple emails about misuse of my personal data and they only replied with a template that didn't address my emails?

I have all bug fixes turned off, so I don't suffer from that.

People use Macs also to produce music and for this task the most important is single core performance. AMD is not great at this and it seems like the new line of CPUs could only get on par with Intel which isn't enough to convince professionals to move.

I need single core performance and I am maxing out 9900K @ 5.1. If AMD proves to be faster than that, show me where to pay.

I review their portfolio and create a sample task to see how communication goes along and then if I am satisfied I place real order. It is not expensive so I can try few people before commiting to some more work. I find this website extremely helpful. I also like that this website enables artists from impoverished countries make living.

Everything is serial so far. Got it. Here's the thing though: Plugin A processes packet n, Plugin B processes packet n-1, Plugin C processes packet n-2, [...] Plugin G processes packet n-6. Now you have 7 independent threads processing 7 independent data packets. As long as the queues between plugins are suitably small you won't introduce latency.

The process is realtime so you cannot receive events ahead of time. It is actually running how you describe, but you can only process so much during the length of a single buffer. Typically solution is to increase the length of the buffer, but that increases latency or reduce the length of the buffer but that introduces overhead.

Each pedal processes its data concurrently (but not parallel with) with every other pedal.

That's how it works.

The single core performance of these CPUs are absolutely atrocious, but the devs make it work for latency sensitive activities like gaming.

I am talking about realistic simulations. You can definitely run simple models without latency, that's not a problem.

Only if it is evicted from the L3 cache, and the 3950X has 64MB of it. That's over a second(!!) of latency at 16 channel+192kHz+32 bits/sample audio.

That's nothing. Typical chain can consists of dozens of plugins times dozens of channels. There is no problem with such simple case as running 16 channels with simple processing.

Speaking of channels, that seems like a natural opportunity for parallelism.

That works pretty well. If you are able to run you single chain in realtime you can typically run as many of them as you have available cores.

You cannot run the pipeline in parallel. Sure you can have a pipeline and work the buffers on separate cores, but the process is serial. If it was as simple as you think it would have been solved years ago. There are really bright heads working in this multi billion industry and they can't figure that out. Probably because that involves predicting the future.

This is how it is typically being done. This is not a problem. Problem is that being concurrent, end to end this process is serial, so you can't process any element of this pipeline in parallel. You can run only so many of those until you run out of time to fill the buffer. I think it could be helpful for you to watch this video: https://www.youtube.com/watch?v=cN_DpYBzKso

For example, recently released IK Multimedia T Racks Tape Machine collection. One instance of the plugin takes about 15% of one core. In a large project this is a lot and you need to think where to use it or use freezing. Then you have a suite of plugins by Acustica that use a variant of dynamic convolution (volterra kernels) to simulate equalizers, compressors or reverbs. Virtual synthesizers like Diva in pristine mode and enabled multi core can also take a lot of resources. You really need to budget what to use where so that it won't break up - which is a skill in itself, that hopefully in the future won't be relevant as much.

I think this is one of the most misunderstood problem these days. Your idea could work if the process wasn't real-time. In real-time audio production scenario you cannot predict what event is going to happen so you cannot simply just process next buffer, because you won't know in advance what is needed to be processed. At the moment these pipelines are as advanced as they can be and there is simply no way around being able to process X filters in Y amount of time to work in real-time. If you think you have an idea that could work, you could solve one of the biggest problems music producers face that is not yet solved.

I am struggling with i9 9900k running @ 5.1GHz. Plugins that process signal with extreme accuracy require a lot of power. It's like with game - your PC probably wouldn't struggle with running many instances of Solitaire, but multiple instances of GTA V with ultra details could be problematic.

This is a simple fact of life and downvoting isn't going to change it. Plugin cannot start processing before it gets data from previous plugin (sure it can do some tricks like pre-computing coefficients for filters etc). How are you going to get around it? What's happening within a plugin of course can be parallelised, but other than that, the processing is inherently serial. If a computing a filter takes X time and a length of the buffer is Y you can only compute so many filters (Y/X) before it starts stuttering. You can spread that across different cores, but these filters cannot be processed at the same time, because each needs the output of the previous one.

These cannot run at the same time as the output of one feeds into another one. Data travelling from one core to another could mean additional performance loss. Some plugins use multiple cores if whatever they calculate can be parallelised, but still the quicker it can be done the more plugins you can run in your chain.