When looking through the history of Windows, some of the major milestones included the very concept of a windowed user interface in 3.1, refining the concept into a complete desktop-oriented (as in, a physical table top, with files and folders and a recycling bin) experience in Windows 95, huge backend improvements in the kernel (eg networking) by merging in the NT kernel (last used intact in Windows 2000) and giving us Windows XP.

Note well that XP was the first juncture between a consumer-oriented OS (a la Win 95/98) and a business-oriented OS (a la NT Server or Windows 2000). The missing link here is Windows ME, which was the next consumer OS after 98 but it flopped so hard when it became apparent that this artificial consumer/business division wasn’t going to scale. Specifically, the Windows 9x kernel had too many DOS-isms whereas the NT kernel had no such issues. Hence, Microsoft undertook the massive effort to bring the two kernels together for XP.

In that sense, XP coupled a newer kernel with a polished UI. In essence, the company bet all its chips on XP. And fortunately for them, it paid off. But this came with a cost: XP has to carry the lineage of both the DOS/95/98/ME and NT/2000 into the 21st Century. This means the same OS has to support things like Active Directory (a feature only used by corporate customers) and Fax for Windows (used by anyone that wanted to use their dial-up modem for faxing, but also on fax servers, which are somehow still relevant today), while also supporting DirectX for the consumer gaming segment, plus multi-user support for “home computer” customers that still share a single machine for a household, despite a market trend towards personalized computing, and everything else under the sun.

And that’s before we get to some of the backwards-compatibility support they still have to upkeep, like 32-bit support on the x86 family of CPUs, and BIOS (in spite of UEFI being a decade old). Notably, Windows on ARM has never kept such backwards compatibility, with ARM32 being completely deprecated and only ARM64 being supported by Windows 10 and beyond (hence, Windows on Raspberry Pi).

And then, of course, the Microsoft own-goals and mistakes: somewhere around 8.1, they decided to meet the tablet/touchscreen market by having Windows be touch-oriented. But as was blitheringly obvious then and now, the desktop concept cannot possibly be similar when the controls (keyboard/mouse versus touchscreen) are swapped out. Thus, this compromised the desktop experience in pursuit of a relatively niche target market. Meanwhile, Apple essentially forked their Mac OS to support mobile, tablet, and smartwatches as iOS, and aren’t exactly itching to merge iOS back into the desktop OS.

A better execution might have been to port Windows for ARM (which is what most/all phones and tablets use today) earlier than they did, use that as the basis of a tablet-experience OS (like how Windows Media Center was just an application atop Windows XP), and then later introduce compatibility with desktop apps (like how Apple can now do full-speed x86 emulation using special ARM extensions baked into their custom silicon). That said, the latter was only technically achievable in the 2020s, but seeing as Microsoft was the market leader well into the 2010s, they would have been in the same position as Apple is in today.

So to summarize my long-winded comment, Windows carries a lot of weight. It is the result of successfully merging two very-real market segments into one product (business users and consumer users), then MSFT dropped the ball by chasing the Next Big Thing and adding more diametrically-opposed objectives to an over-burdened OS, with nary a plan for how to eventually relieve it. Had they instead did a separate OS for tablet and mobile (rip Windows Phone), they could have merged that one into the XP-based kernel and got the refined best-of-both-worlds.

Instead, they now have the worst of both. The Windows 11 desktop experience sucks, with bad icons, near-invisible text boxes, confusion where there wasn’t any, and all while pushing consumers towards web browser-based apps. And to make it sting harder, because they’ve been feeding this mess to their corporate customers, those customers now demand that everything be kept the same (“better the enemy that you know”) which prevents Microsoft from making XP-level wholesale improvements.

They’re stuck, they know it, and they can’t really fix it unless great leadership shows up to take command of the ship. But similar to Amazon (which makes most of its revenue through AWS, not selling/shipping products), Microsoft makes the majority of its revenue in two segments: Azure cloud and Office 365. It’s hard to revamp Windows when it’s now playing third-fiddle.

(I’m sure I’ve got some of the historical details wrong, but it’s Saturday morning so full send)

The absolute first thing is to establish the jurisdiction of this scenario. The answer will be vastly different if the jurisdiction is California/USA than if the jurisdiction were South Susan. No shade against South Sudan, but we are talking about criminal and civil law, so the details might be very different.

But supposing this is a jurisdiction that follows in the Anglo-American common law (such as California, and I’ll proceed using California as the setting), then we can make some generally-true statement, some of which confirm what you’re already written:

1. Criminal law exists to punish bad acts committed against society at-large
2. Criminal law can only punish the persons or entities which have committed an act or omission that is proscribed in law, and only those persons or entities within the territory
3. Dead people or dissolved corporations are beyond the reach of criminal law
4. The notion that the next-of-kin will “inherit” the criminal liability was abolished long ago; see US Constitution “Bill of Attainder” prohibition, and equivalent in other jurisdiction like the UK or Australia
5. Anyone that is still alive and collaborated to aid or supply the dead assailant can be pursued using criminal law or civil lawsuits, or both
6. In parallel to the criminal law system, civil lawsuits can be filed against the remaining property of the dead assailant. This is known as the “estate” of that person, and the lawsuit would be captioned as “XYZ v the Estate of [dead assailant]”
7. A civil lawsuit can only win as much property as the respondent (ie person being sued) has, or any insurance policy they had which might apply, or any debt which was owed to the respondent at the time of their death.
8. Mass murder commonly result in civil lawsuits that do not obtain anywhere near the full amount to compensate for the victims’ families’ loss.
9. As a result, the target of civil lawsuits can be expanded to include adjacent parties, such as the manufacturer of the weapon or materials used, under a claim of product liability or something similar. This is not a guaranteed result, but they often have deeper pockets and good insurance policies.
10. Civil lawsuits can only bring a monetary compensation. The law cannot revive the dead, cannot erase or amend history, and cannot salve the void left when victims are removed from this world unjustly.

With all that said, the entire line of inquiry into the dead assailant’s will, or to their parent’s will, or anything like that, is entirely inapplicable. Children or parents do not inherit the sins of others, at least where criminal liability and civil lawsuits are concerned. Unless, of course, the parents participated somehow or willfully neglected a duty to report (very few of these exist in California, unless the victims were undoubtedly known to be children; see mandatory reporting laws). Thus, these other people cannot be sued nor criminally punished, usually.

The other commenter correctly said that what we call the “justice system” is more accurately called “harm reduction”. That’s not wrong, but I would post that the crimimal law system is about harm reduction (nb: I do not endorse the carcereal state of imprisoning huge segments of the population, disproportionately by race), whereas civil lawsuits are about equity and compensation.

Both systems exist in tandem to prevent people from achieving a bloodier form of justice in the streets, like in days of yore: pistols at dawn, dueling in general, lynching, “bigger army” diplomacy, shakedowns, midnight slaughters of whole families, and other such unpleasantries. It’s definitely not perfect, and it needs reforms in many parts, but the structure serves a purpose and so far, it’s what we have and the best that we have.

I think this would easily qualify for !brandnewsentence@lemmy.world

I’ve even seen people vibe code ethernet drivers for freeBSD.

Please make sure to read what considerations that developer had before undertaking that effort using an LLM: https://github.com/Aquantia/aqtion-freebsd/issues/32#issuecomment-3997341698

Specifically, they (the human) were kept in the loop for the entire process, which included referencing the working Linux driver to do a clean-room reimplementation. This already means they have some experience with software engineering to spot any issues in the specifications that the LLM might generate.

Also, Aquantia (before the merger) already had a published FreeBSD driver but it hasn’t been updated. So this port wouldn’t have to start from zero, but would be a matter of addition support for new NICs that have been released since, but Aquatia hadn’t updated the driver.

This is very much not an example of an Ethernet NIC driver being “vibe coded” from scratch, but a seasoned engineer porting Linux support over to FreeBSD, a kernel that already has a lot of support for easily adding new drivers in a fairly safe manner, and then undertaking a test plan to make sure the changes wouldn’t be abject slop. That’s someone using their tools with reasonable care. In the industry, this is called engineering.

Admiration for what people can do with the right tools must always be put into the right context. Even with the finest tools, it’s likely that neither you nor I could build a cathedral.

I don’t think they can be force applied to everyone who contributes

This is certainly an opinion, but here is a list of major projects that have a code of conduct: https://opensourceconduct.com/projects . How well those projects enforce their CoCs, idk. But they are applied, otherwise they wouldn’t bother writing out a CoC.

it’s not fair to hold people to standards they didn’t personally agree to

Software development is not the only place which holds people to standards. The realm of criminal and civil law, education, and business all hold people to standards, whether those people like it or not. In fact, it’s hard to think of any realm that allows opt-out for standards, barring the incel-ridden corners of the web.

this guy might have just decided to make a project

Starting any project – as in, inviting other people to join in – is distinct from just publishing a public Git repo. I too can just post my random pet projects to Codeberg, but that does not mean I will necessarily accept PRs or bug reports, let alone even responding to those. But to actually announce something, that where the project begins. And to do so recklessly does reflect poorly upon the maintainer.

I’ve not heard of Booklore or the critiques against it until seeing this post, but I don’t think this take is correct, in parts. And I think much of the confusion has to do with what “open source” means to you, versus that term as a formal definition (ie FOSS), versus the culture that surrounds it. In so many ways, it mirrors the term “free speech” and Popehat (Ken White) has written about how to faithfully separate the different meanings of that term.

Mirroring the same terms from that post, and in the identical spirit of pedantry in the pursuit of tractable discussion, I posit that there are 1) open source rights, 2) open source values, and 3) community decency. The first concerns those legal rights conferred from an open-source (eg ACSL) or Free And Open Source (FOSS, eg MIT or GPL) license. The details of the license and the conferred rights are the proper domain of lawyers, but the choice of which license to release with is the province of contributing developers.

The second concerns “norms” that projects adhere to, such as not contributing non-owned code (eg written on employer time and without authorization to release) or when projects self-organize a process for making community-driven changes but with a supervising BDFL (eg Python and its PEPs). These are not easy or practical to enforce, but represent a good-faith action that keeps the community or project together. These are almost always a balancing-act of competing interests, but in practice work – until they don’t.

Finally, the third is about how the user-base and contributor-base respect (or not) the project and its contributors. Should contributors be considered the end-all-be-all arbiters for the direction of the project? How much weight should a developer code-of-conduct carry? Can one developer be jettisoned to keep nine other developers onboard? This is more about social interactions than about software (ie “political”) but it cannot be fully divorced from any software made by humans. So long as humans are writing software, there will always be questions about how it is done.

So laying that foundation, I address your points.

Open source should mean that anyone can write anything for fun or seriously, and we all have the choice to use it or not. It doesn’t matter if it’s silly or useful or nonsense or horrible, open source means open. Instead we shut down/closed out someone who was contributing.

This definition of open-source is mixing up open-source rights (“we al have the choice to use it or not” and “anyone can write anything”) with open-source values (“for fun or seriously” and “doesn’t matter if it’s silly or useful”). The statement of “open source means open” does not actually convey anything. The final sentence is an argument in the name of community decency.

To be abundantly clear, I agree that harassing someone to the point that they get up and quit, that’s a bad thing. People should not do that. But a candid discussion recognizes that there has been zero impact to open source rights, since the very possibility that “Some contributors are working together on an unnamed replacement project” means that the project can be restarted. More clearly, open-source rights confer an irrevocable license. Even if the original author exits via stage-left, any one of us can pick up the mic and carry on. That is an open-source right, and also an open-source value: people can fork whenever they want.

How they were contributing is irrelevant

This is in the realm of community decency because other people would disagree. Plagiarism would be something that violates both the values/norms of open-source and also community decency. AI/LLMs can and do plagiarize. LLMs also produce slop (ie nonfunctioning code), and that’s also verbotten in most projects by norm (PRs would be rejected) or by community decency (PRs would be laughed out).

We should all feel ashamed that an open source project was shuttered because of how our community acted.

I would draw the focus much more narrowly: “We should all feel ashamed that an open source project was shuttered because of how our community acted”. Open-source rights and open-source values will persevere beyond us all, but how a community in the here-and-now governs itself is of immediate concern. There are hard questions, just like all community decency questions, but apart from Booklore happening to be open-source, this is not specific at all to FOSS projects.

To that end, I close with the following: build the communities you want to see. No amount of people-pleasing will unify all, so do what you can to bring together a coalition of like-minded people. Find allies that will bat for you, and that you would bat for. Reject those who will not extend to you the same courtesy. Software devs find for themselves new communities all the time through that wonderful Internet thing, but they are not without agency to change the course of history, simply by carefully choosing whom they will invest in a community with. Never apologize for having high standards. Go forth and find your place in this world.

I second the option of Git + SSH. That will scale to one hundred repos. And if you don’t want the repos to be checked out, use “git clone -n” to not do that. It’ll just be dozens of repos which only have the minimal .git/ directory. All other repos that specify this one as the upstream will have no issues pulling or pushing code.

You won’t have PR features nor a web UI though.

Castle builders

In Anglo-American common law, if a party has previously argued a position in one of their own cases, and later argues a different position in a subsequent case that they’ve a party to, then the doctrine of equitable estoppel would foreclose on certain claims from that party. As usual, the devil is in the details.

Firstly, they must be a party to both the prior and prospective case. A motorist that is injured in a multi-vehicle pile-up cannot assert different facts when suing each of the participants in the crash. However, an advocacy group that files a petition on behalf of another is, by definition, not the party that is bringing suit. Nor is anyone that offers an amicus (ie “friend of the court”) brief that advises the court on how a case ought to be decided.

Secondly, the exact things which are foreclosed will depend. The most common benefit available under equitable estoppel is the loss of a presumption of good faith. So if party A is a corporation and claimed in an earlier employer/employee case that their CEO’s crass, sex-pest behavior was a result of substance abuse (in an attempt at a medical defense or a defense about temporary inability to perceive the situation), then that assertion – irrespective of whether it actually won them that earlier lawsuit – could be used against them in a later case litigated by the shareholders. If the company is sued for the CEO not conveying accurate business info, the defense that their CEO acted in good faith is not going to carry water, if the events coincided in time.

As you can see, the exact remedy that equitable estoppel provides isn’t exactly clear-cut in every instance. But the goal is to prevent the same litigant from abusing the judicial system. One cannot come into court on Monday claiming the sky is blue when it’s convenient for them, then claim on Wednesday that the sky is not blue when it’s inconvenient for them. Two-face assertions are not allowed.

To be clear, these must be actual assertions. Sometimes a civil case can be won merely by the likely possibility that someone else is at fault, making it impossible to determine fault. And so no assertion may be needed as a defense. If a pedestrian is struck and injured by a hit-and-run motorist driving a red car, and five red cars are identified later, any of those motorists can correctly state that there were four other such cars in the area. Pointing out facts unfavorable to the plaintiff is exactly what the defense is supposed to do. But if a motorist actually says “I didn’t injure her”, then that’s an assertion. And judicial estoppel means they may not later claim, for some reason in a later case, that they did do it.

Predominantly in Texas, Buc-ees is nominally a chain of gasoline stations but they’re known for the stores attached to the station, selling all manner of kitsch but also fast food. Ok, they’re also known for having 100+ pumps at each location. But that’s important because it means they’ve always been located at the periphery of city boundaries, on huge lots, usually on the highways into or out of town.

When the gasoline business dries up, Buc-ees still has other business interests to keep them going in the road travel market, and they have real estate along major corridors that could be redeveloped. One option is to invite businesses that occupy motorist’s time while parked charging their electric cars, like wayside attractions (besides Buc-ees itself, obviously). Another would be to fully entrench themselves: develop a hotel so that visiting business people always stop at the Buc-ees before leaving.

So while neighborhood fuel stations would see a slow demise, Buc-ees can turn their fuel locations into new cash cows. This is why diversification is so important.

Whole sections of the country that are zoned for suburban single family housing would not exist as they are today. Not because they’d be illegal or anything, but they’d be incredibly unpopular if most people didn’t own a car, which is needed to basically get to or from a suburban neighborhood.

I understand the question to be something like: what happens if a majority of people are absolutely dead-set unwilling/unable to own a private automobile. And I think the immediate answer is that suburban neighborhoods cease to exist, at least at the current density levels. Either a neighborhood must densify so that transit options make sense, or they must aim to become rural living. This also means that things like suburban schools either turn into walkable urban schools, or into small one-room rural schools.

I don’t actually think rural living will go away, because the fact is that the grand majority of people – USA and abroad – do not prefer rural living. The 18th, 19th, 20th, and 21st Century trends are that people tend towards urban areas, where services and jobs exist. That said, there will always be people that want to live in the hills on 20 acres, and therefore need an automobile. And it’s certainly sounds appealing to some, myself included. But that has never been the majority, so if a majority of people refuse owning an automobile, they will also mostly refuse rural and suburban living.

There is no plausible situation where over 50% of people willingly decide to: 1) not own a car, and 2) live in a suburb or rural area. This is from the fact that all other modes of transport into a suburb or rural area are either: 1) nonexistent (eg metro rail), or 2) ludicrously expensive (eg Lyft, or transit with 15% fairbox recovery) if the cost was borne by the people living there (as opposed to being subsidized heavily by other taxpayers… Ahem, America).

Edit: some more thoughts: standalone strip malls would also change character, because the smaller ones that aren’t on a rail or bus corridor would be undesirable commercial real estate. If they still exist, they’ll likely be integrated into housing, so as to become the #1 most convenient option for people living there. Captive audience, indeed.

But larger strip malls and shopping centers actually might florish: they usually have enough stores and services that transit already makes sense. Indeed, shopping malls are actually really good transit center locations. But instead of giant parking lots, there would be housing, because why not? People who reject cars have every reason to live next to, or on top of, a mall: fully pedestrianized, air conditioned, lots of stores and dining options. Some places even put schools and post offices in their shopping malls. I would also expect that dwelling soundproofing to get better, because the paper-thin walls of American homes and apartments are awful.

In this way, malls are no different than casinos, cruise ships, and downtowns: a small island of paradise to visit, and is distinct from home. Malls will still exist after cars, the same way that Las Vegas exists in the middle of a desert: it is a big enough anchor that draws people.

I too have issues with silicone earbuds, and also with them falling out. Which is why I was over the moon when I discovered wireless clip-on earbuds. They meet my criteria of being convenient (because wireless) while also not falling off (because clip-on). The specific ones I bought (Anker Soundcore c30i) are not noise-cancelling, but I found that I can adjust their position up or down my ears to meet conditions. For example, I wear them high up when out in public, to hear wayward automobiles that might run me down.

Fair, though I personally don’t let my ISP indirectly dictate what I do with my LAN. If I didn’t already have a v6-enabled WAN, I would still manage my LAN using IPv6 private range addresses. There are too many benefits to me, like having VMs and containers be first-class citizens on my LAN, rather than sitting behind yet another layer of NAT. That lets me avoid port forwarding at the border of my home Kubernetes cluster (or formerly, my Docker Swarm), and it means my DNS names correctly resolve to a valid IP address that’s usable anywhere on my network (because no NAT when inside the LAN).

I will admit that NAT64 is kinda a drag to access v4-only resources like GitHub, but that’s only necessary because they’ve not lit up support for v6 (despite other parts of their site supporting v6).

This is my idea of being future-ready: when the future comes, I’m already there.

The approach isn’t invalid, but seeing as you already have the framework set up to deny all and log for IPv4, the same could be done with IPv6.

That is to say, your router advertises an IPv6 gateway to the global internet, but you then reject it because your VPN doesn’t support v6 (sadly). I specifically say reject, rather than drop, because you want that ICMP Unreachable (administratively prohibited) message to get returned to any app trying to use v6. That way, Happy Eyeballs will gracefully and quickly fall back to v6. Unless your containers have some exceptionally weird routing rules, v6 connections will only be attempted once, and will always use the route advertised. So if your router denies this attempt, your containers won’t try again in a way that could leak. v6 leaks are more likely when there isn’t even a route advertised.

This makes your apps able to use v6, for that day when your VPN supports it, and so it’s just a question of when the network itself can be upgraded. IMO, apps should always try for v6 first and the network (if it can’t support it) will affirmatively reply that it can’t, and then apps will gracefully fall back.

This also benefits you by logging all attempted v6 traffic, to know how much of your stuff is actually v6-capable. And more data is always nice to have.

I’m so confused on what the point of such a hash would be. If the time that an email was sent was so important, would existing DKIM timestamps also work? Is this basically the digital equivalent of including today’s newspaper in a ransom note?

Not to say that DKIM as-used is perfect.

For an example of where constant current sources are used – and IMO, deeply necessary – we can look to the humble LED driver circuit. LEDs are fickle devices, on account of their very sharp voltage-current curve, which also changes with operating temperature and is not always consistent from the factory. As a practical matter, the current through an LED is what predominantly controls the brightness, so constant current sources will provide very steady illumination. If instead an LED were driven with a constant voltage source, it would need to be exceedingly stable, since even a few tens of millivolts off can destroy some LEDs through over-current and/or over-heating.

For cheap appliances, some designs will use a simple resistor circuit to set the LED current, and this may be acceptable provided that the current is nowhere near overdriving the LED. Thing of small indicator LEDs that aren’t that bright anyway. Whereas for expensive industrial LED projectors, it would be foolish to not have an appropriately designed current source, among other protective features.

In a nutshell, voltage incompatibility is generally more damaging than current mismatch, typically in a frightening or energetic manner. Many Americans tourists find this out when they bring their 120v AC hairdryers to an overseas hotel with 230v AC power. If there is only room for one number to be emblazoned on an outlet or plug, it should be the rated voltage, first and foremost.

For current protection, we’ve had thermal fuses since the 1890s, and thermo-magnetic circuit breakers since the 1940s. There are even more fancy transistor-based current protections available for industrial equipment that can shut off extremely fast. In a sense, protection against over-current has basically been solved, in the scenarios where there’s enough of a risk of humans or property.

Whereas voltage mix-ups still happen, although consumer electronics are now moving to automatic voltage detection (eg an 18v electric drill battery charger refuses to charge a 12v battery) and through actively negotiated power parameters (eg USB PD). And even without human error, under- and over voltage transients still happen in residential and commercial environments, leading to either instant damage or long-term product degradation (eg domestic refrigerator motor drive circuits).

It should be noted that a current starvation scenario, such as when an ebike is current-limited per regulations, does not generally cause a spike in voltage. Whereas in a voltage starvation situation, resistive loads will indeed try to draw more current in order to compensate. Hence why current protection is almost always built-in and not left to chance.

Firstly, I wish you the best of luck in your community’s journey away from Discord. This may be a good time to assess what your community needs from a new platform, since Discord targeted various use-cases that no single replacement platform can hope to replace in full. Instead, by identifying exactly what your group needs and doesn’t need, that will steer you in the right direction.

As for Element, bear in mind that their community and paid versions do not exactly target a hobbyist self-hosting clientele. Instead, Element is apparently geared more for enterprise on-premises deployment (like Slack, Atlassian JIRA, Asterisk PBX) and that’s probably why the community version is also based on Kubernetes. This doesn’t mean you can’t use it, but their assumptions about deployments are that you have an on-premises cloud.

Fortunately, there are other Matrix homeservers available, including one written in Rust that has both bare metal and Docker deployment instructions. Note that I’m not endorsing this implementation, but only know of it through this FOSDEM talk describing how they dealt with malicious actors.

As an aside, I have briefly considered Matrix before as a group communications platform, but was put off by their poor E2EE decisions, for both the main client implementation and in the protocol itself. Odd as it sounds, poor encryption is worse than no encryption, because of the false assurance it gives. If I did use Matrix, I would not enable E2EE because it doesn’t offer me many privacy guarantees, compared to say, Signal.

Musical chairs would indeed be a “fast paced and exciting” environment, but in the least desirable way.

Obligatory mention: !keming@lemmy.world