• 🇨🇦GreenBeard🇨🇦@lemmy.ca
    link
    fedilink
    English
    arrow-up
    42
    ·
    3 hours ago

    I don’t see why it would be a problem. It’s the ultimate expression of the core values of the company. An archive for all time of all of human knowledge needs a stable, knowledgeable pool of well informed archivists that are going to keep that mission on track long term. You would think that they’d WANT the workers to unionize if only to ensure the project can sustain itself.

  • GreenKnight23@lemmy.world
    link
    fedilink
    English
    arrow-up
    16
    ·
    3 hours ago

    all tech workers should unionize. we are a skilled workforce that is currently being targeted by big tech money.

    • 🇨🇦GreenBeard🇨🇦@lemmy.ca
      link
      fedilink
      English
      arrow-up
      5
      ·
      1 hour ago

      There’s limits to that. It’s hard to unionize things where the job description isn’t fairly stable. There’s lots of areas where we could and should unionize, but if you can’t define a professional standard of competence as a worker, it gets very messy to define a membership base. That doesn’t mean there aren’t mature disciplines within the field that absolutely should unionize, but “All” gets a bit… fuzzy.

      • GreenKnight23@lemmy.world
        link
        fedilink
        English
        arrow-up
        5
        ·
        47 minutes ago

        I’m pretty certain all tech work is very well described. silos exist for a reason. if anything, unionizing would force shitty companies to adequately describe what job they are hiring for instead of looking for “rockstars only” or my favorite “family members”.

        those are just flag words for “we’re going to hire you for this, and make you work on anything but that for 18 hours a day until you quit”

  • Artwork@lemmy.world
    link
    fedilink
    English
    arrow-up
    4
    arrow-down
    1
    ·
    2 hours ago

    Thank you for keeping the ineffably marvelous history intact as much as possible!

    Let’s hope it’ll help the following issue of HTTP 429 (i.e., “rate limit”) I do get frequently, too (e.g., ~7/10 times), for unknown reasons, possibly originating from the relatively recent update:


    Source