• 0 Posts
  • 23 Comments
Joined 3 年前
cake
Cake day: 2023年6月19日

help-circle
  • Clean the printing surface with dish soap and tepid water, and adjust your z offset. It appears to be too low from what I can see, but it’s hard to tell from a few pictures. It’s not supposed to be 0, and will depend on your specific printer, extruder, … You should aim to have fully filled squares, with no apparent “scars” on the surface left by the hotend moves. A nice rule of thumb is to be able to barely move a sheet of paper between your plate and the hotend freely without feeling friction (make sure to clean the tip of the hotend before). If after these steps it still produces these results, maybe there is an issue with you bed planarity, but most likely your pla has gone bad (I’ve even seen sealed bags go bad over a few years), try with a freshly dried filament, or a new roll from a reputable source


  • It really depends on your end goal I would say.

    With a “bare” arch install you will probably learn the most (possibly the hard way). Also, arch being a rolling release, be prepared to update your system a lot, and fix problems as you go. That being said, I’ve been using the same arch install for a few years now and have had to fix stuff only once (Nvidia drivers, the usual culprit). If you want to try bleeding edge stuff, that would probably be the best option.

    Nixos : same as you, tried, and left because the community couldn’t settle, and seemed to be fragmenting more and more. Also cool for bleeding edge stuff (thanks to the easy rollback)

    You could also go for a debian based distro (debian or Ubuntu). My servers run on this, simply because they tend to require less maintenance.

    There are also quite a few “docker-centric” distros, that can also be an option.

    Whichever option you choose, if you use a lot of containers, mane sure to use something like docker compose, and keep your compose files safely somewhere (a git repository, a backup’d nas, …). You will keep a lot of nixos’s workflow goodness (everything is a config file), without some of the trouble.



  • Random idea that might work: Try to install ReFind from windows, it should work and allow you to boot from random thing more easily. Then try using it to boot from the SD card. Don’t forget to turn off secure boot. If that doesn’t work, the right idea is indeed to “burn” the media on a partition, however you will also encounter some amount of headache with this option: an installer is not a single partition, but multiple ones. You could try only having the “main” partition on disk, and use refind to boot it too.

    TL;DR: ReFind could help you. Turn off secure boot.





  • Most actual poisoning techniques don’t actually work that well. When I end up with a PDF, I usually strip out the existing text layer, apply a denoiser and a few other preprocessing steps to correct common errors, then a layout / reading order detector, and finally OCR the different blocs. This is against the most common poisoning techniques, and one of the most efficient, called : someone printed a document, forgot about it for 3 years, then scanned it slightly tilted (and dirty, crumpled, …), and the scanner decided to apply its crappy OCR.

    Using screenshots of the PDF also avoid any kind of font face poisoning, and anti copy protection.

    If you really, really need to protect your PDF, please consider accessibility first, then what would work imho is to use the scripting features of pdf to actually render your content on the fly. That would probably mess up most of the “automatic” processes.









  • Graphene user here ! The privacy and security gains are quite huge. Play services are more or less regular apps, with the sandbox offering limited access. Some of the “advanced” security offered by graphene triggered a few times for me, sometime highlighting something sketchy in some apps.

    Also, you can disable the internet permission for apps, which can effectively block a lot of stuff (ex : you install a supposedly offline game, but it stills asks for the permission: denied).

    If your main concern is not depending too much on Google, your options are limited, and very, very flawed depending on how far you whish to go (went far down this rabbit hole, came back). One less “extreme” way, using graphene, is to install play services and everything dependent on a separate user account, and clone app from this account to the one you will use. Since alternate accounts are sandboxed and not running when not logged in, when you use your phone from the main account, you will effectively be almost goggle free.

    Almost, because the main remaining privacy hole is notifications. A lot of things goes through GMS in order to reach your phone without melting your battery


  • It does, don’t remember the details but at one point I let a packet capture tool on my phone run for a few days and checked which apps phoned home. Gboard was one of them. You’d besurprisesd at the amount of network traffic for most apps between 2-4 am.

    Just remove its network permissions, and it works fine (without the phoning home part) AFAIK other spell checkers / autocomplete aren’t quite there yet


  • It is also a huge deal because since (at least in France) the government forced ISPs to log DNS queries, a lot of browsers (and latest android and iOSversion’s) have now migrated to DNS over https or TLS DNS, which means that the only clear text DNS query they can intercept is the one to fetch your secure DNS service address. Now, having a trusted CA installed in browsers means that they can also spoof the identity of this secure name service, and regain a bit of control.

    They invested a lot in surveillance technology (for both good and bad reasons), and https, DNS and encrypted messaging / phone calls means this was all for nothing.

    And yes, by being authorized as a trusted CA, you can effectively spoof pretty much anything by setting a proxy. Some tools even leverage this for app analysis. Look up mitmproxy for example, or squid. A lot of companies already do this to inspect inbound / outbound traffic.