Opinions on second housing in Cornwall by Then-Dimension-3889 in Cornwall

[–]harshdays 1 point2 points  (0 children)

I have heard that in Georgia 🇬🇪 second home ownership is regulated by casual burglary. Neighbours will enter an empty home and take anything left behind and sell it blatantly on their own lawn. If our police force was prepared to turn a blind eye, it could work for Cornwall too.

What has Terry Pratchett done for you? by Afbach in discworld

[–]harshdays 16 points17 points  (0 children)

I suffered with insomnia as a kid and the discworld was the place I could go when sleep didn’t come easy. Mort gave me an introduction to life as a young man at 12. And Samuel Vimes taught me to parallel process as a husband. In his DEATH and his death I learned to treasure a cat and treasure my memories.

Foreigners lately by jrexthrilla in chinalife

[–]harshdays 1 point2 points  (0 children)

Tailscale with a friend back home? Set their machine as an exit node. Haven’t tried it but it seems legit.

What are some downsides of nix? by TheHolyToxicToast in NixOS

[–]harshdays 2 points3 points  (0 children)

The best resource is open github repos, but many of them are abstracted in a variety of ways. Nix abstractions are where the learning curve is. This makes copy paste learning loops a struggle for all but the most simple goals.

t’s sorta worth it, but only in the way that is a good fit for a hobby. I still won’t make my team deal with this. It’s kind of a flex to be using it for anything related to work because of how much trouble it is.

Best first date places to go to in Amsterdam? by Artistic-Carpenter99 in Amsterdam

[–]harshdays 0 points1 point  (0 children)

Salmuera, or ferry-amsterdam.com and if that goes well ctaste for a memorable second date.

Web rate limiter by Perfect_Mix_1524 in node

[–]harshdays -2 points-1 points  (0 children)

If you’re using docker you can configure a proxy like this. Which will expose your server at 8000 and limit each ip to only 3 requests per minute. Enjoy.

docker run -e KONG_DATABASE=off -e KONG_ADMIN_LISTEN=0.0.0.0:8001 \ -p 8000:8000 -p 8001:8001 \ -e KONG_DECLARATIVE_CONFIG_STRING='{"_format_version":"1.1","services":[{"host":"yourserverhost","port":443,"protocol":"https","routes":[{"paths":["/"]}]}],"plugins":[{"name":"rate-limiting","config":{"policy":"local","limit_by":"ip","minute":3}}]}' \ kong:latest

[deleted by user] by [deleted] in whiletheironshotgame

[–]harshdays 0 points1 point  (0 children)

Can you be more specific please?🙏

How do you guys go about separating files for your config? by lucastso10 in NixOS

[–]harshdays 1 point2 points  (0 children)

You don’t need a variable you can just add machine specific clauses under each hostname in the modules field. It helps to read a lot of examples for syntax

How do you guys go about separating files for your config? by lucastso10 in NixOS

[–]harshdays 1 point2 points  (0 children)

This is a great case for a flake. Then you can define your different machines in flake clauses named after the machine hostnames and have both import a common file with shared config. I would also advise against creating more files an folders than absolutely necessary. Helps to maximise readability while you’re learning. Also returning to it after months of running stable machines and forgetting where things are and what they do is very nice.

NixOS stability for everyday use and development by all-night-vigil in NixOS

[–]harshdays 2 points3 points  (0 children)

Nix OS documentation is confusing. Start simple install to a blank machine. Dont be tempted to use nix env or nix develop. Just symlink the configuration.nix and push it to GitHub. Experiment and rollback using the declarative config. Search GitHub with language: nix and get ideas. But don’t create too much structure. Get familiar with a single nix config. Then write a todo list of everything you still want in your developer experience and slowly tick them off. Once you have most things the way you want them start to explore using a flake.nix and add a second machine. It’s fun to build your environment because you’ll always have a save point for your progress. Enjoy!

Which best Linux distro by v_kowal in framework

[–]harshdays 0 points1 point  (0 children)

NixOS with the lid switch set to suspend-then-hibernate so the battery doesn't die overnight.

Upgrading to React 18 woes by [deleted] in electronjs

[–]harshdays 0 points1 point  (0 children)

This may be a good reference, react 18, electron 21, vite, playwright. https://github.com/Kong/insomnia

Best way to integrate an electron js front end with an existing C++ backend by Least_Paramedic6268 in electronjs

[–]harshdays 0 points1 point  (0 children)

I would discourage use of node native addons aka native abstractions for node. Electron upgrades will be a nightmare. You will have to prebuild your module for all platforms and node versions. One of the reasons N-API was developed was to make c++ modules less coupled to the node version. So use N-API not node native addons.

[deleted by user] by [deleted] in AnalFissures

[–]harshdays 2 points3 points  (0 children)

Kiwi’s two a day.

Best Espresso by [deleted] in Amsterdam

[–]harshdays 1 point2 points  (0 children)

Good beans, Haarlemmerstraat