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

help-circle

  • I’m calling bullshit on any user count they release. The site was filled with bots even when I still used it. People kept complaining about “karma farmers” as if there were users who repost popular content. It has always been largely Reddit’s own bots too keep new users entertained and recycle popular content so that it reaches as many users as possible. They turned this up to 11 before going public.

    Now that they no longer provide an API, they are free to make up any fake metric they want to try to pump up their worthless stock.


  • Not sure if this works for you, but when I’m in a socially confusing situation, I involve people. If you think someone is talking bad about you, ask them about it. Ask for guidance. If you ask someone for help, they will often remember it positively. It takes courage to ask for help, as it’s a sign of weakness, and people usually respect that you trust them with your request.

    Ideally it will turn out to be a misunderstanding, or you get some constructive criticism, or you get a confirmation that people are actually talking bad about you. At least you will have more clarity. If there wasn’t really anything bad going on, now you’re still in a conversation. Even if you say thanks and end the conversation, you’ve broken the ice with that person.

    Friends are very much necessary. You need people in your environment, other than your family, to exchange ideas with and talk about things that are on your mind. Don’t try to substitute friends with online relationships. It will never be equal. Finding local people with similar interests online is fine if that helps you to reach out. You can’t force making friends, it’s a waste of time. Start with making one friend. Quality over quantity


  • I’d be more worried about media than the ability to pirate it.

    Music has adapted to generate plays. Platforms are already being polluted with genAI music.

    TV was replaced by streaming services. Series come and go and are very specifically tailored to get people to subscribe. Exclusives are the standard. Single season productions are not uncommon. People are also already investigating ways to pollute this pool with genAI as well.

    Movies are a stream of Marvel and Disney garbage that was already more CGI than acting. Now genAI and upscaled classics are on the menu.

    Piracy will not go away. People used to record movies with camcorders in the cinema, now they pull raw files from CDN nodes. There is always the scene. The platforms that try to profit from the scene come and go.








  • If you want to get into the scene, hopefully, you made this post from a clean account that can never trace back to you. Otherwise this shit will break your back at some point.

    The people you want to be in contact with, don’t want to be in contact with you. People who want to be in contact with you, are cops or stupid people.

    If you need to ask, then you shouldn’t know. People who offer help are likely to deceive you.

    There is still value in watching https://en.wikipedia.org/wiki/The_Scene_(miniseries)

    That being said, that material was highly likely already captured by existing professionals and nobody will care. Don’t risk anything for a bit of thrill. Actually releasing pirated material and actively breaking copyright law is no joke. You might think it’s good fun, but there are people who try to fuck you up as their full-time job. Pirates are often mentally ill or are motivated financially. There is no Robin Hood you could help for a greater good.





  • gencha@lemm.eetoSelfhosted@lemmy.worldHTTPS on homelab (just locally)
    link
    fedilink
    English
    arrow-up
    1
    arrow-down
    1
    ·
    2 months ago

    I roll out Step CA to my workstation with an Ansible role. All other clients on the lab trust this CA and are allowed to request certificates for themselves through ACME, like LetsEncrypt.

    All my services on all clients on the network are exposed through traefik, which also handles the ACME process.

    When it comes to Jellyfin, this is entirely counter-productive. Your media server needs to be accessible to be useful. Jellyfin should be run with host networking to enable DLNA, which will never pass through TLS. Additionally, not all clients support custom CAs. Chromecast or the OS on a TV are prime candidates to break once you move your Jellyfin entirely behind a proxy with custom CA certificates. You can waste a lot of time on this and achieve very little. If you only use the web UI for Jellyfin, then you might not care, but I prefer to keep this service out of the fancy HTTPS setup.





  • Sharing the network space with another container is the way to go IMHO. I use podman and just run the main application in one container, and then another VPN-enabling container in the same pod, which is essentially what you’re achieving with with the network_mode: container:foo directive.

    Ideally, exposing ports on the host node is not part of your design, so don’t have any --port directives at all. Your host should allow routing to the hosted containers and, thus, their exposed ports. If you run your workloads in a dedicated network, like 10.0.1.0/24, then those addresses assigned to your containers need to be addressable. Then you just reach all of their exposed ports directly. Ultimately, you then want to control port exposure through services like firewalld, but that can usually be delayed. Just remember that port forwarding is not a security mechanism, it’s a convenience mechanism.

    If you want DLNA, forget about running that workload in a “proper” container. For DLNA, you need the ability to open random UDP ports for communication with consuming devices on the LAN. This will always require host networking.

    Your DLNA-enabled workloads, like Plex, or Jellyfin, need a host networking container. Your services that require internet privacy, like qBittorrent, need their own, dedicated pod, on a dedicated network, with another container that controls their networking plane to redirect communication to the VPN. Ideally, all your manual configuration then ends up with a directive in the Wireguard config like:

    PostUp = ip route add 192.168.1.0/24 via 192.168.19.1 dev eth0
    

    Wireguard will likely, by default, route all traffic through the wg0 device. You just then tell it that the LAN CIDR is reachable through eth0 directly. This enables your communication path to the VPN-secured container after the VPN is up.