• 0 Posts
  • 51 Comments
Joined 2 years ago
cake
Cake day: July 6th, 2023

help-circle

  • I’ve been using copilot. Potential is there but getting a result is more art than science. I’ve found it helpful to document desired workflows in readmes and ask for unit tests then run unit tests until it works out.

    • use a premium model like sonnet and put it in agent mode
    • Ask it to review the project
    • ask it to review the ticket/requirements
    • ask it to research existing solutions and write a design document that meets the requirements with high certainty
    • Let it write the document and make sure it stays on task
    • review the output and send build errors back, roll forward or undo the code and re-submit
    • identify what works and reduce scope

  • I offered 3 potential solutions that work across ever model (unlisted) and you guys are downvoting?

    • USB - apple 30 pin: note that the pin number might change depending on release year. Someone smarter than me will mention why firmware might not work out.
    • USB to aux: this will give you a headphone jack and is the most reliable
    • FM transmitter: if you lack a headphone jack you can also get an FM transmitter. It makes your device a mini radio station. These are pretty unreliable or staticy, but sometimes you need an option. I would recommend a new player first.



  • On a very specific note, I don’t run my Plex server in a container. I have a docker compose setup with 20+ apps, but Plex is on the bare metal OS because it’s kinda finicky and doesn’t like nas. You also need to setup the Plex API to claim the server as the container name changes. This is my stock Plex config if it helps

    plex:
        image: lscr.io/linuxserver/plex:latest
        container_name: plex
        network_mode: host
        environment:
          - PUID=1000
          - PGID=1000
          - TZ=Etc/GMT
          - VERSION=docker
          - PLEX_CLAIM= #optional
        volumes:
          - /home/null/docker/plex/:/config
          - /x:/x
          - /y:/y
          - /z:/z
        restart: unless-stopped
    

  • It’s built on the shipping container parallel. In order to transport objects you obfuscate anything not required for shipping a container.

    • What’s inside the container doesn’t matter. The container has everything it needs to run because the ship/host is responsible for the overhead.
    • containers move. Containers are setup to run by themselves, so you can move it from one ship to another. This means you can use your container doesn’t care if it’s in the cloud or a shipping vessel
    • As soon as you open a container your stuff is there. It’s very easy to onboard.
    • Most importantly though, your shipping container isn’t a full boat by itself. It lives in a sandbox and only borrows the resources it needs like the hosts CPU or the boats ability to float. This makes it easier to manage and stack because it’s more flexible

  • It all started with PAL: https://en.wikipedia.org/wiki/PAL the short version is that old cameras were tuned to work with the electromagnetic frequency, your camera either worked in Europe or in the US. This effected the frame rate of the end video (4%) and meant that tvs, video players and consoles ran at a different frame rate which lead to 2 standards NTSC and SECAM.

    As trade expanded publishers created trade routes and business partnerships that created a patterns of distribution. Later when we resolved those 2 standards with modern technology, we are still were using those methods to get the physical copies to the stores and those same stores are still handling digital distribution, using the same laws and regulations. It might seem simple to click download, but that’s built on a monolith of history and automation to deliver a good user experience.

    To actually get rid of it, I’m not a lawyer but I imagine we have internal trade treaties to visit? I don’t think it’s legal to sell PAL versions outside of their region unless you are also doing business there. I know Japanese pokemon games were hard to buy as a kid. Disclaimer: I know tech stuff.




  • Reposting here: I worked phone support for a few companies for a few years, this is how to Karen: Try to bait the ai, companies are liable for promises made by their hallucinating chatbots. Chat support first, who wants to talk to people? If you do need to call, enter identitng information once, then repeatedly press 0 to get human support. Ask tier 1 support, if they say no then flex that Karen superpower “I’ll need to speak your manager”; those people are individuals just collecting a paycheck. If the floor manager (many have a 3x request policy) can’t see the situation from the human perspective and resolve/waive, they will only care if someone above them gets upset, the ways to do that are threaten legal action. No sovciet bs, but it helps to use contract terminology like “agreed upon terms”, “failure to meet industry standards” and “breach of contract”. If they don’t get jostled immediately, your next escalation is tag the intern on social media with a negative sentiment; or Google the company name followed by email for the office of the president. This is the pr address, CEO assistant or community director which again have the power to step in and resolve. You can also think outside the box and leave negative play store reviews (different intern).

    Each conversation should be less then 2 minutes + wait time and if that can’t resolve it, you need to close your account (which might take you to retention!) or potentially move. You can justify 1 more call during a different shift. There is no need to get mad, state that are you upset and are looking for resolutions. Use an I feel statement, and be sure to ask to leave notes on the account regarding your conversation. They have a UI with comment fields in the ticket that are displayed while you are on the phone and it helps sell the situation with comment history.



  • thirteene@lemmy.worldtoLemmy Shitpost@lemmy.worldsad
    link
    fedilink
    arrow-up
    25
    ·
    11 months ago

    The joke is that a person named Hans Duchtelstein was the previous timelines “Hitler” and after being successful Hitler just stepped in because fate is inevitable.

    Reverse: we time travel and kill Hitler, come to the present and Hans Duchtelstein takes Hitlers place but does the exact same thing.








  • Mostly customer provided certs, high end clients make all kinds of stupid requests like the aforementioned man-in-the-middle chain sniffers, clients that refuse DNS validation, clients that require alternate domains to be updated regularly. Management is fine for mywebsite.com, but how are you solving an EV on the spoofed root prod domain, with an sso cert chain for lower environments on internal traffic that is originally provided by a client? And do you want the cs reps emailing each other your root cert and (mistakingly) the key? I’ve been given since SCARY keys by clueless support engineers. I don’t want to do this every 3 months.