

OK, sure, but again the claim was:
there is no problem in keeping code quality while using AI
Whether or not human-written code also requires review is outside the context of this discussion, and entirely irrelevant.


OK, sure, but again the claim was:
there is no problem in keeping code quality while using AI
Whether or not human-written code also requires review is outside the context of this discussion, and entirely irrelevant.


I’m sorry, what exactly do you think this conversation is about if not using AI for code generation?


No, I want worker protections, regulatory enforcement, and broad public distrust of the exploitative owner class who are using AI to extract more wealth while destroying the environment we all live in.
Patronizing “AI” systems is collaboration with the worst garbage of the human race, the robber barons who are comfortable killing people for quarterly profits.
People like Peter Theil, Elon Musk and Sam Altman.


So don’t accept code that is shit. Have decent PR process. Accountability is still on human.
If this is necessary then there is, in point of fact, a “problem in keeping code quality while using AI”.


Every person in every industry in a rush to replace the work of creative people with output from machine learning models can fuck right off.
Every consumer who is content with products made by such people can also fuck right off.


there is no problem in keeping code quality while using AI
This opinion is contradicted by basically everyone who has attempted to use models to generate useful code which must interface with existing codebases. There are always quality issues, it must always be reviewed for functional errors, it rarely interoperates with existing code correctly, and it might just delete your production database no matter how careful you try to be.


Nice save, and a fantastic PSA.
Also I’m a big fan of sleeping on a problem as a path to a solution. I’m not sure how exactly that skill develops, but it’s definitely something that I’ve done a few times over the years.


There’s a pretty good Behind the Bastards episode on Stahlin. Basically he was an ultra-paranoid drunk that forced his cabinet members to get drunk with him on a regular basis, which pretty much ruined any potential for effective government in the USSR.
Russia has a strong-man fetish which even the Bolsheviks couldn’t overcome. For all the post-revolution ideology and communist rhetoric, they still just want a Tsar.


The more things go in this direction, the more likely they are to join in. The biggest reason they’re (at best) wishy-washy in this area is that they’re trying to pull centrist votes.
If the apparent center shifts, they’ll shift with it.


Depending on what you’re emulating, the 8BitDo ultracompact options might work for you:

Basically turn your phone into a Gameboy, good for 90s games where you don’t need sticks. The controller and clip together will cost you $35.




OK, so you want to install Linux on an old laptop after wiping the hard drive.
Sure, you would have root control for that OS. Make sure that there is no BIOS/UEFI password set before you start, or that you have the password.
Do not use the root account for regular use, especially if you will be connecting this laptop to the Internet. Log in as a normal user account and escalate your privilege as needed.
I also highly recommend gparted for editing the hard drive partitions before you install the OS. Don’t install goarted, just run it live from a USB drive.
Do you know which Linux distribution you want to install?


er, what exactly do you mean by “from the scratch”? and what exactly constitutes “my own system”? are you planning on designing your own logic circuits, manufacturing your own chips, and then writing your own firmware to run them?


Perfect explanation.
Thank you, I try. It’s always tricky to keep network infrastructure explanations concise and readable - the Internet is such a complicated mess.
People like paying for convenience.
Well, I would simplify that to people like convenience. Infrastructure of any type is basically someone else solving convenience problems for you. People don’t really like paying, but they will if it’s the most convenient option.
Syncthing is doing this for you for free, I assume mostly because the developers wanted the infrastructure to work that way and didn’t want it to be dependent on DNS, and decided to make it available to users at large. It’s very convenient, but it also obscures a lot of the technical side of network services which can make learning harder.
This kind of thing shows why tech giants are giants and why selfhosted is a niche.
There’s also always the “why reinvent the wheel?” question, and consider that the guy who is selling wheels works on making wheels as a full-time occupation and has been doing so long enough to build a business on it, whereas you are a hobbyist. There are things that guy knows about wheelmaking that would take you ten years to learn, and he also has a properly equipped workshop for it - you have some YouTube videos, your garage and a handful of tools from Harbor Freight.
Sometimes there is good reason to do so (e.g. privacy from cloud service data gathering) but this is a real balancing act between cost (time and money, both up-front and long-term), risk (privacy exposure, data loss, failure tolerance), and convenience. If you’re going to do something yourself, you should have a specific answer to the question, and probably do a little cost-benefit checking.


But if I’m reading the materials correctly, I’ll need to set up a domain and pay some upfront costs to make my library accessible outside my home.
Why is that?
So when your mobile device is on the public internet it can’t reach directly into your private home network. The IP addresses of the servers on your private network are not routable outside of it, so your mobile device can’t talk to them directly. From the perspective of the public internet, the only piece of your private network that is visible is your ISP gateway device.
When you try to reach your Syncthing service from the public internet, none of the routers know where your private Syncthing instance is or how to reach it. To solve this, the Syncthing developers provide discovery servers on the public internet which contain the directions for the Syncthing app on your device to find your Syncthing service on your private network (assuming you have registered your Syncthing server with the discovery service).
This is a whole level of network infrastructure that is just being done for you to make using Syncthing more convenient. It saves you from having to deal with the details of network routing across network boundaries.
Funkwhale does not provide an equivalent service. To reach your Funkwhale service on your private network from the public internet you have to solve the cross-boundary routing problem for yourself. The most reliable way to do this is to use the DNS infrastructure that already exists on the public internet, which means getting a domain name and linking it to your ISP gateway address.
If your ISP gateway had a static address you could skip this and configure whatever app accesses your Funkwhale service to always point to your ISP gateway address, but residential IP addresses are typically dynamic, so you can’t rely on it being the same long-term. Setting up DynamicDNS solves this problem by updating a DNS record any time your ISP gateway address changes.
There are several DynDNS providers listed at the bottom of that last article, some of which provide domain names. Some of them are free services (like afraid.org) but those typically have some strings attached (afraid.org requires you to log in regularly to confirm that your address is still active, otherwise it will be disabled).


“I’m a personality prototype. You can tell, can’t you?”


“A doctor must go where the sick people are”


The intent is to highlight the stupidity of the tariffs.


OK, sure, but again the claim was:
Whether or not human-written code also requires review is outside the context of this discussion, and entirely irrelevant.