@gattsuru's banner p

gattsuru


				

				

				
10 followers   follows 0 users  
joined 2022 September 04 19:16:04 UTC
Verified Email

				

User ID: 94

gattsuru


				
				
				

				
10 followers   follows 0 users   joined 2022 September 04 19:16:04 UTC

					

No bio...


					

User ID: 94

Verified Email

it took urban liberal Jewish/* lawyers to deploy it in practice?

I think urban liberal would have stood stronger on its own.

I didn't claim Vaxry is blameless or looks good, or even that his faults were merely insufficient empathy. From my first post:

And to be fair, there's some pretty embarrassingly childish behavior, there: a couple years ago Vaxry joked with wanting to get AIDs as a the same as identifying as gay, and separately a moderator screwed around with a user's public profile (then at the time, the only way to put pronouns up) for yucks.

But there's a bit of a problem.

There's a paradox of tolerance issue here, banning is not the only way to exclude bright people from your community. You can also do it just by being an asshole to them. Some people are brilliant assets that turn dumb if you start overtly politically attacking them. Some people need to be able to express the "nasty" things they believe to be true to think properly. This is a fundamental competing access needs issue that you can't just gloss over by never banning anyone.

As a nitpick, Popper's Paradox of Tolerance wasn't using 'tolerance' to mean 'things that progressives like today', but the simple possibility of open debate and discussion.

But more critically, few if any people who try to bring this more expansive non-Popperian version forward do so in any even-handed way. Vaxry's Discord isn't part of freedesktop.org. Vaxry is not accused of behaving poorly in FreeDesktop.org spaces, and I've not been able to find any evidence of such, whether because he's autistic enough to follow their rules in their spaces, or just from lack of opportunity.

You may say that there's a competing access need, but the modern-day variant turns into an insistence that the competition is over. If Vaxry and his cohort can't "express the 'nasty' things they believe to be true to think properly" in a Discord and github issue specific to their project, they can't be 'acerbic' anywhere -- and that's very clearly the target that the FreeDesktop.org held. In that view, the choice is between 'banning' people in the sense that they feel excluded and turned around because of things they found by digging at depth into it, and just directly actually-banning people. The first group will always be able to expand their ranks and justify greater interdiction.

And, to be blunt, the direct-bans get no small amount of people knowing that they'll be excluded by assholes, anyway. It's just that the banhammer-wielders are sort of asshole that the people in charge like.

Most projects don't really have enough people for complex structures. I keep pointing to MinecraftForge, and while the commit log is even less good of a record than normal because some parts were ported from other version control, it gives a good idea of how much Zif's Law applies even for these structures. To the extent they end up with multiple maintainers at all, it's much more often to solve the 'hit by a truck' problem than any serious planning.

There's been a few efforts to come up with more robust structures, but I'm skeptical that they're trying to solve the right problem, nevermind actually having a solution. Given that the FOSS ones I can name are QuiltMC and Rust, this is... not the most encouraging endorsement (and Quilt specifically had a big snafu over their original keyholder).

Linus Torvald has lieutenants, and in practice who you draw matters a lot, but in theory and at the edge case he's got veto power over everything and anything that catches his attention. Python has a five-person lead council since van Rossum retired in 2018, but the only way to cycle the leadership is to wait. Occasionally you'll see corp-adjacent groups try to have reviewers selected from other parts of the same project or even from a set who just do reviews, but then the people reviewing the PRs aren't really tied to the code it's changing.

The bigger problem's that the overwhelming majority of FOSS contributors don't stay in any place for that long, especially when it's not their own project, and those that do tend to be a little obsessed.

For the most part. I'm not sure whether Vaxry overestimated his 'power' -- from the e-mail chain, he pretty clearly saw the RedHat dev's starting e-mail as absolutely showing the FreeDesktop team was ready and willing to ban his ass, knew they could and would, and he seemed more concerned that FreeDesktop was going to try to take over as much of the Hypr space as possible. And while he worked on FreeDesktop's git, it wasn't his community, or really even a community given how much of a kludge any communication around the FreeDesktop-specific areas tended to be.

FreeDesktop could always fork Hypr, and Vaxry could (and since, has) forked wlroots, and FreeDesktop was already using a lot of his tools; that's what FOSS means, to a large extent.

The problem's more that this fractures an (admittedly small) portion of the FOSS community: even if we don't get the whole 'bad person touched this thing' reaction, there's definitely people on the "start looking at how they want to see their world curated" chain. A lot of things like 'many eyes make all bugs shallow' or 'working with the best ideas on the planet' start falling apart once you start banning people from your Issues and PR pages.

Is Free Desktop important?

FreeDesktop is the space (literally a GitLab instance, may heaven have mercy on their souls) where people build the tools that almost all Linux desktop environments run on, including X11 (the user interface drawing framework that underlies every conventional desktop from GNOME to KDE to Cinnamon to ChromeOS) and Wayland (which is what Linux is starting to move toward as a replacement). So it's about as relevant as Linux On The Desktop is, for better or worse.

What's hyprland?

Hyprland is technically 'just' the window compositor (lies-to-children version: stitches applications together into a function desktop 'screen'), but it's more generally used as a name for the desktop environment produced by mixing it and other pieces together, like GNOME or KDE would be. This is a quick video showing just how it looks, and this some of the different behaviors. Essentially, it's designed for rapid but space-optimized window control, whether by mouse or keyboard, and management of many virtual desktops easily.

Hyprdots is a more fully-featured mix of it and those other pieces.

It doesn't have a huge userbase, even by not-Chromebook Linux standards, but it's easily the most popular Wayland-specific desktop environment. The Discord has a 10k members, for what little that's worth, and most users probably only bother with the discord if something breaks and they can't fix it.

Is Vaxry important?

Vaxry is the founder and lead developer for hypr, along with having done some work for wl-roots, which is a library many projects use to simplify common Wayland requirements. He's not the only person working on hyprland, but the commit comparison looks like this, and the other hypr stuff is even more lopsided.

This ban won't prevent him from writing further hyprland work, but it will block him from writing any pull requests or even issues for Wayland or wl-roots, and the broader response will make hypr-like conventions or projects harder to adopt, even when correct.

A Linux Cancellation

Vaxry, the creator and maintainer of hyprland, has been banned from FreeDesktop.Org and its member projects.

Background and Dramatis Personae

The Linux pipeline to an actual desktop is complicated and made of a bunch of moving parts, buried under the actual GUI itself, following the dual Linux philosophies of having everything do one task well(ish), and filling technical discussion with as many three-letter acronyms as possible. A historically important one is the X Window System, also known as X11 or xorg, but is both long in the tooth, covers an unusually wide area of ground for a Linux component, and is incredibly janky. While incredibly important for normal desktop users, the system has a long and bizarre history, with long periods of strife or minimal development: the current FreeDesktop space is technically just an independent github competitor for Linux desktop-specific development, but in practice there's a lot of RedHat Linux people in high places, in no small part because RHEL is the biggest way to be a linux dev and actually make money from it.

In recent years, many X11 developers have moved over to create a new version that better separates responsibility between the display protocol and everything else, along with covering a number of places that X11 just made bad mistakes in 1990 has been stuck with since, and this has turned into Wayland (and some related libraries like wl-roots), developed on the FreeDesktop.org gitlab. It's not quite ready for prime-time, especially for tasks like gaming with a nVidia card, but it's getting pretty close, and there are already some capabilities (eg, multiple displays with different refresh rates) that are a single text-file mod away in Wayland and you'd have an inconsistent time with in X11.

While some existing desktop environments, such as KDE, have worked to directly port over from X11 to Wayland, many Linux devs have taken the opportunity to try Weird and New things, instead, either because the need to develop several components previously internal to X11 seems like the best opportunity for such novel task, or because they're Linux devs. One branch consists of tiling window managers: while not new to Linux (or even Windows, they've taken some increasing popularity in the Wayland environment. Two of the most popular current ones are Hyprland and Sway. Though I'll caveat that popular here means you can find people using it: there's reason it's hard to find packages for them outside, and even harder to find prebuilt distros with it enabled. (Manjaro has a Sway community iso, in case you want to make three bad decisions at once.) Both are independently developed from FreeDesktop, though dependent on the Freedesktop-built wl-roots library.

Hyprland was founded by the psuedoanon Vaxry. I've described it in other contexts as catgirl thighhigh, and even the official github glamour shots are very clearly within that ethos, with many of the community themes being even more so. You could force it to look Professional, but the defaults provide a bizarre combination of mouseless window management, varied and sometimes obnoxious keyboard combinations, a fully text-based and live-updated config system, strong support for transparency and multiple desktops virtual or otherwise, and highly performant and kinda goofy animations (and fucking default-on rounded window corners, wtf). You don't have to own a Blahaj to like the theme, but there's a cluster of personality types that it seems to appeal toward, and the other half of them involve the sorta person that can leave leekspin on repeat for five hours on a second monitor and find it keeps getting funnier every single time they see it. Sway is intended as a drop-in-replacement for the much-older (x11) i3, and [a little more professional/grognardy in its base form, for better (hypr considered a license switch in a PR without having consulted a lawyer first) and worse (manual tiling).

Like a lot of Linux desktop environments (begun, the why-is-gnome-pronounced-that-way wars have), they Don't Like Each Other. Hyprland gives Sway special thanks "For showing how 2 do stuff the overkill way", Sway's original author has written multiple blogposts over the last six months with names like "Hyprland is a toxic community". This mostly didn't matter for Freedesktop.Org, though, since it's the sorta linux space where things like an official irc server would be a little too newfangled and a little out-of-scope.

And They Kept Using Discord

Which means most of the drama happens in weakly-affiliated channels. Hyprland has a Discord server, and while its membership is a mix of Blahaj and leekspinners, its ethos is very much toward the latter. In addition to mainstay stuff like a server ruleset that might as well be summarized as "don't make me come over there", right under announcements channel is the #days-since-vaxry-was-an-idiot, and not far under that is the official list of all accepted fanart of hyprchan, the hyprland mascot. (I didn't say the leekspin side was never trans, anymore than the blahaj side solely trans.) But while the server and Vaxry were willing to tolerate and use what could charitably be called 4chan humor and more accurately be called rude and bad jokes, they do keep to the rule poc||gtfo.

In early March, a Red Hat employee operating under the auspices of FreeDesktop contacted Vaxry about things he, and moderators of his Discord, had done. And to be fair, there's some pretty embarrassingly childish behavior, there: a couple years ago Vaxry joked with wanting to get AIDs as a the same as identifying as gay, and separately a moderator screwed around with a user's public profile (then at the time, the only way to put pronouns up) for yucks. However, toward the end, that employee spelled out that that "... if more bad and more recent behavior ends up coming to our attention - it can be damaging to freedesktop's reputation as well, and we would have to consider steps to protect our community's reputation". Vaxry took this as a threat, and this escalated, first with the Red Hat employee highlighting that "The code of conduct team absolutely has the right to remove you from Freedesktop.org and ban you from the gitlab instance", and then when, when Vaxry said "further emails from the freedesktop.org's Code of Conduct team will now be ignored unless You, as a team, decide to change Your attitude wrt. the issue at hand", the freedesktop Code of Conduct team pulling that trigger, Vaxry put various comments on his blog, yada yada.

Bang-Bang! Maxwell's silver hammer came down upon his head.

Both Vaxry and the unnamed RedHat employee come across as prats in the e-mail chain. It's very easy to read that chain as RedHat wanting on paper an official "It won't happen again" commitment and show of contrition, especially as hypr has become a bigger part of the wayland world (there's no serious census, but hypr's userbase seems the biggest among novel Wayland compositors; hyprcursor is genuinely a major improvement over the fucked-up xcursor, and has no serious competitors). It's also very easy to see this e-mail exchange as somewhere between requiring hypr spaces to act fully under RedHat corporate norms, and more cynically hanging up a Sword of Damocles for later -- even assuming arguendo that Vaxry's behavior retroactively justified the threat in the first e-mail, it made it very clear it was a threat.

((And for various reasons it's a little concerning to have two desktop environment developers that aren't quite clear on how capitalization works.))

There's a certain irony in the stolid and more formal Sway being the Blue-Tribe-themed one, and the purple-and-pink-and-blue-everywhere unprofessional hypr-active world being the not-Blue-Tribe-themed one, but there's another sense where it's not a huge surprise.

Ostensibly, this shouldn't matter much. Yes, hyprland and wayland and wl-roots are still buggy messes. But to the extent hyprland might be more vulnerable now to Wayland or wl-roots bugs, if Vaxry can't supply PRs or even bug reports to wl-roots, it'll drive the fixes to hypr, to the broader Wayland ecosystems' detriment. There are other people using hypr that could still report it up (and Vaxry has already forked wl-roots). In practice, any dev taking hypr-like conventions, especially newer devs, can and should be a little cautious in freedesktop environments, and there's already been a slow siddle away from hypr among the influencer set. There's been calls in some package managers to pull the project after some early posts from DeVault, which to be fair have been mostly rejected; we'll see if that changes. Which still doesn't matter.

But there's a tendency among a Certain Set to talk about how cancel culture has peaked, or how it doesn't impact 'normal' people, or how it's just a fiction, and I think it's worth mentioning the examples that don't show up in google news or conventional culture war channels.

The DJI device feels a lot like an upscaled version of the Lego MindStorms kit. It's okay as an entry-level tool for everything, and that's what makes it appealing for new learners, but you can't really get in deep or into expertise for any component. If you're programming, you're either running Python or Scratch, and even with an adult instructor it's not a great environment for learning Python. You can take it apart and reassemble it, but you're really limited in what you can physically build with it; you can rearrange DJI-provided sensors, but it's hard to even use other PWM devices, nevermind something really weird like a random I2C or SPI sensor.

The mecanum drive is a major selling point, and five or ten years ago getting decent mecanum wheels was nightmarish enough FRC or FTC teams would 3d-print them (pro tip: don't), though now a small robot set can be found under 80 USD. They do definitely make path coding easier to get right, at least for open-space play.

You could definitely build something better for a similar or slightly higher price, so a lot depends on what you're trying to do and introduce: for a student new to robotics, it's one of the cooler-looking options to dip your toes; to a student with experience it's a bit of a (very pricey) toy that gets frustrating if you try to do anything deeper. Probably the strongest selling point comes about if you really want to focus on video/image processing, and you just want a platform to do it on.

I can't speak much for the competitions and camps. As far as I know, the youth sports never went out of east Asia, the university league is 'international' but requires all competitors to be attached to a college (and the pieces look vastly un-challenging for college students), and the camps are inaccessible. Which is a pity, because I like the idea of something between BattleBots-one-robot-leaves and FIRST-it's-about-working-together-for-a-high-score philosophies.

Oof. I guess I'll need to work on making my summary of the recent hyprland cancellation a bit more readable.

Thanks for saying so. I've been trying to highlight more esoteric stuff, but it necessarily involves dropping a pile of context at the start of a post, and it's hard to tell the right balancing point between succinct-but-incomplete and complete-but-infodumpy.

Cynically, "celebrate" in the mission statement probably means 'get scholarships and burnish college resumes': FIRST doesn't pull in a lot for either, but it really clearly wants to have the cash of a sports team scholarship and the reputation of an Eagle Scout.

Less cynically, a lot of school environments teach tech, not just poorly, but also as a chore, even when it could or should have been fun. You don't and shouldn't celebrate or applaud things just for being present, but from physics labs to chemistry to programming to the complete destruction of the shop class, we've lost a lot of the framework for 'projects' as things that can be completed or have real win/lose states. For all my complaints, FIRST, even at its goofiest FLL versions, avoids that problem.

In discussing Dunbar's number, it's not uncommon to see people divide matters into sub- and super-Dunbar counts (eg from 2013), and this can be useful in some contexts, but it also munges together a million-person org that's constantly growing (or trying to constantly grow) and a 200-person-org that's doing minimal recruiting.

Hyperdunbar approaches do not merely require an organization to exceed Dunbar's number, but that the organization constantly be striving for growth, unconstrained and reaching for infinity or the nearest limit. They do not merely have the problem that superDunbar groups do of wildly changed social dynamics, but the constant churn makes even many of the social technologies built for superdunbar organizations break.

Apologies for coining a word for what may well be have an obvious term.

Apologies, this post was a little more stream of consciousness than I'd intended. My thesis is more that :

  • Every organization, even an organization of one person, must select relative priorities of growth against other targets. For businesses, marketing and investment versus product development; for artists, growing your audience against growing your skills; for streamers focusing on following the algorithm versus following your interests. For FIRST, that's a part of that's the division between creating and expanding teams versus developing skills for those teams, but the pattern exists much more broadly.

  • Organizations that make that decision don't do so (only) because they've forgotten their original goal, or because they've been taken over by people who don't care about that goal, but because scale does genuinely have (distributed) benefit.

  • But that strategy has costs. Effective Altruists often focused on the degenerate cases, where outreach becomes almost all of what the organization does, or where outreach has hit decreasing returns while the organization is unwilling to admit that. But there are more honest problems, such as where this emphasis on outreach disconnects your metrics from your measures, or where successful growth can Baumol you as relative productivity varies with scale for individual parts of the organization.

  • More critically, it is fundamentally risky approach at the level of individual people, while obfuscating the outcome of that gamble. If a consistent and always-applicable recruitment paradigm existed, you would already have joined, as would every adult in the county/country/planet; if you could keep in mind the outcome of your recruitment efforts, it wouldn't exceed your Dunbar number. Not everyone approached can be a recruit, not all recruits persist (or are even desirable), so on: even successful orgs notorious for their outreach can spend hundreds of manhours to get four or five mid-duration recruits. Organizations can eventually make this work out by playing the odds across a large enough number of people, but individual actors within the organization can not. Hyperdunbar non-outreach/recruitment efforts can similarly be risky and hide their outcomes: it's very easy to give a talk before a thousand people, and very hard to know what portion of the audience was listening the next day.

  • Because of their public-facing nature, difficulty of measurement, influence of the internet and media coverage (and, cynically, hyperdunbar organization efforts to dazzle or baffle their membership), these approaches are what are most visible when looking into most fields from outside, such that they seem like the only viable option.

  • But that framework is flawed; hyperdunbar efforts can and often do run face-first into a ditch.

  • Even some efforts toted as wildly successful can fade off at shockingly low numbers. That's not to call them a failure for doing so, even if it's not always or often what the stated goals were. However, it shows a space where the tradeoffs necessary to try to scale to vast numbers weren't necessary.

  • And a lot of good can be done outside of hyperdunbar efforts.

Against A Purely HyperDunbarist View

World’s for FIRST is in a week.

For those unfamiliar with the organization, For Increasingly Retrobuilt Silly Term For Inspiration in Science and Technology runs a series of competitions for youth robotics, starting from a scattering of Lego Mindstorm-based FLL competitions for elementary and middle schoolers, to the mid-range 20-40 pound robots of FTC that play in alliances of 2v2 across a ping-pong-table-sized space, and for high schoolers FRC running 120-pound robots in 3v3 alliances around the space of a basketball court. Worlds will have thousands of teams, spread across multiple subcompetitions. (For a short time pre-pandemic, there were two Worlds, with all the confusion that entailed.)

If you’re interested, a lot of Worlds competition will streamed. And a lot of both off-season and next-season competitions and teams are always looking for volunteers.

The organization’s goal... well, let’s quote the mission statement:

FIRST exists to prepare the young people of today for the world of tomorrow. To transform our culture by creating a world where science and technology are celebrated and where young people dream of becoming science and technology leaders. The mission of FIRST is to provide life-changing robotics programs that give young people the skills, confidence, and resilience to build a better world.

There’s a bunch of the more normal culture war problems to point around. How goes the replacement of the prestigious Chairman’s Award with Ignite Impact? If not, complain at least that it’s a missed opportunity on the level of POCI/POCI for replacing a bad naming with a worse one? How do you end up with events playing the PRC’s theme song before the US national anthem?

There's even internal culture war stuff, which may not make a ton of sense to outsiders. Does the move away from commercial automotive motors to built-to-FIRST and especially-brushless motors privilege teams with more cash, or compromise safety or fair play? Should regional competitions, which may be the only official field plays small teams get, also accept international competitors? Should mentors white glove themselves, should they only do so during official competition events, or should the possibility of the Mentor Coach be abolished?

But the biggest question in my mind is how we got here.

Worlds competition is an outstanding and massive event, with an estimated 50k-person attendance at a ten-million-plus square foot convention center. And it’s a bit of a football game: there’s a lot of cheering and applause, and a little bit of technical work. There will be a number of tiny conferences, many of which will focus on organizational operations like running off-season events. People network. That’s not limited to Worlds itself, though the dichotomy is more apparent there: there might be one or two teams per regional competition that have a custom circuit board on their robot, but I'd bet cash that the average regional bats under 1.0 for number of teams with custom polyurethane or silicone parts.

Indeed, that football game is a large part of how teams get to Worlds. The competitions operates as a distributed tournament, where players who win certain awards may elect to continue to the next event in a hierarchy. The exact process and what exact awards count as continuing awards are pretty complex and vary by location (especially post-COVID), but as at the FRC level, the advancing awards prioritize two of the three teams that won a local competition's final, and then the team that has done the most recruitment and sponsoring of FTC or FLL teams over the last three (previously five) years, and then the team that has done the most for the current year. (Followed by the most competent Rookies, sometimes, and then a whole funnel system rolling through more esoteric awards.) In addition to the inherent randomness of alliance field play, there's a rather telling note: the 'what have you done for FIRST today' award, if won at the Worlds level, guarantees an optional invite to every future Worlds competition. By contrast, teaching or developing esoteric skills or core infrastructure is an awkward fit for any award, usually shoved into the Judge's Award, which with 3.5 USD won't buy you a good cup of coffee at Worlds.

There’s reasons it’s like this, and it’s not just the Iron Laws of Bureaucracy, or the sometimes-blurry lines between modern corporate infrastructure and mid-level-marketing. The organization hasn't been hollowed out by parasites and worn like a skinsuit (at least not in this context): it's the sort of goal that the founders and first generation would have and do consider a remarkable victory. I’m not making the Iscariot complaint, because it’s not true.

FIRST couldn’t exist in the form it does without these massive events and the political and public support they produce, not just because you wouldn’t hear about any smaller organization, but because the equipment and technology only works at sizable scale. Entire businesses have sprung up to provide increasingly specialized equipment, FIRST got National Instruments to build a robotics controller that resists aluminum glitter a little better, even the LEGO stuff has some custom support, and they can only do so because an ever-increasing number of teams exist to want it. SolidWorks, Altium, dozens of other companies donate atoms and/or bits on a yearly basis; the entire field system for FRC wouldn’t work without constant support and donation by industrial engineering companies. WPI might devote a couple post-grad students to maintaining a robotics library without tens of thousands of people using it, but I wouldn’t bet on it. States would not be explicitly funding FIRST (or its competitors) unless those programs can show up on television and have constituents that can show up at a state politician’s door.

Those demands drive not just how FIRST operates today, but what its interests are looking toward the future, not just in what it does, but what it won’t do. From a cynical eye, I wouldn’t say with certainty that FIRST would drop ten community teams for a school system buy-in, or twenty for a state program, but I wouldn’t want to be on the community team for any of those hard choices. There is no open-source motor controller or control board available for FIRST competition use, and there’s not a procedure available to present one, and there won’t be. There’s a lot of emphasis on sharing outreach tricks, and a little for sharing old code or 3d models, and a lot of limits to providing skills.

Because throughout this system, the most impactful thing you can do is always getting more people. It’s not Inspiring, it’s not Chairmanny Impactful, but that's what those awards are, with reason. Shut up and multiple: the math, in the end, is inevitable.

And I’m going to deny it.

There's a story that goes around in the FIRST sphere, where one of FIRST's founders bargained or tricked Coca-Cola into in exchange for developing some other more commercial technology. The exact form and valence tends to vary with who tells the story, whether to highlight the speaker's anti-capitalist frame, to gloss over some of the frustrations with the Coca-Cola Freestyle (tbf, usually more logistic and maintenance than with the pumps themselves), or to wave away the rough question of whether it paid off).

But that last point is a bit unfair: Solving Problems In Extreme Poverty is the sort of difficult and low-odds environment where high-variance options make sense to take, and you should expect a high-variance low-odds option to fail (or at least not succeed wildly) most of the time, and at least it wasn't as dumb an idea as the lifestraw. Maybe (probably!) enough of the steps that combine to keep FIRST running fall into the same category.

I'm hoping teaching kids isn't a low-odds environment. And ultimately, most volunteers and teams and sponsors signed up more for that than for the flashing lights and the fancy banners. But teaching, in matter involving true interaction, can not be done at the scales and directions that turn a roll of the dice from gambling to a variance strategy. It's difficult enough as a mentor to remember all the names the students and family for even a moderately-sized FRC or FTC team; few in a team that "support 128" teams (not linking directly: these are teenagers) can name every one or even a majority. These organizations have, by necessity, turned to maximize how many opportunities they present to their affiliates, without much attention to what that opportunity is. Few turn to the full argumentum ad absurdum where the recruitment exists solely to get more recruiters, but they’ve not left that problem space behind, either.

((There are other nitpicks: the same economies of scale that make these answers work eliminate many less-difficult problem whose presence is necessary to onboard and upskill new learners, the focus on bits over atoms breaks in similar ways that the outreach-vs-teaching one does.))

Dunbar proposed an upper limit to how large a social group the human mind readily handles. There's a lot of !!fun!! questions about how well this will replicate, or how accurate the exact number is, or what applicability it has for a given level of interaction: suffice it to assume some limit exists, that some necessary contact increments the counter at some level of teaching, and that it can't possibly be this high. At some point, you are no longer working with people; you're performing a presentation, and they're watching; or you're giving money and they're shaking a hand. At best, you're delegating.

These strategies exceed the limit, blasting past it or even starting beyond it. They are hyperdunbar, whether trying to get fifty thousand people into a convention center, or trying to sell ten thousand books, or 8k-10k subscribers. There are things that you can't do, or can't do without spending a ton of your own money, without taking these strategies! Whether FIRST getting NI's interest, writing or drawing, building or playing video games full-time, you either take this compromise or another one, and a lot of the others are worse.

But they're simultaneously the most visible strategies, by definition. I do not come to kill the Indigestion Impact Award; I come to raise the things that aren't in the awards. Even if FIRST could support a dozen teams that emphasized bringing new technologies forward in a one-on-one basis, and if your first exposure to the program selected from teams randomly, you'd be much more likely to hear from the hyperdunbarists -- hell, it could well be that way, and I've just missed the rest of them.

Yet they are not the only opportunity. You don't have to be grindmaxxing. One team, even in FIRST, can share skills simply for the purpose of sharing skills. It’s why I volunteer for the org. You can go into an artistic thing knowing you want a tiny audience, or to cover costs and if lucky your time, or as a hobby that's yours first. It shouldn't be necessary to say that outright, as even in hyperdunbar focuses, most fail down to that point. Yet even in spheres where Baumol's hits hardest, it can be a difficult assumption to break.