• 0 Posts
  • 24 Comments
Joined 1 year ago
cake
Cake day: June 19th, 2023

help-circle
  • It could be a case of too much cooling, while simultaneously being too much heat.

    If you’re blowing so much air that the filament instantly solidifies when it leaves the nozzle, it’s not going to bond with anything else. It’s also interesting that the first layers are fine (when the part cooling fan is typically not running), but problems start when the part cooling fan turns on.

    Have you tried without part cooling at all? Another thing is that your part cooling might be cooling down the tip of the nozzle, causing tiny partial clogs, which are cleared every so often by friction.


  • Did you notice a difference in print speed when you slowed down? As this is a small print, it could already be as slow as it will be due to minimum layer times.

    It could also be that the nozzle spends too much close to the print. What happens if you print 2 or 3 of them?

    This is typically more of an issue with PC where you don’t have a part cooling fan running, but maybe it’s the case here too?





  • As far as I know the 1DXIII is still being produced, nearly 4 and a half years after its launch.

    Single lens reflexes have one massive advantage: the sensor is not being used while you’re composing or idle, which means the sensor doesn’t heat up as much. Hot sensors generate noise, which you then have to compensate for (by doing an equal exposure with the shutter closed to remove the hot pixels).

    But mirrorless is faster, cheaper to produce, smaller. It’s inevitable that DSLRs will soon be a relic of the past. But they won’t be for a while: 30% of the enthusiast market in 2022 was still DSLRs.




  • I think you’re misguided about the APIs. Gmail supports IMAP and SMTP. Proton supports those too if you run an encryption bridge on your computer. Fastmail supports IMAP/JMAP/SMTP (they invented JMAP to try and innovate).

    Email providers most likely must provide SMTP and IMAP due to compatibility requirements with Apple Mail and other clients.


  • Email is ridiculously complex—the technology is dead simple, but the number of exceptions and (undocumented) rules you need to abide by or risk getting banned by half the internet without being told is nothing to sneeze at.

    I should know: I have built multiple support platforms that worked through email (amongst other channels).

    You mention wanting to start at the SMTP level, and then building a Qt interface. So you’re going to write an SMTP client, an IMAP/POP3/JMAP client, a storage engine, a user interface, and a better search system, all on your own? You’re describing a gargantuan task.

    No offense, but each one of those could be a project on its own. You probably think they’re all simple tasks (they’re not), and that you can follow a few RFCs to get things going (you can’t), and that it’ll be easy to debug (it won’t). Finally, I think you’re underestimating how large people’s email maps get.

    Why not write a plugin for Thunderbird that improves the search?





  • You cannot prevent your employees from discussing wages. It is literally illegal to do so, and you cannot reprimand people for doing so.

    Under the National Labor Relations Act (NLRA or the Act), employees have the right to communicate with their coworkers about their wages, as well as with labor organizations, worker centers, the media, and the public. Wages are a vital term and condition of employment, and discussions of wages are often preliminary to organizing or other actions for mutual aid or protection.

    If you are an employee covered by the Act, you may discuss wages in face-to-face conversations, over the phone, and in written messages. Policies that specifically prohibit the discussion of wages are unlawful as are policies that chill employees from discussing their wages.

    You may have discussions about wages when not at work, when you are on break, and even during work if employees are permitted to have other non-work conversations. You have these rights whether or not you are represented by a union.

    https://www.nlrb.gov/about-nlrb/rights-we-protect/your-rights/your-rights-to-discuss-wages







  • “Sound” when it relates to water comes from Germanic- and Proto Indo European languages. In Denmark, the Øresund (English translation “The Sound”) separates Denmark and Sweden. In Dutch, “zond” used to a be term for a sea-based water inlet into the lands. Many nordic languages still have “sund” in their vocabulary (Danish, Swedish, Icelandic, maybe Norwegian too?).

    In Proto Indo European, the “swem” prefix is related to things of the water, or swimming. “Zwemmen” in Dutch still today means “to swim”.

    Wiktionary gives the follow definition:

    long narrow inlet, or a strait between the mainland and an island; also, a strait connecting two seas, or connecting a sea or lake with the ocean.

    It also quotes a text from 1605:

    The Sound of Denmarke, where ships pay toll.