keurrr

I think the reason this was posted is not because of miscellaneous infrastructure, but that it’s an implementation of an interesting algorithm. If you care enough to leave a comment like this, update it yourself.

Well, the spammers sending you junk mail already have all this? Not much to lose here :)

So you are claiming the protocol that Signal has adopted is already backdoored by the government. Extraordinary claims require extraordinary evidence. You need to provide some kind of evidence of this. We are talking 20+ years of open and public research on post-quantum cryptography.

I don't think these incentives make sense at all. Government organizations suspected to be developing quantum computers probably have larger annual budgets than 20 billion. The ability to undermine virtually all cryptographic systems is unquantifiably large.

Once the cat is out of the bag, everyone will rush to post-quantum cryptography and all that value will be lost in a relatively short period. Indeed, we already witnessed this in the 2010s following the Snowden revelations when big tech, in a concerted effort, adopted HTTPS. Now that is the standard.

For example, "The Fiscal Year 2022 budget appropriation included $65.7 billion for the National Intelligence Program, and $24.1 billion for the Military Intelligence Program."

Source: https://irp.fas.org/budget/index.html

The original version was a browser extension. It was very painful to maintain support for all the different types of input fields. Most large social media sites do not use standard text areas.

https://github.com/XCF-Babble/babble

My friend and I implemented this a couple of years ago. It is no longer maintained but the general ideas still apply. Very few social media sites use standard text areas which makes maintaining compatibility a total PITA.

https://github.com/XCF-Babble/babble

There is another group that fully supports an E2EE Facebook https://github.com/DimensionDev/Maskbook

Talking about GUI and data science... So ironic. Look at the author and when this was written.

Thanks. I actually found your repo before seeing this post and sent you an email. Definitely going to port it back to C and merge it in. Thanks so much for this. Hand vectorizing this was on my TODO.

I didn't forget about you! I did a release statically linked with qt5. Let me know if this works for you. Email me at [email protected] if you run into any issues. Use prettyeq-static.

https://github.com/keur/prettyeq/releases/tag/v0.2-alpha

Oh, you need the qt5 shared libs to compile. I am planning to do a release in the next couple weeks that statically links the full thing so no one has to deal with this. Qt makes it very annoying to static link your project (you are stuck compiling Qt yourself), so been putting that off.

If you feel strongly about clipping, I would also accept a patch that allows a user to select an option in the GUI to prevent it.

That makes me so happy to hear! Since this thread is getting less active, feel free to email me at [email protected] if you need anything else.

In the project directory run:

mkdir ./make ./build

cd ./make

qmake CONFIG+=release ..

make -j<cthread_count>

mv ./prettyeq ../build

Cool, yeah. Would love if you contributed that. So off the top of my head we would want to get all output sinks and display them in the GUI and, when the user switches, detect the number of channels they support and live configure to that. We would need to update the null sink, sample_spec struct, and latency. This would live in equalizer/pretty.c so that's a good place to poke around.

Email me at [email protected] if you have any questions. The pulseaudio C API can be a bit... opaque :)

I can’t statically link with it because I would need to release my own software under the GPL.

I can't link with fftw3 since it's GPL. The other libraries that were permissive licensed had confusing APIs and the output binaries were almost as large as my entire project. CPU usage is high but because of one poorly designed part of the GUI (eqhover.cpp)

This is pretty accurate. I wrote it to tweak songs to my speakers when I'm streaming music. I wanted something very fast, no configuration, pleasant graphics.

While probably not suited for production work, the design is based off of existing production tools that I am very familiar with (Channel EQ from Logic Pro X, Parametric Eq 2 from FL Studio).

Hah, pulseeffects was why I wrote this project. It has tons of latency, very sluggish UI, not nice to use.

So my background is I did music production in high school. I actually based the design for PrettyEQ off of the Logic Pro X equalizer and Fruity Parametric EQ 2, and those will happily let you clip. So I like the idea of leaving that to the user's discretion (move the filters slowly, especially in the lows and highs, and know your speakers well). These days, especially in EDM / Hip Hop, slight clipping in bass in somewhat stylistic. So I don't know. Maybe could be an option in the GUI that could be switched on? Would need to think about it more.

I'm not personally into cli stuff, but most of the code in the equalizer/ directory could be used without much change. If anyone started that project and needed assistance I would for sure help out.

Not by hand, but the FFT I wrote for the spectral analyzer is compiled with -ffast-math and gcc vectorizes it (verified with objdump). Same thing with the functions that change the filter parameters.