mgclient VS abaddon

For the compiler toolchain, I decided to use Emscripten since it bundles nicely with JS (if you recall from the previous article, the system libraries are exported in JS, which provides a nice native integration). Moreover, Emscripten integrates nicely with cmake, making it easy to extend the current build scripts of mgclient. Therefore, after a set of small changes to the codebase, I managed to add WASM as a compilation target of mgclient. The best part is that the integration is so smooth that you can build it in one go with cmake .. -DWASM=ON && make -j4, and if you are curious about how this all works internally, check out our cmake files GitHub repository.

There is a broad number of drivers in many different programming languages available for both solutions. While Memgraph only maintains a few in-house drivers that it develops and supports (C, C++, Python, Rust), most Neo4j drivers can also be used with Memgraph. This is due to the fact that both solutions use the Bolt protocol, labeled property graph model and Cypher query language.

FROM python:3.8 # Install CMake RUN apt-get update && \ apt-get --yes install cmake # Install mgclient RUN apt-get install -y git cmake make gcc g++ libssl-dev && \ git clone https://github.com/memgraph/mgclient.git /mgclient && \ cd mgclient && \ git checkout dd5dcaaed5d7c8b275fbfd5d2ecbfc5006fa5826 && \ mkdir build && \ cd build && \ cmake .. && \ make && \ make install # Install pymgclient RUN git clone https://github.com/memgraph/pymgclient /pymgclient && \ cd pymgclient && \ python3 setup.py build && \ python3 setup.py install # Install packages COPY requirements.txt ./ RUN pip3 install -r requirements.txt COPY card_fraud.py /app/card_fraud.py WORKDIR /app ENV FLASK_ENV=development ENV LC_ALL=C.UTF-8 ENV LANG=C.UTF-8 ENTRYPOINT ["python3", "card_fraud.py"]

Discord https://github.com/uowuo/abaddon

Here you go.

Sadly no, but its more privacy respecting than the regular client for sure. FOSS options include: https://github.com/diamondburned/gtkcord4 https://github.com/uowuo/abaddon https://github.com/terminal-discord/weechat-discord (weechat plugin to use Discord within weechat) https://github.com/evelyneee/accord (seems to be for M1 macs) https://github.com/ArmCord/ArmCord (seems to support AMD64, not just Arm64) https://github.com/khlam/discord-sandboxed (sandboxing for standard discord client) There are others I'm sure. One easier option is to run the Discord code in a newer version of Electron. This still isn't open source, but it provides better security and performance. Arch users can use the AUR package discord_arch_electron, other users can just follow the commands in the PKGBUILD for said package and figure it out. Hope that helps. Keep in mind even if your client is open source, Discord's servers aren't, and while there will be some mitigation of data collected, it'll still be quite a bit.