The host sets up a GATT server and the other players have a client role.
The other option was setting up a game via whatever WiFi network was available, but many hotspots now restrict peer to peer access. For cross platform support, iOS doesn't allow local hotspot creation (which could have been an alternative) even thought Android does. Bluetooth was the option that all platforms could support without having to deal with third party WiFi.
As a regulatory decision, this isn't about protecting the consumer. It's about preventing an externality being handled by all of society, specifically reducing e-waste.
It's interesting to read that an entire video streaming rework was done with AI, but likely won't be upstreamed because of the upstream policy on AI gen code. I wonder if that will ever be re-done using the plan GE outlined in the release notes.
Also really excited about this because there are several games that get kind of borked because they get stuck on an intro video before you get to the game menu without doing any winetricks.
> With all of that work done, I am happy to say all of the games listed above now have functional video playback with NO winetricks needed and NO dll overrides needed. No quartz,no dshow, no amstream, no lavfilters, no klite, no rsx3d, no wmp9, no wmp11, etc. -- All the functionality previously needed from those overrides is now patched directly into wine for the listed games that needed them, and the protonfixes that were previously added have now been removed since they are no longer needed.
It might come to be that maintainers have to begin accepting llm-authored or llm-assisted contributions just to maintain control of the project. Otherwise users will gravitate towards forks that offer the functionality they want.
They very specifically do not accept AI contributions because there is no way to tell if it's just regurgitating parts of the various Windows source code leaks from over the years ad-hoc, which would be a very costly mistake to make if Microsoft were feeling litigious.
The remedy for unintentional infringement is generally to remove the infringing code and cease distribution. That used to be a serious issue when rewriting the offending code might take years. But these days? Rewriting any offending code is a matter of specifying the interfaces and setting Claude / Codex to work. Risk of incorporating derived code might go up with accepting LLM submissions, but cost of recovering from them seems to have dropped accordingly, at least on the technical side.
Perhaps you've never maintained any serious open source software. A line-by-line source code audit for license compliance including some ripping-out and re-writing of non-compliant code was the first thing I did when taking over maintainership of Repsnapper nearly 20 years ago. Was required to get it into Fedora. I don't see how the presence of LLM generated code changes that kind of work at all.
That would be something Microsoft would have to prove in court and not that the AI came up with a similar approach on its own. ReactOS never got sued despite its similarity to Window's code.
Also not all Wine code is related to reverse engineering.
Or it might come to be that rejecting LLM-authored or LLM-assisted contributions becomes a badge of quality, and users gravitate to them to avoid buggy, inconsistent, or non-performant versions of the same software.
There's no need to guess, the reasoning is clearly laid out:
“Don't use an LLM tool to generate code. There's no guarantee
that the training material of that LLM respects our Clean Room
Guidelines, or that its output is compatible with the LGPL.”
Doesn't wine have various rules to remain a white-room implementation?
Not sure using LLMs which have possibly been trained on leaked Windows sources would be compatible with that. But that's just speculation, I wonder if LLMs possibly using leaked sources for training has been looked into. (probably legally difficult as the investigator would have to access the leaked sources too...)
Not sure if those fork would be maintainable long term if their authors need to lean so heavily on LLMs just to get their coding done. Would bet more on the original project that have demonstrated they know what they are doing & can do the work by themselves (if at more realistic pace).
Unfortunately, it's my first time using the discount code, and I didn't realize it required in-app code to enable it. There is a new build that should now have the discount. I will extend it another week.
I like the trial idea. Will see if I can get that out quickly.
Onboarding on the custom API is very tedious (I used openrouter: took me 20 minutes to guess the URL and model format you expected, full of 404 and 200 errors).
I added the model, connection test worked, I added all the requested permission and set Aide to be default assistant, but unfortunately after tapping a microphone I get "Client-side error", and after asking it via text something super basic (eg: "what's the time now") it responded with "Provider error".
I'll probably try tomorrow with my local model so I can have full visibility of the traffic because frankly the app doesn't help much :)
Missed the window for edit: I agree that ideally I'd have a tiny local MOE-kind of model, able to establish the complexity of the request, route simple local requests to the instantly available local agent, and route all the rest outside (to one of several models).
Even if you believe the previous administration switching fonts was virtue signaling, then by the same logic you have to also believe this is just virtue signalling.
Just guessing from what is written in the article: Calibri once was chosen by the former administration for accessibility reasons. Maybe the virtue signaling being that Calibri isn't great with respect to accessibility (and IMHO wasn't even designed for it in the first place).
> fonts like Times New Roman have serifs ("wings" and "feet") or decorative, angular features that can introduce accessibility issues for individuals with disabilities who use Optical Character Recognition technology or screen readers. It can also cause visual recognition issues for individuals with learning disabilities.
> On January 4, 2023, in support of the Department's iCount Campaign on disability inclusion (reftels), Secretary Blinken directed the Department to use a more accessible font. Calibri has no wings and feet and is the default font in Microsoft products and was recommended as an accessibility best practice by the Secretary's Office of Diversity and Inclusion in collaboration with the Executive Secretariat and the Bureau of Global Talent Management's Office of Accessibility and Accommodations.
In 2023, the US State Department signalled how virtuous it was, by moving from the previously-default MS Office font to the then-currently-default MS Office font. The current MS Office default font is Aptos, place your bets on what the State Department is going to switch the font to in 3 years time.
As far as I know, font choice has no zero effect on screen readers, which ask compatible software what words are on screen and read them out. There is evidence that serifs cause visual recognition issues for some individuals, but there's also evidence they aid recognition for different individuals.
It probably helped everyone to choose 14pt Calibri over 12pt Times New Roman, as the font is more legible on LCD screens.
The virtue being signalled by the current administration is that everything their predecessors did was wrong and they're literally going to reverse everything out of sheer pettiness. If anything, they should acknowledge the president's long friendship with Epstein and pick Gill Sans as the default. That would be the ultimate "anti-woke" move I think.
Calibri is a Sans Serif font and because it has been the default Microsoft Office font for more than a decade, it is fake email job haver coded (i.e. it appeals to young and middle-aged women who work in HR, this demographic being predominantly Democrat). Times New Roman is a Serif font which looks old and official to cater to boomers and has Roman in it to appeal to Zoomers who want to RETVRN with a V to tradition.
(I didn’t read the article as this is a non-story, but I’m definitely right).
Yep, I've seen what craziness happens when the admin is woke, and I've seen the craziness when it's "anti-woke" and I preferred woke. At least woke didn't kidnap people into unmarked vans for writing a college newspaper article. I don't agree with woke, but they won't send me to Guatemala torture prison bc I don't agree
There's a reason Star Trek teleporters have a "Heisenberg compensator", we cannot record both the position and momentum of a particle precisely. Scanning the "configuration of particles" to transmit to this theoretical printer is the first impossible roadblock. The human you scan can never be the same exact person printed.
The reason Trek has it is likely a common misunderstanding of QM: it's not only that we cannot record both position and momentum, the information does not exist in the first place.
TLDW: an infinitely long wave does not (cannot) have any definite location, but it does have a definite periodic wavelength; conversely, a single impulse noise (a shockwave from e.g. a bullet or an explosion) has a definite location (in the direction of motion and at any given point in time) but no meaningful wavelength.
The more you constrain the possibility space of one, the looser the other becomes in a physical sense, not just the information you have about it.
That said, we definitely don't have the means to 3D print even relatively simple tissues, last I checked we are still limited to structures thin enough to be kept alive by oxygen diffusion.
One of my open questions on this topic is: given we can cryopreserve small tissue without the freezing-damage problem, why can't we do a repeated process of:
1. cell culture tissue sheets that are ~1mm (or whatever) thick
2. cryopreserve each sheet
3. then assemble those sheets, still frozen
4. then thaw out as per normal procedure for cryopreserved organs
Caveat: I have minimal knowledge of biology, this may be a stupid idea for a whole bunch of reasons I don't even know the names of.
Simulations still need to run on something & need energy to power them. The better, more stable, higher fidelity simulation you want, the more mass & energy it will need. And that needs to come from somewhere - a thing many infomorphs tend to conveniently forget far too often.
To the extent what they’re suggesting isn’t bunk, it’s in being able to transmit genetic information and then print it to a womb. Then have a generation of psychopaths raised by a robot.
As with many topics, the Orions Arm Universe project has you covered - the Engenerator[0]!
Originally developed in-universe when a bunch of immortal cyborgs got bored on a colonization ship & decided to instruct a precursor probe to print a machine that prints a machine that will print their bodies on site. :)
The engenerator technology is completely safe[1] and can't be misused in any way.
The other option was setting up a game via whatever WiFi network was available, but many hotspots now restrict peer to peer access. For cross platform support, iOS doesn't allow local hotspot creation (which could have been an alternative) even thought Android does. Bluetooth was the option that all platforms could support without having to deal with third party WiFi.