Since when AI content is compared to user content? Why do you change topic?

more good content

Well, it still counts as “more content” which is usually on par with user count.

Lemmy attract its own community naturally

Do you want to see more content, or you don’t?

Yup, developers.

Instance admins adding such tags would make it inconsistent and basically impossible to use. It should be unified = implemented by Lemmy developers.

P.S. Developers who develop Lemmy software. Admins who own and manage instance (website/server).

I really wish there could be tags and sub-tags.

Tag examples:

• Politics
• Sport
• Anime
• News
• AI

Sub-tag examples:

• US
• Europe
• Africa
• Basketball
• Volleyball
• F1

Some sort of curated list by Lemmy developers that might change over time depending on user demand.

Then client apps can fetch such list from any server and allow you to apply such filter.

Imagine being able to block whole category of sports? Anime? News? Whatever people want/don’t want.

You are reffering to “freedom of choice”. It’s a good thing. <3

Pretty buttons

Umm okay. Personal preference.

the ability to scroll and see all my configs in one window with a single click

Isn’t scrolling a single docker-compose.yml easier to see everything? I mean, if you want to change anything - you just edit and re-run command.

What specifically does portainer add?

"Windows engineer’ lmao.

Missing at least these:

1. Load balancers/Reverse peoxies - Caddy, Traefik.
2. Missing DNS server “blocky” which I find way better than Pi-Hole.

Nice list, but could have more. :)

Technically like this:

Anyone -tcp80-> vps -tcp80-> router -tcp80-> homeserver.

Exit of homeserver-originated traffic would be your router, not vps. Unless you specify custom routes in your router, then yeah, might be possible.

Also you don’t need EoIP tunnel at all, since it’s all in Layer4.

Some time ago I’ve done a “public IP implementation” on my VPS when I was on mobile network (no public IP).

Basically set up IPSec/Wireguard on VPS and connect your router to it. Then setup EoIP over VPN between VPS and your router. Then add EoIP tunnel to your LAN’s bridge in your router.

Then setup all ports forwarding (using iptables) from your VPS to your router on LAN, so if you connect to your VPS using tcp80, it will be simply forwarded (NAT’ed) to your router. Except tcp22, for SSH to your VPS obviously…

And now you have yet another public IP lol.

This is not something you asked, but might give you some ideas.

I’ve done something similar in Ireland, where ISP router was the only way to connect. Managed to setup everything on OpenWRT router, but it kept disconnecting, so I put openwrt router behind ISP router.

Interesting thing I found in ISP router is DMZ host - just point it to your own router and that’s it. Basically ISP router doesn’t exist lol.

Then you have absolute freedom with your router.

Isn’t “MAC NAT” you are after? I’ve seen Mikrotik has this feature to perform NAT for bridge devices. EDIT: no, since your ISP might check at DHCP leases and realise that you are cheating. Go with regular router instead.

Also regular router would be sufficient IMO. Also don’t forget to set static TTL value so your “ISP” doesn’t see that you have a router between your devices.

Also create MAC address and save it. Always change it before connecting - you will have less trouble.

How about this?

which threatened her with death

From the taliban point of view:

• Women bad
• Gays bad

How tf does it work in their opinion?

IMO if you are asking such question - stick to Bitwarden cloud.

Passwords, at least to me, is something I don’t want to lose. I don’t trust myself I could provide a proper uptime & security, so I just use cloud version.

Yeah. I just wrote something similar. 😅 https://lemmy.world/comment/1330730

Here is the example docker-compose.yml:

services:
  caddy:
    image: caddy
    container_name: caddy
    volumes:
      - ./caddy/data:/data
      - ./caddy/config:/config
      - ./caddy/Caddyfile:/etc/caddy/Caddyfile
    ports:
      - 80:80/tcp
      - 443:443/tcp
      - 443:443/udp
    restart: always

  lemmy:
    image: lemmy
    container_name: lemmy
    ...

Before executing, create a new directory caddy i working directory, then create new file Caddyfile in it (lemmy is a container name):

mydomain.com {
    reverse_proxy lemmy:<lemmy_container_http_port>
    encode zstd gzip
}

Then fix your UDP Buffer size, so it’s compatible with QUIC: https://github.com/quic-go/quic-go/wiki/UDP-Buffer-Sizes

And that’s it. tcp80, tcp443 and udp443 should be reachable from anywhere, as Caddy out of the box uses ACME to retrieve TLS certificates for your domain.

Give it a try. Honestly Traefik is shit for a simple load balancer. It’s more suited for large enterprises and kubernetes services, but it also has numerous issues, such as basic auth performance issues, lack of headers customization as well as in overall somewhat difficult configuration. Caddy makes it straightforward & simple, which is perfect for simple users who love to self-host.

I tried using Traefik in big corporation, 20+ different load balancer and reverse proxy (all with TLS termination) rules.

Caddy not just worked, but also worked faster and was WAY simplier to setup (using Caddyfile and reverse_proxy directives) than Traefik.