hsdkfr734r

hsdkfr734r , 13 days ago

To blow leaves.

hsdkfr734r , 15 days ago

I'm not sure if this counts as a comic strip. I would say no if pressed for an answer.

hsdkfr734r , 17 days ago

Thaumaturge. You mean a "wizzard" or sorcerer?

hsdkfr734r , 17 days ago

Yes, this. Magic, wizardry, witchcraft, sorcery, spellworking and maybe... enchantment. : )

hsdkfr734r , 19 days ago (edited 19 days ago)

Divide by 1/2 or multiply with 2/1. It's an equivalent transformation.

hsdkfr734r , 1 month ago

Nice. I think I get that reference.
Both arguments are true.

To be fair they also open source more recent products like... power shell. One could argue, they do it to increase their market share. But is it a market if everybody gives away his products for free?

In the end they are an organisation that has to feed its members and share holders. So no blind trust. But it's still nice that they share it.

hsdkfr734r , 1 month ago

Not anymore, you don't!

hsdkfr734r , 1 month ago

I assume you want to access a self hosted service on your local server from the Internet.

To make the service accessible from the Internet multiple things are required:

• the router can be accessed from the outside. Find your public IP in the router or use a find-my-ip website. Better: do both.
  This is the address you can use to access your router (or whatever service you choose to expose through it).
  Side note: If the Ip-adresses of your router and the one of the find- my- ip- site are different it could mean that your provider uses CG-NAT (because ipv4- addresses are scarce, the provider doesn't give you a real publicly accessible address). This means you can't access your router from the Internet. Try IPv6 or contact your provider to get a publicly accessible ipv4- address.
• because the above mentioned IP- address of your router might change, dyndns is used. Configure it in your router and test it. Test if the DNS- name you have set up resolves to your ip- address (nslookup or ping it).
• to make your service available to the Internet you need to configure port forwarding in your router (or add your server as exposed host - means all ports are forwarded to the Internet). This means the router passes request to itself on to your internal server.
  Careful: everybody can access whatever services you expose. Advice: it's a good idea to use a VPN. Setup a VPN-server in your Lan and only port-forward its port in the router. Connect to the VPN from the outside - Afterwards use the internal services through the vpn- connection.
• scripts and the internal ip: the dyndns name needs to be used instead of the IP. Find a way to make the scripts use that name to resolve it to your external IP.

hsdkfr734r , 1 month ago

Space. The
final Fröntier.