

Australia is (has?) pulling all research scientists off Macquarie Island due to worries about the potential stress of thousands of seals dying en-mass:


Australia is (has?) pulling all research scientists off Macquarie Island due to worries about the potential stress of thousands of seals dying en-mass:


thanks you and @Irdial@lemmy.ml LM Studio was the tool I think I was looking for


see, I don’t really do popular (except for the kids) and private trackers just seemed like too much hard work


Ive trued private trackers, but there is very little for me to try and keep up the ratio them while on public my share ratio is well above 5.
Public trackers and no vpn gets it done


the red die is to indicate untaxed, it will stain fuel filters on road vehicles to show that untaxed diesel has been used, at least that is how it us used elsewhere


ok, but then that has extra tax attached (assuming, as I’m not in the US, that is like the UK where red diesel doesn’t have all the road tax attached.) Here in NZ it is all ‘white’ diesel and Road User Tax is separate


that is true, but it will still be needed to used to gather in all the autumn crops and plant the spring ones not too far away


I have Gulf of Mexico (Gulf of Authoritarian)


I still have Ontario on desktop and the wifes android down here


original content written with or which facilitates the use of LLMs (large language models) or other generative AI technologies
I feel that this becomes very restrictive.


Yes the flavours may bit a bit more, but here in NZ our beef is generally outside all year and grass fed so tends to be richer/stronger than some meat that I’ve had overseas.
And like any meat, treat it well to get the most out of it


There is nothing wrong with wild meat, nor cheval
QBT-nox
just sits there and runs


and if a crew does an ev battery correctly re-ignition is low from what i’ve heard. They can be harder to put out though.


his full diapers?


I have AdGuard Home running on OPNSense as a local DNS with a wild card for for the ‘local domain’ pointing to Caddy
in Caddy I have this section:
*.<domain>.net {
#header X-Frame-Options "SAMEORIGIN"
tls internal
encode gzip
import sec-headers
@sub1 host pve.<domain>.net
@sub2 host kasm.<domain>.net
...
handle @sub1 {
import sec-headers
reverse_proxy * https://10.1.1.11:8006/ {
transport http {
tls_insecure_skip_verify
}
# header_up Host {host}
header_up X-Real-IP {remote}
header_up X-Forwarded-For {remote}
header_up X-Forwarded-Port {server_port}
header_up X-Forwarded-Proto {scheme}
}
}
handle @sub2 {
import sec-headers
reverse_proxy https://10.1.1.119/ {
transport http {
tls_insecure_skip_verify
}
# header_up Host {host}
header_up X-Real-IP {remote}
header_up X-Forwarded-For {remote}
header_up X-Forwarded-Port {server_port}
header_up X-Forwarded-Proto {scheme}
}
}
...


Lets just ban Viagra - as it affirms your ‘masculinity’


maybe about a year a go I read an interview with a Iranian official - it was basically “If the US brings a war to us there will be unbelievable hurt in reply - they have no idea what we are capable of”
Turns out it was right on the money


Back up the server then work through:
Just follow the guide https://iocaine.madhouse-project.org/documentation/3/getting-started/ Bind the iocaine service to 0.0.0.0:42069
cat /opt/iocaine/etc/iocaine/config.d/00-server.txt.kdl
http-server default {
bind "0.0.0.0:42069"
use handler-from=default
}
expose interface to Docker (make sure not to expose it to the world).
sudo iptables -I INPUT 4 \
-s 172.18.0.0/16 \
-d 172.18.0.1 \
-p tcp --dport 42069 \
-j ACCEPT
add the interface to the proxy service in a custom/docker-compose.yml.template
proxy:
{{COMPOSE_CADDY_IMAGE}}
env_file:
- ./caddy.env
- {{ CADDY_EXTRA_ENV }}
volumes:
- ./caddy/Caddyfile:/etc/caddy/Caddyfile:ro
- caddy_data:/data
- caddy_config:/config
extra_hosts:
- "host.docker.internal:172.18.0.1"
...
add iocaine to caddy in a custom/Caddyfile.template
{$LEMMY_HOSTNAME} {
import caddy-common
######################################
########## iocaine code ##########
@read method GET HEAD
reverse_proxy @read host.docker.internal:42069 {
@fallback status 421
handle_response @fallback
}
...
rebuild all the docler images (at least the caddy one ./deploy.sh -f) and test
I think that should work
CrowdSec
this seems interesting