walden

At the bottom of the page (in a browser)

At the bottom of the page (in a browser) click ModLog and search for your username.

I’ve used it plenty of times for other reasons. I can never remember what kind of CPU I have and it tells me. I can’t even remember how much RAM I have, and it tells me that, too.

I’m sure the next thing someone is going to do is tell me the individual commands to find that info, but I can’t be bothered with that.

Oh thanks for the heads up

Aha, that must be it. The photo in question is 6.7MB

I’m able to save a trail without any photos, but if I try to add a photo it lets me select the photo, but saving the trail gives a toast notification in the bottom right that says “Error saving trail.” The web, db, and search logs don’t show any errors.

Mine was having some weird problem with docker, I think it must be a docker bug. Basically it put the Wanderer stuff at the very bottom of the routes (running “sudo route” on Debian lists the routes). The last entry in the routes table needs to be eth0 or the equivalent so that stuff can loop back to the beginning of the list. At least that’s my understanding.

So anyway, to get around that bug/limitation I had to create a static docker network which I called “wanderer-static” using docker network create --attachable -d bridge --subnet 172.28.0.0/16 --gateway 172.28.0.1 wanderer-static. Choose a subnet that’s not being used already.

Then in the docker compose file, point everything at that network by:

Removing

 networks:
   wanderer:
     driver: bridge

Adding

networks:
  wanderer-static:
    external: true

And finally, pointing each service to that network. Under each service you should have:

    networks:
      - wanderer-static

I also had to update the ORIGIN and whatever else to http://wanderer-static:7000, etc.

Looks cool. I have it up and running with the docker compose provided. Every time I try to create a user it says “Error creating user”, and the logs say [ERROR] [23:30:00]: Login failed. Unable to obtain cookie.

Edit: I got it working, just had to updated some of the network stuff in the docker compose. The networking in Portainer is a bit “complex”.

I can’t get photos to work. Oh well.

I think a law passed allowing businesses to do this now. Before they were bound by their agreements with pay processors. Typically they allowed a discount for cash, but not an extra charge for credit. The whole “$10 minimum for credit cards” wasn’t supposed to happen, either.

Now the payment processors aren’t allowed to enforce that type of rule.

Source: I read a similar comment elsewhere on the internet a couple of years ago, and that’s what I remember from it.

I wouldn’t say so. Digital rights, online privacy, etc. apply to everyone, not just people sharing files on the internet.

Interesting choice.

Is Pirate Party a nickname or do they actually call themselves that?

This is honestly the most confusing and complicated part of self-hosting.

I agree! It took me years to finally decide to buckle down and wrap my head around what a “reverse proxy” is. Once I figured it out things became so much more usable and fun.

Combined with DNS redirects in my LAN (to get around NAT loopback), things are very easy to use.

FYI here’s a link to the other compose file I was talking about: https://github.com/LemmyNet/lemmy/blob/main/docker/docker-compose.yml

The only downside to keeping everything in a lossless format is that over the years new formats emerge. mp3 used to be the only game in town, but now we have multitudes of lossy formats to pick from. By having your collection in mp3 format, you aren’t able to say “hey, this new format looks cool, let me switch to that”. By storing everything in a lossless format (FLAC), you can convert for mobile as you see fit.

That was a fun watch.

I just updated my comment above with more info, FYI.

I’m not a pro at Docker, but I’ve spun up over 30 different services using Docker Compose so I’m more than a novice. I would say that Lemmy’s documentation is the worst I’ve ever seen.

The website points you at that compose file which is (I think?) designed for Ansible. I think there’s another example somewhere without all the jibbery joo, but I can’t search for it right now.

Edit: here it is https://github.com/LemmyNet/lemmy/blob/main/docker/docker-compose.yml

No idea why they don’t link to that one in the first place. I’d fix it if I knew how.

I think the docs recommend (and this is how I have it set up) leaving the go2rtc stream as you have it currently, and changing the stream path for the camera config to rtsp://127.0.0.1:8554/nursery

Is the problem that the bags aren’t long enough? Fill the bottom of the can with something the bag can rest on.