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

help-circle


  • In response to your question, I’d like to share my personal experience regarding remote work. I have been working entirely remotely for years, and given this background, I cannot imagine returning to an office setting, even if it was just for one day a month.

    The primary reason is tied to time and quality of life. If my office were an hour away from my home - and in reality, it’s even further - I would be committing 8 hours a week just for commuting. This effectively means that in terms of hours, I’d still be tied to a five-day work commitment when considering the commute time.

    But beyond the simple tally of hours, there are aspects of daily life and routine to consider. On the days I’d be expected to be in the office, I would have significantly less time to spend with my son. This would majorly impact our daily routine. We wouldn’t get the chance to have lunch together, and the management of daily commitments would become much more complex.

    In conclusion, given my background and personal priorities, I would unquestionably choose to continue working from home five days a week rather than commuting to the office for four days. The flexibility and time saved from commuting hold invaluable worth to me.











  • I just copy&pasted their README in chatgpt asking for a comparison (so there may be allucinations)

    Both PrivateBin and Paaster are “pastebin” tools that allow users to share snippets of text or code online. Both emphasize privacy and security, encrypting data at the local level in the user’s browser before sending it to the server. However, there are several key differences between the two services:

    1. Design and User Interface: While PrivateBin self-identifies as a minimalist pastebin, Paaster seems to put an emphasis on user experience, offering features like file drag & drop and a paste history.

    2. Features: Both offer basic features like password protection and the option to delete data after reading, but PrivateBin also offers features like the ability to have anonymous or nicknamed discussions, Markdown formatting support, code syntax highlighting, and the ability to upload files. On the other hand, Paaster offers a paste history feature, PWA support, and i18n.

    3. Trust: PrivateBin warns users not to blindly trust the server administrator, whereas Paaster advises users to either host their service or use a trusted hosting service.

    4. Implementation and Maintenance: Paaster seems more developer-oriented, with API documentation, a CLI tool, and support for Vercel and Docker. PrivateBin, however, also has a developer and installation guide.

    5. Hosting Options: Paaster seems more geared towards self-hosting, with detailed instructions for use with Docker and options for use with external storage services like Amazon S3 and Google Cloud Storage. PrivateBin does not provide specific hosting details in the provided text.

    6. Security: Both use end-to-end encryption, but they use different encryption algorithms. Paaster uses XChaCha20-Poly1305, while PrivateBin uses 256-bit AES in Galois Counter mode.

    These are just some of the key differences between the two services. Both have their strengths and unique points, and the choice between the two will depend on the specific needs of the user or organization.





  • It’s interesting how different people have different approaches … I migrate from Caddy to Traefik because I found it magical … Whenever I need to add another selfhosted service I just adapt a docker-compose like this one

    version: '3.8'
    
    services:
      homeassistant:
        container_name: homeassistant
        image: ghcr.io/home-assistant/home-assistant:stable
        #image: homeassistant/raspberrypi4-homeassistant:stable
        volumes:
          - ./media/:/media
          - ./config/:/config
          - /etc/localtime:/etc/localtime:ro
        environment:
          - TZ=${TZ}
        restart: unless-stopped
        networks:
          - t2_proxy
          - backend
        labels:
          - traefik.enable=true
          - traefik.docker.network=t2_proxy
          - traefik.http.routers.homeassistant.rule=Host(`home.mydomain.bla.bla`)
          - traefik.http.routers.homeassistant.entrypoints=websecure
          - traefik.http.routers.homeassistant.tls.certresolver=myresolver
          - traefik.http.services.homeassistant.loadbalancer.server.port=8123
    
    networks:
      backend:
        external: true
      t2_proxy:
        external: true
    

    As you can see I just need to change the host and the port in the labels to have a new domain pointing to the right port … I wasn’t able to find an easier way to add a new service to caddy