Darkassassin07

If Iran struck Mar A Lago while Trump was golfing there, I might just jizz my pants.

Hard to say for sure really.

I can respect someone's religious views as long as they aren't trying to push them on me. That's to say; not trying to make me believe the same or insist that I have to follow the rules of their chosen religion.

As far as my own views go; I don't follow any particular religion. I don't necessarily believe there isn't some form of god, but I don't follow/believe in any specific deity either. Maybe there is, maybe there isn't; but there have been hundreds of thousands of gods/goddesses/deities/religious figures throughout human history. Who's to say you've chosen the correct one, along with the correct set of (sometimes oddly specific) rules and regulations to go along with it?

You want commandments to follow? Here's one:

"Don't be an asshole"

Everything else kind of just falls into place around that. As long as we can respect each other and our differences; yeah, romance is certainly possible.

That's fair. I think it kind of depends on how much you interact with creators and their communities. (comment sections, comunity posts, live content, etc)

I haven't browsed Reddit since the creation of my Lemmy account (~2years ago); though I've wound up viewing a Reddit thread or two via a google search on rare occasion. Beyond those two, the only other 'social media' I've used in at least a decade is Youtube.

'Could' vs 'are'.

They may not have been, but they could if they wanted to, supposedly.

Now, if they didnt before, they certainly have the motivation and arguably the justification.

I certainly wouldn't blame them for seeking out nuclear weapons now.

The thing is, until someone actually faces any consequences in modern times for atrocities such as these; simply saying how bad they are has become meaningless.

I'm not sure whether this is specific to this project, docker, or YAML in general.

Looking through my other 20 or so compose files, I use the array notation for most of my environment variables, but I don't have any double quotation marks elsewhere. Maybe they're not supposed to work in this format, idk.

Good to keep in mind I guess.

Dev replied to my github discussion.

Apparently it's an issue with array style env variable layout.

environment:
    key:"value"

Instead of

environment:
    - key=value

Trying to set that up to try out, but I can't get it to see/use my config.yaml.

/srv/filebrowser-new/data/config.yaml

volumes:

• /srv/filebrowser-new/data:/config environment:
• FILEBROWSER_CONFIG="/config/config.yaml"

Says '/config/config.yaml' doesn't exist and will not start. Same thing if I mount the config file directly, instead of just its folder.

If I remove the env var, it changes to "could not open config file 'config.yaml', using default settings" and starts at least. From there I can 'ls -l' through docker exec and see that my config is mounted exactly where it's supposed to be '/config/config.yaml' and has 777 perms, but filebrowser insists it doesn't exist...

My config is just the example for now.

I don't understand what I could possibly be doing wrong.

/edit: three hours of messing around and I figured it out:

• FILEBROWSER_CONFIG="/config/config.yaml"

Must not have quotation marks. Removed them and now it's working.

Come with me, and you'll be, in a woooorld of OSHA violations!

Our* boys, lol

Decided to do some more reading on this topic. TIL:

TCP, the more common protocol; requires at least one side to have a port forwarded through their NAT to the client, so the other side can make a connection to that open port.

uTP on the other hand, can 'holepunch' by sending a packet to a known IP, which opens a port through the sending clients NAT, specifically for that IP. That port can then be used to send and receive by either side until it closes due to inactivity.

So, torrent clients can use uTP holepunching to open a port without requiring manual forwarding, then advertise that open port to public trackers. Client 'A' will try to connect to an IP+port it got from the tracker and get ignored (because the recipient NAT isn't expecting data from that IP and drops the packets). Then when client 'B' decides to connect to client 'A', 'A's port will now be open and allowing data from 'B's IP, thus establishing a connection.

This is slower than a direct connection because both clients need to be made aware of each other and decide to attempt to connect at reasonably similar times. It also requires public trackers with peerexchange enabled and the torrents cannot be flagged as private.