• 3 Posts
  • 22 Comments
Joined 11 months ago
cake
Cake day: March 1st, 2024

help-circle










  • Agreed.

    Looked at the project LICENSE and saw no character licensing waiver from Disney. This not a case of fair use, The package is both branded kenobi and uses copyrighted imagery. Removing all doubt. The image most likely is not in the public domain. But if that is, this should be clearly documented and isn’t.

    My first impression is, what a noob move.

    Taking a step back, lets keep in mind, software is Intellectual Property. All our licenses are meaningless, if coders disregard copyright law.

    There is nothing wrong with the software as long as it’s fork’ed away. The package name, the main script file name, and entrypoint name should be renamed. The imagery should be deleted.

    Send a letter to Disney saying, stay away from our kids then kick them out of the Western world. Then take a shower. Maybe burn our clothes just be sure.

    Disney is guilty of mixing good and evil and calling it good. They propagandize your women projecting imagery that men should be rejected. They project themselves as priests seeking to supplant culture and society with their own set of morality and ethics.

    We are a separate group, we are priests of technology. And don’t want to be stuck in the dark ages forever cuz a group of pervs discovered they can get little girls to pose for the camera and then feed the girls princess fantasies.

    BUT that doesn’t excuse our actions. If we disregard copyright law.



  • Just got back from talking with our team. The senior coder in charge of emojis in usernames is currently upgrading the windmills in the uk, having been able to enhance efficiency by 0.001%. Wow! Thats 14 Mega tons of CO2 removed from the atmosphere every year!

    Will take the weekend to get commercial Fusion energy rolled out and right after that will address your issue. Which i’m sure many other users will be thankful you brought to our attention. And luckily had the right man for the job on staff. He’s amazing, capable, enthusiastic, and eager to help.






  • I use stub files and mypy, but have concerns about behavior.

    Thought the point is to move the static type checking stuff into a separate file. This makes the code much easier to read.

    1. When a particular stub file becomes out of date, contents don’t reflect what’s going on in the code, there is no warning.

    2. inner functions are ignored.

    3. a functions contents are ignored.

    Reluctant to use a library running node (gh actions aside) or Rust. My opinion is speed and correctness are insufficient arguments to introduce another tech stack. If something breaks, suddenly the onus is on me to understand why. That’s complicated if the additional tech stack is in a coding language i’m unfamiliar with.

    This takes out: ruff, uv, and pyright. And whatever else comes out.

    Have seven published python packages.

    Trying to be open minded. Please layout other arguments why should be open to utilizing other tech stacks.