Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)B
Posts
0
Comments
255
Joined
3 yr. ago

  • Doesn't this need an AI disclosure in the title and post per the rules of this community?

  • I emailed them at support@greenfi.com with basically the message "I can't login I get this message, what can I do to resolve this", went back and forth a bunch, did all the annoying troubleshooting reinstalling the app, clearing app data, etc, sent screenshots of the message, assured I wasn't using a VPN, sent all the details of my phone and rom version, had to poke them when they didn't respond, got a random message of them saying "we see you were able to gain access" and I had to be like wtf no I didn't?, told them it worked if I temporarily enabled play protect and said I would switch banks if I couldnt access check deposit which is mobile only, they replied with some justification why play protect is tripping it up, so I told them that I had no issues having play protect off with other financial apps like fidelity and chase bank, and finally got a response from a "supervisor" saying "i refreshed your settings" settings" and it started working.

    Not sure if they just whitelisted my account or what, but maybe if enough people complain they will get tired of whitelisting everyone and change course.

  • I switched away from Ally bank for similar reasons, on my lineage'd pixel 5 with gapps, their app would always fail the login the first time then succeed the second time for no reason.

    Then the bank I switched to, greenfi (coastal community bank) completely blocked login unless I had play protect (in Google play) enabled, which allows Google to uninstall any app from your phone without asking if they decide it's a "security risk" or whatever - I can totally imaging them deciding that ReVanced / morphie / patched apps that block their ads to be a "security issue". Luckily greenfi was more understanding and they did something that allowed me to log in again.

  • Vrchat is heavily CPU limited if you have a decent graphics card - me and my friends all have various x3d cpus and it's still not enough so this is welcome news. I have a 9800x3d and a friend has the 9850x3d and in tough situations we get around 50-70fps which is pretty middling for VR.

  • I completed a 300 mile move yesterday, and my homelab was one of the least stressful parts thanks to my pre-emptive downsizing from a half rack to just a Synology + Intel nuc. I also pre-emptively switched from forwarded ports to a reverse proxy because I didn't want to be thinking about what isp I would end up with. Even further, I linked the nas and nuc directly with Ethernet so that I wouldn't need to rely on static IPs or router-assisted local hostnames, mdns, avahi, whatever because I wanted to be able to transplant my lab onto any network just in case of emergency - thankfully I haven't had to test that out but it's nice knowing my lab should work on any network where both boxes can reach the internet / my reverse proxy. I was thinking worst case if we ended up in some apartment complex with some crappy provided setup that had broken local discovery then it would be 1 less thing to worry about.

  • Don't make me think about how much I've spent on VR and accessories...

  • Nice, I would still be tempted to register the inner door code to open the outer door too. I hate redundancy and love the idea of everyone having 1 credential that opens everything they are allowed to access. At my current place we use codes but we don't have access to register them unfortunately so I have to put up with memorizing multiple things, on top of having the front office accidentally reset our accounts one day causing us to need to toss all our old codes and memorize a whole new set because they don't know how to re-register the old codes that they wiped.

  • You can key the shared door to accept both unit keys, while each unit key will only be able to open their own unit and the shared door, but not the other unit.

    I did this when I rented in a multi family home that had a shared outer door but individual unit front doors, so I could use my own apartment key to also open the outer shared door and the shared exterior basement door.

  • Fyi the filters are instance based, so the person you replied to and probably some of the people who downvoted you have no idea what you're talking about. Only we can see it because we're on .ml

  • This is not for the case of using text, it's for protecting text in images. The problem with adding invisible text is that LLMs can defeat it by screenshotting and using OCR. This tries to plug that loophole.

  • Invisible text doesn't work for images though, which is what this is specific for. Invisible text is also defeated by taking a screenshot, so if you use this too then you have a chance of defeating both LLMs that read the text as well as those that screenshot and OCR.

  • For some reason the battery isn't mentioned in the parts list but it's shown in the video and mentioned in the instructions. Would be pretty easy to power the esp feather with a dcdc converter off of a USB port or something assuming it doesn't take 5v directly

  • To re-state, it's not a problem of understanding or the language, it's a problem with overused, bland, and repetitive language and phrasing. It's not fun to read even if you can understand it perfectly.

    Just because 200 people understood your post doesn't mean it isn't annoying to read. And it's a super simple thing to fix - don't use AI to rewrite your post and just use a normal translator instead, which won't inject bland and repetitive phrases and structures.

  • Yeah Google translate preserves a lot more of your communication style. AI overuses so many phrases it can get annoying reading something that was processed through it.

  • It feels like there's been an increasing flood of AI slop projects, with varying degrees of monetization / donations. I think it'll become a huge problem if we don't have at a minimum very strict rules around AI generated slop projects. I think a mandatory tag with penalty of removal is a good bottom floor, in addition to the recent community participation activity % requirements for promoting monetized projects, which covers a good chunk of AI projects.

    Then hopefully soon we can figure out as a community what to do to control the remaining volume of non-strongly-monetized AI slop projects if those are still too widespread, but having it labeled is absolutely needed transparency, and that'll still be difficult because lots of people seem to lie about not using AI.

  • Honestly I like the idea of your project but the writing style of your post is very grating.

  • Ah cool, the docs made it sound like container: uses the container ID hash instead of the name so I wasn't sure how that works. I just put stuff like this in the same compose file since they're all closely related.

  • If it helps, here's how I had my gluetun / transmission set up with mullvad (I've since moved to proton for port forwarding but I saved the mullvad config in case I needed to switch back):

     
        
    services:
      gluetun:
        image: qmcgaw/gluetun:v3
        container_name: gluetun
        restart: always
        cap_add:
          - NET_ADMIN
        devices:
          - /dev/net/tun:/dev/net/tun
        volumes:
          - ./volumes/gluetun:/gluetun
        environment:
          - TZ=America/New_York
    #      Mullvad
          - VPN_SERVICE_PROVIDER=mullvad
          - VPN_TYPE=wireguard
          - SERVER_COUNTRIES=USA
          - SERVER_CITIES=New York NY
          - WIREGUARD_PRIVATE_KEY=
          - WIREGUARD_ADDRESSES=x.x.x.x/32
          - UPDATER_PERIOD=24h
          - UPDATER_MIN_RATIO=0.1
          - UPDATER_VPN_SERVICE_PROVIDERS=mullvad,privado,protonvpn
        networks:
          - default
          - ingress
    
      transmission:
        image: linuxserver/transmission:latest
        container_name: transmission
        restart: always
        network_mode: "service:gluetun"
        environment:
          - PUID=0
          - PGID=0
          - TZ=America/New_York
        volumes:
          - ./volumes/transmission:/config
          - /volume1/Media:/media
    
      flood:
        image: jesec/flood:latest
        container_name: flood-sidecar
        restart: always
        command: --port 3000
        user: "0:0"
        network_mode: "service:gluetun"
        volumes:
          - ./volumes/transmission:/config
          - /volume1/Media:/media:ro
        environment:
          - TZ=America/New_York
          - HOME=/config
        labels:
          - com.centurylinklabs.watchtower.enable=true
          - "traefik.enable=true"
          - "traefik.http.routers.flood.rule=Host(`flood.example.com`)"
          - "traefik.http.services.flood.loadbalancer.server.port=3000"
          - "traefik.http.routers.flood.entrypoints=websecure"
          - "traefik.http.routers.flood.tls.certresolver=mytlschallenge"
          # This example uses "Selective Authentication"
          - "traefik.http.routers.flood.middlewares=oauth-middleware"
    
    
      

    Idk how zimaos works, but the way to attach containers like this is with network_mode: "service:othercontainer" which might need them to be in the same compose file (the docs aren't clear).

    Also note that you can't put any port mappings on a container using network_mode service, you have to put them on the other container that is handling networking since the first container is piggybacking off of the other and doesn't have its own networking.