It was meant to be humorous framing, given the impossibility of making humans from magma or the iron core. :)

Which ethnicity’s population are we going to reduce?

I honestly believe that “we” aren’t going to do jack s**t. It’s a process which is nearly unsteerable. People are going to live longer and longer, and use resources that would otherwise be used by children they might have had. Society is going to be burdened by caring for the old, and this is going to reduce chances of caring for the young.

In nearly every developed country, population growth is slowing or population has already started decreasing. Only in the least developed regions (some areas of Africa) does the opposite still apply, but UN predictions (made by competent people) suggest the process just reaches there later.

So, every ethnicity’s population is going to be reduced. Every ethnicity can also consider if their numbers are adequate, too high or too low. If a nation feels threatened by disappearing from the maps, they can try to reorganize their society. Random ideas: a few laws that give parents various health and social security guarantees regardless of their employment status, especially in case they’re single parents, then maybe create a few dating sites that actually try to help their users find people they like, etc…

There is plenty of resources to support humanity.

I cannot say I agree, and I think I recall that some indicators currently suggest we’d need about 3 planets to keep going at the same pace.

I think we shouldn’t use up every atom on Earth to churn out more humans. Our species has experienced a massive population explosion and is at peak numbers.

Usually this kind of events are followed by a hurtful population crash. It seems considerably better if growth ends due to a (subconscious?) decision to stop expanding, rather than a war for remaining resources.

The founder of the Antinatalism International, Anugraha Kumar Sharma, argues that “there is absolutely no hope whatsoever in this world.”

Well, that’s hard to argue against. I might disagree, but I cannot artificially give him any hope, even if he wants some.

For some, the progressive embrace of antinatalism might just be a reaction to the pronatalism espoused by the Right. Because Vice President J. D. Vance wants you to have more children, the only natural reply is that we ought to have none.

Not for me. They can want all they want, but to consider children, I imagine I would need to find a society relatively free of strife, a society with lower risk. I would need to feel somewhat secure in my own future, because you have to raise children for a hefty amount of time. Most importanly, I’d have to find someone who’d like to do this together.

Some creatures respond to environmental stress by breeding earlier and faster, and trying to do that more desperately. I cannot find such a response in my own “code”. I respond to environmental stress by saving resources to overcome hardship, and focusing effort to defeat the source of hardship. If that means a decline in population by 1.7 people, so be it.

I think that in the modern times, more people have started thinking this way. Having children is expensive and can effectively put you below the poverty line, and stop you from pursuing goals, whatever they are.

I’m not even anti-natalist. I’m just not interested in reproduction - precisely because I still have a future that I might influence for the better - but not if I waste my resources on reproduction.

Also, I think a scarcity of humans might actually cause society to value humans more. In the Middle Ages, when the plague reduced populations, serfs were able to obtain better conditions and break the pattern of slavery in many lands. Feudal lords struggled because their vast empty lands could not be managed by their dwindling crew - someone could till a field or hunt game without paying taxes or asking for permission out there. Of course, this pattern might not apply in modern times, however.

the global democratic left has been incapable of developing an economic agenda that looks beyond the next election cycle.

Not sure if I can agree. Over here, the agenda looks pretty clear. Achieve progressive taxation. Achieve higher taxation of capital than labour. Achieve lower taxation of worker-owned companies. Achieve universal health insurance. Beyond the economic, achieve a governing system not disproportionately influenced by the wealthy. Preferably, achieve all this without violence.

(and reaching those goals is prevented by the disproportionate propaganda capability of the economic right, mostly financed by the wealthy)

Некоторые мысли:

• скорее всего, по-русски здесь говорят немногие (но, конечно, есть автоматический перевод). Я говорю, но это не мой родной язык. Чтобы побудить людей к дискуссии, я бы порекомендовал английский.

• создание бренда, который передает какую-то информацию о продуктах, на мой взгляд, решение проблемы не с того конца - бренды так не появляются

• типичный бренд (например, Raspberry Pi) начинается с одного продукта (часто экспериментального) и расширяется. Добавляют новые продукты. Если они лучше, бренд получает репутацию.

• в ходе жизни типичной компании в какой-то момент возникает соблазн обменять репутацию (форму социального капитала) на деньги, сделав что-то дешево и не выполнив обещаний

Но, повторюсь, мне это кажется очень абстрактным и “высоко в облаках”.

— translation —

Some thoughts:

• most likely, few people can speak Russian here (but of course, automatic translation exists). I can, but it’s not my native language. To get people to discuss, I would recommend English.

• creating a brand that conveys useful information about products is, in my opinion, solving the problem from the wrong end… brands don’t appear like this

• a typical brand (e.g. “Raspberry Pi”) starts from a single product (often experimental) and expands. New products are added. If they are better, the brand gets a reputation.

• a classic problem awaits then: in the course of a typical company’s life, at some point, there comes a temptation to exchange a good reputation (a form of social capital) into money, by doing something cheaply and not fulfilling promises

But I repeat, this seems very abstract and “high in the clouds” to me.

Sounds like a nice material. :)

It would be a method of representing trust or distrust in a structured way that’s automatically accessible to the end user.

The user could right-click an image, pick “check trust” from a menu, and be presented with a list of metainfo to see who has originally signed it, and what various parties have concluded about it.

Negative proof: the AI company signs it with their watermark.

Positive proof: the photographer signs it with their personal key, providing a way to contact them. Sure, it could be a fake identity, but you can attempt to verify and conclude that.

Cumulative positive and negative proof: on top of the photographer, news organizations add their signatures and remarks (e.g. BBC: “we know and trust this person”, Guardian: “we verified the scene”, Reuters: “we tried to verify this photo, but the person could not be contacted”).

The photo, in the end, would not be just a bitmap, but a container file containing the bitmap (possibly with a steganographically embedded watermark) and various signatures granting or withdrawing trust.

The concept is new to me, so I’m a bit challenged to give an opinion. I will try however.

In some systems, software can be isolated from the real world in a nice sandbox with no unexpected inputs. If a clear way of expressing what one really wants is available, and more convenient than a programming language, I believe a well-trained and self-critical AI (capable of estimating its probability of success at a task) will be highly qualified to write that kind of software, and tell when things are doubtful.

The coder may not understand the code, though, which is something I find politically unacceptable. I don’t want a society where people don’t understand how their systems work.

It could even contain a logic bomb and nobody would know. Even the AI which wrote it may tomorrow fail to understand it, after the software has become sufficiently unique through customization. So, there’s a risk that the software lacks even a single qualified maintainer.

Meanwhile some software is mission critical - if it fails, something irreversible happens in the real world. This kind of software usually must be understood by several people. New people must be capable of coming to understand it through review. They must be able to predict its limitations, give specifications for each subsystem and build testing routines to detect introduction of errors.

Mission critical software typically has a close relationship with hardware. It typically has sensors coming from the real world and effectors changing the real world. Testing it resembles doing electronical and physical experiments. The system may have undescribed properties that an AI cannot be informed about. It may be impossible to code successfully without actually doing those experiments, finding out the limitations and quirks of hardware, and thus it may be impossible for an AI to build from a prompt.

I’m currently building a drone system and I’m up to my neck in undocumented hardware interactions, but even a heating controller will encounter some. I don’t think people will experience success in the near future with letting an AI build such systems for them. In principle it can. In principle, you can let an AI teach a robot dog to walk, and it will take only a few hours. But this will likely require giving it control of said robot dog, letting it run experiments and learn from outcomes. Which may take a week, while writing the code might have also taken a week. In the end, one code base will be maintainable, the other likely not.

They have made the fences tall, which creates an impression of fragility, but we don’t see how deep the posts run into ground. :)

I have a solar fence in operation for 1 year. My version is 1 panel width tall - about 1.2 meters tall, and I built it extremely cheap - 5 cm rectangular wooden posts with a metal screw tip running 30 cm into ground. Assembly using household screws and luck. During storms, it does change position, but I haven’t noticed disassembly.

During hail, it would survive events that would smash my other panels, because a vertical surface exposes less target area and offers more oblique angles of collision to hailstones.

As for efficiency, my vertical array is the most efficient array I have during winter. It’s never covered by snow and catches low sunshine better. In summer, it is the coolest (but not most efficient) array that I have, because it creates verticial convection and gives away heat more efficiently. But it differs from theirs because it’s an east-west array (they seem to have used a north-south geometry to catch morning and evening sunshine).

As for what they said of their results:

The panels generated much less electricity than a standard tilted array, but it was produced in mornings and evenings. “It matches better when there is high electricity demand in the system,” says Victoria.

The heater model they depict looks good.

• not capable of producing carbon monoxide
• high probability of self-extinguishing when pushed over
• reduced chance of causing burns

Yep, indeed, I’m already discovering differences too. :) A good document for techies to read seems to be here.

https://reticulum.network/manual/understanding.html

I also think I see a problem on the horizon: announce traffic volume. According to this description, it seems that Reticulum tries to forward all announces to every transport node (router). In a small network, that’s OK. In a big network, this can become a challenge (disclaimer: I’ve participated in building I2P, but ages ago, but I still remember some stuff well enough to predict where a problem might pop up). Maintenance of the routing table / network database / <other term for a similar thing> is among the biggest challenges when things get intercontinental.

Interesting project, thank you for introducing. :)

I haven’t tested anything, but only checked their specs (sadly I didn’t find out how they manage without a distributed hashtable).

Reticulum does not use source addresses. No packets transmitted include information about the address, place, machine or person they originated from.

Sounds like mesh networks like I2P and (to a lesser degree, since its role is proxying out to the Internet) like TOR.

There is no central control over the address space in Reticulum. Anyone can allocate as many addresses as they need, when they need them.

Sounds like TOR and I2P, but people’s convenience (easily resolving a name to an address) has created centralized resources on these nets, and will likely create similar resources on any network. An important matter is whether the central name resolver can retroactively revoke a name (in I2P for example, a name that has been already distributed is irrevocable, but you can refuse to distribute it to new nodes).

Reticulum ensures end-to-end connectivity. Newly generated addresses become globally reachable in a matter of seconds to a few minutes.

The same as aforementioned mix networks, but neither of them claims operability at 5 bits per second. Generally, a megabit connection is advised to meaninfully run a mix network, because you’re not expected to freeload, but help mix traffic for others (this is how the anonymity arises).

Addresses are self-sovereign and portable. Once an address has been created, it can be moved physically to another place in the network, and continue to be reachable.

True for TOR and I2P. The address is a public key. You can move the machine with the private key anywhere, it will build a tunnel to accept incoming traffic at some other node.

All communication is secured with strong, modern encryption by default.

As it should.

All encryption keys are ephemeral, and communication offers forward secrecy by default.

In mix networks, the keys used as endpoint addresses are not ephemeral, but permanent. I’m not sure if I should take this statement at face value. If Alice wants to speak to Bob tomorrow, some identifier of Bob must not be ephemeral.

It is not possible to establish unencrypted links in Reticulum networks.

Same for mix networks.

It is not possible to send unencrypted packets to any destinations in the network.

Same.

Destinations receiving unencrypted packets will drop them as invalid.

Same.

Trying to figure out how my heat pump supposedly supports WiFi… in unfathomable and non-standard ways. It’s available as an access point, I can associate and ping it, but no TCP ports listen and no UDP port responds. Nothing cool, undocumented features down to the rocky bottom. When you buy a heat pump and plan to automate its use, check out supported protocols before making a decision. :)

If Chat gave me a broken answer, I would appreciate if someone said “hey, look - it’s broken here”.

The solution is obvious: wind energy can be collected outside a building, on an empty field, or at sea for maximum emptiness. Which is what people already do.

instead of having me listen to your gripes

Not my preferred way of dealing with criticism. You wrote a proposal (well, you let Chat write a proposal and presented it). I read it through, and considered if it was OK. I found parts that weren’t and said so. If you don’t want to listen to that, why did you post?

I am splitting a hair, but the goal is pointing out - Chat is nice at producing text and searching for information, but unreliable at actually evaluating if something would work. Unless you’re extremely good at asking, it will spew proposals that won’t work.

P.S.

As for non-rotating wind generators, yep, I’ve read about them. They aren’t efficient. In the equations determining performance, there is a term named “swept area”. For a non-rotating generator, swept area is the surface of its profile viewed from upwind/downwind. For a rotor, swept area is the surface of the circle reached by blades. The difference is huge.

…and that is why Chat cannot be trusted to build houses. It hallucinates:

Exhibit A:

At its core, this building incorporates an innovative vertical farming system. Towering gardens thrive within its walls,

Exhibit B:

The building’s walls are constructed using rammed earth or compressed earth blocks, utilizing the surrounding soil and natural resources abundantly available in the area.

One can go vertical, or one can go rammed earth. One does not go vertical with rammed earth. :) And wind turbines attached to building structure are a nuisance. An efficient turbine needs to be clear of obstacles.

Beyond that, it has done a good job. The write-up was streamlined with my cultural sensibilities, before it collided head on with my sense of engineering. :)

I tried, and that GitLab page requires logging in. I don’t have an account, so I can’t comment more.

More information can be found here: https://veilid.com/framework

I read it, haven’t tested it - commentary below.

Before I go into commentary, I will summarize: my background is from I2P - I helped build bits and pieces of that network a decade ago. As far as I can tell, Veilid deals in concepts that are considerably similar to I2P. If the makers have implemented things well, it could be a capable tool for many occasions. :) My own interest in recent years has shifted towards things like Briar. With that project, there is less common ground. Veilid is when you use public infrastructure to communicate securely, with anonymity. Briar is when you bring your own infrastructure.

• Networking

Looks like I2P, but I2P is coded in Java only. Veilid seems to have newer and more diverse languages (more capability, but likely more maintenance needs in future). I2P has a lot of legacy attached by now, and is not known for achieving great performance. A superficial reading of the network protocol doesn’t enable me to tell if Veilid will do better - I can only tell that they have thought of the same problems and found their own solutions. I would hope that when measured in a realistic situation, Veilid would exceed the performance of I2P. How to find out? By trying, in masses and droves…

• Cryptography

Impressive list of ciphers. Times have changed, I’m not qualified to say anything about any of them. It leaves the appearance that these people know what they are doing, and are familiar with recent developments in cryptography. They also seem to know that times will change (“Veilid has ensured that upgrading to newer cryptosystems is streamlined and minimally invasive to app developers, and handled transparently at the node level.”), which is good. Keeping local storage encrypted is an improvement over I2P - last time I worked with I2P, an I2P router required external protection (e.g. Linux disk encryption) against seizing the hardware. With mobile devices ever-present everywhere, storage encryption is a reasonable addition. I notice that the BlockStore functionality is not implemented yet. If they intend to get it working, storage encryption is a must, of course.

• RPC (remote procedure calls)

Their choice of a procedure call system is unfamiliar to me, but I read about it. I didn’t find anything to complain about.

• DHT (distributed hash table)

Looks somewhat like I2P.

• Private routing

Looks very much like I2P.