• 0 Posts
  • 4 Comments
Joined 14 days ago
Cake day: January 2nd, 2026
  • clean_anion@programming.devto3DPrinting@lemmy.world•Is this nozzle too low or bed temperature issue?English
    3·
    10 days ago

    It’s most likely an error with the nozzle height. The PEI plate not heating up enough shouldn’t cause the adhesion in the photo above (and this is not a first layer problem, as the error is not at a uniform height). Additionally, a few lines are very faintly visible on the plate where they shouldn’t be, indicating nozzle height. Make sure that it is easy to move a piece of paper between the nozzle and the PEI plate when adjusting the height, feeling only a very small amount of pressure as you do so.

  • clean_anion@programming.devtoPrivacy@lemmy.ml•Is there something like an addon that generates (or picks from a list of) random cookies so you don't fall into captcha hell if you have to use Google?
    5·
    13 days ago

    TL;DR: not possible with random cookies, too much work for too little gain with already-verified cookies

    There is no such add-on because random cookies will not work. Whenever someone has been authenticated, Google decides the cookie the browser should send out with any subsequent requests. Google can either choose to assign and store a session id on the browser and store data on servers or choose to store the client browser fingerprint and other data in a single cookie and sign this data.

    Additionally, even with a verified session, if you change your browser fingerprint, it may trigger a CAPTCHA, despite using a verified cookie. In the case of a session token, this will occur because of the server storing the fingerprint associated with the previous request. On the other hand, if using a stateless method, the fingerprint will not match the signed data stored inside the cookie.

    However, this could work with authenticated cookies wherein users contribute their cookies to a database and the database further distributes these cookies based on Proof of Work. This approach, too, has numerous flaws. For instance, this would require trusting the database, this is a very over engineered solution, Google doesn’t mind asking verified users to verify again making this pointless, it would be more efficient to simply hire a team of people or use automated systems to solve CAPTCHAS, this approach also leaks a lot of data depending on your threat model, etc.