1,192 karma · joined March 14, 2018
...which is Arch, by the way :D
Blender 2.5 came out ~15 years ago, and as I was learning Blender in 2010/2011 it did not feel nearly as good as it does now. I believe that something similar could happen with FreeCAD, as I tried it some years ago and it was unusable in my opinion, but now I can work with it without any major issues. And the more attention they get, the better it will become.
In FreeCAD it works but you have to think a bit how you approach it. For example, if you reference an edge that you later on go back and delete, of course it will break things. Also if everything is not correctly constrained and you go back and edit it, it will likely break things. And then there are some bugs as well, but it's free and open source so I am not complaining. :)
Similarly as with mesh modeling, where correct modeling style is needed for smoothing not to break things, with CAD you also have to get used to certain approach to modeling, you can't be as chaotic.
But the more you do it, the better you will become and in my opinion learning proper CAD modeling approach is easier than proper mesh modeling in Blender.
The ability to make models precise, constrained and and parameterised more easily allows going back to previous steps to make adjustments.
For 3D printing it is very helpful to be able to change a defined variable and have the whole model recalculated. I often use variables for clearance, screw hole diameters, etc.
Recently FreeCAD has become very good and I have switched to it. And there are a lot of great FreeCAD tutorials on Youtube.
I think it makes no sense for them to put much focus on developing a separate small open source version of their server. So it is good that they actually support its development.
So, looks like Tailscale is paying one of the developers to develop for headscale, as par of his job.
This is one of the best ways a company can support an open source project though.
I guess it doesn't really matter, but it would have been nice to give some transparency to the reader that it was not due to actual technical limitations.
https://github.com/Janhouse/tailscaled-derper/blob/main/dock...
Since we use TLS passthrough and Traefik just proxies TCP, you have to pass certificates to derper, so you either use the Traefik certificate extractor or some other tool to get them.
And initially I though that I would have to integrate libproxyproto into derper in order to handle client IP addresses correctly behind Traefik but it looks like it doesn't really need it.
It would be like complaining Vaultwarden is bad because the Bitwarden project is not fully open source even though Vaultwarden is fully open source and has most of the features implemented.
And Headscale kind of ticks all the other boxes mentioned, except "not headscale", because:
* p2p mesh network - it is a mesh network. And even when mesh is blocked, you can use multiple relay servers (derp) which will relay to the mesh from closest location. And you can host your own derp servers.
* Open source and selfhosted - check
* Not Wireguard (Signature-based blocking) - in cases where wireguard is blocked, the derp relay servers run over https and are usually not blocked based on signatures. For example, I use it with Traefik proxy in TCP mode so I could run derp and other http services on the same 443 port and it works great. So - check?
Packaged in nixpkgs - check
On top of that, if you add Headplane admin UI you get nice graphical management, very similar to the one of Tailscale.
I also recently started playing around with web UI layer that generates traefik json config. Currently it is quite basic since it was initially made to provide limited time access to development instances but it could in theory manage most important aspects of proxy config and replace something like nginx-proxy-manager. https://github.com/Janhouse/traefik-proxy-admin
AeroSpace tiling window manager finally changed my work day from constant struggle to only occasional struggle with macOS. I use it with sketchybar which is not yet perfect, but it could become quite good and performant with some work on it.
I currently use Gnome on Linux, not a tiling window manager, and I would gladly go with Hyprland, but about a year ago while I was trying it out, it crashed quite a few times so it clearly was not ready for production use back then. Will give it a shot again.
There are a lot of gotchas and considerations with Nextjs, but it is a framework and it is not unexpected that unless it is developed by yourself, frameworks require some getting used to.
There are some things that could be better, especially in non-Vercel-hosted scenarios, and if the backend for frontend part becomes too complicated, I would switch to Nest.js, but overall I am satisfied with Next.
Also the infrequent random OS crashes were annoying. And sometimes WiFi would stop working after sleep (wold not show any access points) and would require a reboot.
M1 is 5 years old already and is still not fully stable and lacks features. It seems like the overall development effort started slowing down a couple years ago and while we did get the amazing audio daemon and graphics driver, development of other things seem to be stuck.
If I remember correctly, there were also some comments from Marcan (?) on social media about issues with supporting newer chips (M3/M4), hinting that M3 and M4 are vastly different and require significant effort to add Linux support.
So if M3, M4 and other future versions are too different to get supported in decent time frame, then that means that Asahi is all about supporting years old hardware. That reduces interest by Linux users looking to buy a laptop now, and thus potentially reducing available donations, developer pool, interest, etc.
I love what Marcan, Alyssa, James and others have achieved and how they have pushed Linux further. I think that their contributions will stay relevant and be useful for other hardware for many years to come.
Looking at the drama and people stepping down, I don't think MacBooks will be properly supported on Linux in this decade.
Not sure which of these tools is currently the best but they are clearly needed.
I am testing MetaMCP to expose internal MCP servers to the cloud version of Claude, enabling me to use Home Assistant and some other internal services in verbal conversations with Claude app on the phone.
I think 3rd party MCP server use is available in other AI assistants as well but Claude is the only one who allows using them in Europe.
I can only wish that this would become a standard approach with any AI assistants, including the built in phone assistants like Siri, but Apple is so so far behind and always trying to squeeze every bit of money wherever they can, I doubt they will ever do that.
This approach enables better integrations with local services specific to different regions, and I would somewhat compare this to RSS feeds which were popular 15 years ago. Would be nice if most e-commerce sites would provide their own MCP servers for managing carts, placing and tracking orders, etc. I don't want to see a world where single monopoly grabs this market and makes things shit again (like it happened with social media), especially for those who live outside of USA.
After some fine-tuning and eliminating false positives, it is running smoothly. It logs all the temporarily banned and reported IPs (to Crowdsec) and logging them to a Discord channel. On average it blocks a few dozen different IPs each day.
From what I see, there are far more American IPs trying to access non-public resources and attempting to exploit CVEs than there are Chinese ones.
I don't really mind anyone scraping publicly accessible content and the rest is either gated by SSO or located in intranet.
For me personally there is no need to block a specific country, I think that trying to block exploit or flooding attempts is a better approach.
In order to avoid exposing something unnecessarily in the certificate transparency logs, I use a single wildcard certificate, so all the subdomains are not listed anywhere automatically.
I use the same approach for services hosted in the internal subdomain, because I don't want everyone to know what exactly I'm running in my homelab.