• 0 Posts
  • 14 Comments
Joined 1 year ago
cake
Cake day: December 14th, 2023

help-circle

  • I’m saying that if your home server (mastodon.social in your example) is outside of Turkey, then there is less reason for them to comply in the first place because they only risk the mastodon.social server being blocked in Turkey. That one is a bad example because they’re one of the largest and they might have a bunch of users in Turkey, so if you want to be extra safe, you’d want to pick a server that isn’t so big so that they are less likely to care about complying with some other county that they might not have any users from.

    If the server you use is based inside the country that has a problem with your content, then you’d be screwed - though all the other servers will still mirror and cache your content for a bit even if you get taken down.

    The resiliency lies in the fact that you can choose to register in a country that is politically friendly towards your posts or if your home country is friendly but you want to avoid being taken down, you can self host a single user instance and refuse any requests from other countries.

    Edit: Now that I think about it, there’s also the fact that as long as the account itself isn’t limited by their home server, the content in question would be accessible through the federated copies, so if the home server isn’t within Turkey / jurisdiction and doesn’t take down the account, the country trying to take down the content would need to send takedown requests or request to geofence the content to each individual server on the entire fediverse - since the home server would be freely federating it to every server with users who follow the content, otherwise they would need to block every fediverse server and every new one every day that more pop up.


  • The difference is that if your home server is outside of Turkey then you can tell them to kick rocks. Bluesky probably complies because they don’t want to be blocked from Turkey. In a truly decentralized system like activitypub, only the server hosting the account / content in question risks being blocked, which means almost nothing the closer you get to a single account instance. Meanwhile every other server not in Turkey would not notice a difference.

    Edit: this was under the assumption that they took it down completely, but it looks like they only geofenced it. Regardless, if they are pressured enough they would be capable of completing hiding an account worldwide, which isn’t possible with activitypub without the legal alignment of every instance’s country since bluesky on the other hand has sole control of the only relay.


  • Gotcha thanks for the info! It looks like I would be fine with ocis or opencloud, but since my main use case and pain points are with document editing which is collabora, it probably wouldn’t change much besides simplifying the docker setup (I had to make a gross pile of nginx config stuff pieced together from many forum help posts to get the nextcloud fpm container to work smoothly). But it already works so unless it breaks there’s little incentive for me to change.


  • What are the apps that you would miss? I basically only use my NC as a Google drive and docs replacement, so all it has to do is store docx files and let me edit them on desktop or mobile without being glitchy and I’ve really wanted to consider OCIS or similar.

    That second requirement for me seems hard because of how complex office suites are, but NC is driving me to my wit’s end with how slow and error prone it is, and how glitchy the NC office UI is (like glitches when selecting text or randomly scrolling you to the beginning).


  • After I check the usual torrent sites, if I can’t find it on Usenet then I try finding random sketchy streaming sites (just by duckduckgoing title + year + stream) because usually you can youtube-dl them with a little fiddling, then my last resort is a DHT indexer like btdig. That’s more risk with viruses but if you’re paying attention it’s not that hard to avoid, but DHT indexes have lots of ancient stuff so be prepared to wait for seeds if you find it.

    Sometimes I also find what I’m looking for on like page 7 of duckduckgo results at archive.org

    Edit: also check soulseek - it’s primarily for music but you can share any file. I share my entire movies collection and get a constant stream of people downloading from me daily so it seems people search for and seem to also share TV and movies so it’s worth a check.



  • Hmm, well it doesn’t seem to be any problem with the docker compose then as best as I can tell. I picked a random ext4 flash drive and replicated your setup with the UID and GID set and it seems to work fine:

    # /etc/fstab
    /dev/sda1       /home/<me>/mount/ext_hdd_01  ext4    defaults 0 2
    
    ~/mount % ls -an
    total 12
    drwxr-xr-x  3 1000 1000 4096 Mar 27 16:22 .
    drwx------ 86 1000 1000 4096 Mar 27 16:31 ..
    drwxrwxrwx  3    0    0 4096 Mar 27 16:26 ext_hdd_01
    
    ~/mount/ext_hdd_01 % ls -an
    total 6521728
    drwxrwxrwx 3    0    0       4096 Mar 27 16:26 .
    drwxr-xr-x 3 1000 1000       4096 Mar 27 16:22 ..
    -rw-r--r-- 1 1000 1000 6678214224 May  5  2024 PXL_20240504_233345242.mp4
    drwxrwxrwx 2    0    0      16384 May  5  2024 lost+found
    -rwxr--r-- 1 1000 1000          5 Mar 27 16:27 test.txt
    
    # ~/samba/docker-compose.yml
    services:
      samba:
        image: dockurr/samba
        container_name: samba
        environment:
          NAME: "Data"
          USER: "user"
          PASS: "pass"
          UID: "1000"
          GID: "1000"
        ports:
          - 445:445
        volumes:
          - /home/<me>/mount:/storage
        restart: always
    

    I was able to play the PXL.mp4 video from my desktop and write back the test.txt file

    Have you checked the logs with docker logs -f samba to see if there’s anything there?

    Also you could try to access the HD from within the container, using docker exec -it samba bash and then cd into /storage and see what happens.


  • I would suggest adding “UID” and “GID” environment variables to the container, and set them to the numeric values for user and group numbers that show in place of your name when you use “ls -an” inside of the “mount” folder (they will probably be the same number).

    For example, if inside your mount folder you see:

    ls -an
    total 12
    drwx------ 2 1001 1001 4096 Mar 27 13:54 .
    drwxr-xr-x 3 1000 1000 4096 Mar 27 13:51 ..
    -rwx------ 1 1001 1001    0 Mar 27 13:54 hello.txt
    -rwx------ 1 1001 1001    4 Mar 27 13:54 test.txt
    

    Then set UID: 1001 and GID: 1001

    I get the same error as you when I copy your docker-compose and try to access a folder owned by my user. When I add the UID and GID of my user id to the docker-compose (1001 for me), the error goes away.


  • What did you set UID and GID to and what is the output of “ls -an” when run inside of the shared directory? You can remove the file names for privacy. I just tested the docker container and it seems to work between my Linux laptop and my windows 11 desktop using this docker compose:

    services:
      samba:
        image: dockurr/samba
        container_name: samba
        environment:
          NAME: "Data"
          USER: "samba"
          PASS: "secret"
          UID: "1000"
          GID: "1000"
        ports:
          - 445:445
        volumes:
          - ./samba:/storage
        restart: always
    

    The files in my shared folder are owned by UID/GID 1000/1000 which is why I put those as my UID/GID, and when I logged in from Windows I entered samba and secret as the password and I was able to access and modify the files in the shared folder.




  • I use it to auto update nginx and haproxy containers, since they adhere very well to semver there is very little risk of breakage if you use the correct tag and not just :latest. I haven’t had a single issue in many years, and it’s nice to know that I’ll get critical security updates within 24h of images being pushed.