How can wifi be a star topology when all clients connect to the base station using the same airwaves? If it really were a star topology, it would also not be possible to use aircrack-ng or other tools to gather data for WPA cracking by passive listening -- that can only happen on a shared medium network.
I think the most accurate classification is that wifi emulates a star topology at OSI layer 2 on top of a layer 1 bus topology.
> it was designed in 1998 by networking gear companies
That's false. Firstly, rfc1883 was published in 1995 which means work started some time before that, and the RFC process included operating system vendors and RIR administrators. The primary author of rfc1883 worked at Xerox Parc, and the primary author of rfc1885 worked at DEC. Neither were networking gear companies.
No, I think proposed, draft and internet standard all have specific meanings we don't need to debate over. Your claim that IPv6 was first proposed in 1995 is correct, as is my claim that it was first accepted in 1998. No one actually uses a proposed standard, but when it is draft people start implementing it and giving feedback over issues until it is fully ratified is my understanding (correct me if that's wrong please).
Maybe if we'll get rack-sized fusion reactors out of it, I will consider the AI/Datacenter spending craze in the same light as NASA projects. Until then, they are rich kids' vanity projects and nothing more.
The UAE doesn't have a self-advancement culture, it's a capital-backed monarchy that imports pretty much all of its research and production; in other words it piggy-backs on the knowledge produced in other societies. There is no advancement through dialog in the country itself.
Everything in the UAE is about being perfect. It's part and parcel of Arab culture, especially for the Gulf Arabs. Nope, we can't do any wrong, we're excellent individuals, we're an exceptional society, we're a remarkable nation. Every business deal is a fruitful deal, every investment is a multibagger investment, every project is a successful project, every Emirati/Gulf Arab professional is infallible. Normie government bureaucrats are addressed as "His/Her Excellency" even.
In such an environment, don't expect any introspection into failures or any risk-taking capacity. Because everything has to be perfect.
Dubai at least took a beating in 2008, and has since taken a more cautious and guarded approach than before. Abu Dhabi, Doha and Riyadh continue to take very cavalier attitudes - they're all ah so very perfect.
It's not just the UAE, it's pretty much all of the Gulf states. They're essentially a less obviously extreme version of Turkmenistan, or something like late-1930s Germany where everything looks prosperous and OK provided you walk very carefully and don't see some of the things that are happening.
Ukraine does it to avoid assisting Russian damage assessment and targeting efforts. Avoiding embarrassment is not really part of the equation, especially when they need to push for more international support.
They want to make it so Iran doesn’t know if they successfully hit that Oracle data centre.
But they also want to make it so foreign investors don’t get scared off by the prospect of their data centre getting blown up. Obviously investors will avoid the area so long as missiles are flying - but by coming through the conflict "unscathed" will let them bounce back fast. Likewise with tourism.
Which of these is the bigger motivation? Hard to say. But I gather most drones have cameras, so I imagine Iran have a pretty good idea of where their drones are striking.
They are more likely to get funding from EU if they can make it look like they can win the war.
Which of these is the bigger motivation? Hard to say. But I gather most drones have cameras, so I imagine Russia has a pretty good idea of where their drones are striking.
I think the main EU fear is ex-soviet countries fearing they are next if Ukraine falls. So Ukraine should not necessary win, it should mainly bleed Russia and not loose. An eternal standstill is probably best, realpolitik-wise (To be clear, I am not happy with this analysis).
True. As far as EU BigPowers are concerned, they know Ukraine has lost the war but don't really care if Ukraine is being destroyed and Ukranians are dying, as long as they kill as many Russians too.
It astounds me that even in 2026 people are still regurgitating this standard-issue Russian propaganda canard about "Ukraine already lost the war", consciously or subconsciously. While the war is going on, you can make equally vacuous claims that "Russia already lost the war" with about as much cause.
Ukraine is fighting for its survival against a fascist and colonialist invader that aims to end its nationhood. The final outcome is unclear.
The real tragedy is that intelligent people like you buy the EU propaganda that "Ukraine is winning this war" without truly understanding what is happening on the ground.
The stark facts are simple - nearly 20% of Ukranian territory has been strategically captured by the Russians. Ukraine has no real chance of getting it back. Ukraine's counter-offensive has failed twice. It cannot launch any more counter-offensive because it doesn't have the men - any counter-offensive by recalling men from other parts of the frontline would weaken the defence line. So any new counter offensive launched needs to really bloody the Russians to completely back off, or the whole frontline will collapse and Ukraine will face a complete military defeat. Whatever Russian territory Ukraine had occupied has been recovered by the Russians. In case Ukraine doesn't accede to Russian terms, Russia has also been working on a plan B that entails systematically destroying Ukraine's industrial infrastructure (demilitarisation through de-industrialisation - https://politics.stackexchange.com/a/94244 ).
All Ukraine does now is to launch drones and missile attacks at Russian infrastructure for western and social media PR (as it is the only way EU will keep funding Zelensky's government and the war), while it is forced to retreat in the frontlines every week as the Russians slowly keep advancing.
>The real tragedy is that intelligent people like you buy the EU propaganda that "Ukraine is winning this war"
All depends on your victory conditions, tovarish.
>In case Ukraine doesn't accede to Russian terms, Russia has also been working on a plan B that entails systematically destroying Ukraine's industrial infrastructure
You don't seem to be following this war very closely. Short of nukes, Russia has already done everything it possibly can, including trying to freeze old people in their flats during cold snaps, multiple times. They've been targeting industrial infrastructure since day one, but interestingly what's been changing is that Ukraine is increasingly playing that game too, focusing on demilitarizing Russia by targeting its defence industry and increasingly taking its oil exports offline. Turns out two can play this whole de-industrialisation game. It remains to be seen who succeeds, but things aren't looking as good on this front for Russia as they did in 2022 or 2023, that's for sure.
>All Ukraine does now is to launch drones and missile attacks at Russian infrastructure for western and social media PR
Well and also to do things like take 46% of Russia's oil export capacity offline just when oil prices were soaring. You know, small trifles.
>while it is forced to retreat in the frontlines every week as the Russians slowly keep advancing.
Slowly is doing all the heavy lifting here, to borrow a common AI slop refrain. Russia is now losing more men per month than it can recruit, somewhere in the vicinity of 30-40 thousand. Ukraine is extending the drone kill-zone to 30+ km from the so called "front line" (more of a zone). It produces millions of drones and is at the forefront of a drone revolution in warfare. In other words, its demilitarization is progressing swimmingly, but for the minus sign.
> All depends on your victory conditions, tovarish.
The break with factual reality in your post is enlightening. As is the misinformation of Russia "running out of men" when that is the situation Ukraine is facing. There is no "victory", is the point. There is no path to defeating Russia without a nuclear war. That Ukraine can bring about the economic collapse of Russia is a delusional fantasy.
You are just lazily "no u"-ing and projecting at this point, and your uninformed cheerleading of Russian fascism is profoundly uninteresting, so there's nothing further to discuss with you. You're either a Russian Z-bag, or one of those tedious people who make up their minds on a topic they mistakenly think they mastered and then shut themselves off from contrary information. Case in point, the hilarious timing of you saying the Russian economy isn't nearing collapse, when it's one of the main topics of discussion on even on Russian TV and press. Which of course, if you're the second type, you can't watch/read.
What is clear that you have no understanding of either superpower politics, military capabilities or how economies work. You are clearly one of those shameless EU cheerleaders who don't care about Ukrainians getting slaughtered and their country destroyed, as long as they "weaken" Russia in the process.
I don't think Ukraine lost. They surely did a lot better than anyone expected. Right now, I'd say it can go both ways, with Ukranian deaths vs Russian economic crash and hurt for their rich class seeming the main determinaters. If Putin drops dead, if the rich feel enough bombs exploding in Moscow, .... Then Ukraine wins
They have lost depending on the parameters you use to judge the war - I see 20% of Ukraine territory occupied by the Russia, Ukraine having no real military capability to launch an effective counter-offensive (due to lack of manpower), 75% of their industrial infrastructure is destroyed or lost to occupation. They are only surviving and fighting based on the charity of the EU. And their only hope of victory is based on the fantasy that EU is selling them - that once Russian economy collapses, they will "surrender". Even if an economic collapse were to happen in Russia (ala of USSR level), which I don't see happening, Russia will absolutely not end the war in any manner unless their military goals are achieved. Ukraine in NATO means NATO nuclear missile will easily be able to reach Moscow within minutes. Zelensky is a fool to keep ordering strikes deep inside Russia because every successful strike (with unsophisticated drones and ordinary missiles) inside Russia makes the Russians realise how militarily vulnerable they will be Ukraine were to join NATO, and so they will do everything to prevent that. (And let's not forget that Russia is a nuclear power - Ukraine cannot militarily win this war until NATO joins it).
Obviously investors will avoid the area so long as missiles are flying - but by coming through the conflict "unscathed" will let them bounce back fast. Likewise with tourism.
Definitely with tourism. FOAF flew through there a week or two back and said it was very much business as normal at the airport apart from slightly longer queues, otherwise it was the same as it was before the shooting started. This in a country that had been targeted by something like 2,500 dones and 500 missiles.
Its almost like the idea of nations and representative government have been co-opted by sinister forces to advance an agenda that doesn't serve the people.
Perhaps its time humanity evolve beyond this foolishness?
Your first example is a valid uri but not a valid http url, because it's missing a host part. Your second example is not a valid uri, as the spec requires that [scheme]:// is followed by a host indicator.
Neither has much to do with / normalization, which applies to the path part of a valid uri.
Yes, the uri spec must allow the host part to be empty. That's easily shown by remembering that file:/// URIs are commonly preceded by three slashes, so the spec must allow for that. Not sure where the brain was going with that.
> A sender MUST NOT generate an "http" URI with an empty host identifier. A recipient that processes such a URI reference MUST reject it as invalid.
And it really is an empty host component, as RFC3986 section 3.2 specifically says:
> The authority component is preceded by a double slash ("//") and is terminated by the next slash ("/"), question mark ("?"), or number sign ("#") character, or by the end of the URI.
So yes, collapsing all those ////// into two really is illegal according to the spec -- but then again, the specs are mostly about network communication, so machine-to-machine. I consider a browser's url bar parsing to be more in the UX domain than in the technical domain.
The improved register count must make it much less claustrophobic for students. It's not just the same ISA but with wider words.
Looks like I'm mistaken on terminology though. x86 includes the 16-bit, 32-bit, and 64-bit ISAs of that family, and doesn't refer specifically to the 32-bit generation.
> I read the V1 code this time instead of guessing
Does the LLM even keep a (self-accessible) record of previous internal actions to make this assertion believable, or is this yet another confabulation?
No they do not (to be clear, not internal state, just the transcript). It’s entirely role-play. LLM apologies are meaningless because the models are mostly stateless. Every new response is a “what would a helpful assistant with XYZ prior context continue to say?”
Yes, the LLM is able to see the entire prior chat history including tool use. This type of interaction occurs when the LLM fails to read the file, but acts as though it had.
> while providing the minimum of abstraction people wanted
Yes, I think this is key. I wasn't around in 1985, but on every attempt to write something in Ada I've found myself fighting its standard library more than using it. Ada's stdlib is an intersection of common features found in previous century's operating systems, and anything OS-specific or any developments from the last 30 years seem to be conspicuously absent. That wouldn't be so much of a problem if you could just extend the stdlib with OS-specific features, but Ada's abstractions are closed instead of leaky.
I'm sure that this is less of a problem on embedded systems, unikernels or other close-to-hardware software projects where you have more control over the stdlib and runtime; but as much as I like Ada's type system and its tasking model I would never write system applications in Ada because the standard library abstractions just get in the way.
To illustrate what I mean, look at the Ada.Interrupts standard library package [0] for interrupt handling, and how it defines an interrupt handler:
type Parameterless_Handler is
access protected procedure
with Nonblocking => False;
That's sufficient for hardware interrupts: you have an entry point address, and that's it. But on Linux the same package is used for signal handling, and a parameterless procedure is in no way compatible with the rich siginfo_t struct that the kernel offers. To wit, because the handler is parameterless you need to attach a separate handler to each signal to even know which signal was raised. And to add insult to injury, the gnat runtime always spawns a signal handler thread with an empty sigprocmask before entering the main subprogram so it's not possible to use signalfd to work around this issue either.
Ada's stdlib file operations suffer from closed enumerations: the file operations Create and Open take a File_Mode argument, and that argument is defined as [1]:
type File_Mode is (In_File, Inout_File, Out_File); -- for Direct_IO
type File_Mode is (In_File, Out_File, Append_File); -- for Stream_IO
That's it. No provisions for Posix flags like O_CLOEXEC or O_EXCL nor BSD flags like O_EXLOCK, and since enum types are closed in Ada there is no way to add those custom flags either. All modern or OS-specific features like dirfd on Linux or opportunistic locking on Windows are not easily available in Ada because of closed definitions like this.
Another example is GNAT.Sockets (not part of Ada stdlib), which defines these address families and socket types in a closed enum:
type Family_Type is (Family_Inet, Family_Inet6, Family_Unix, Family_Unspec);
type Mode_Type is (Socket_Stream, Socket_Datagram, Socket_Raw);
Want to use AF_ALG or AF_KEY for secure cryptographic operations, or perhaps SOCK_SEQPACKET or a SOL_BLUETOOTH socket? Better prepare to write your own Ada sockets library first.
To be fair, the file-handling is probably the 'crustiest' part of the standard library. (To use the posix-flags, you use the Form parameter.)
The best way to use Ada, IMO, is type-first: you define your problem-space in the type-system, then use that to solve your problem. -- Also, because Ada's foreign-function interface is dead easy, you could use imports to handle things in a manner more amiable to your needs/preferences, it's as simple as:
Function Example (X : Interfaces.Unsigned_16) return Boolean
with Import, Convention => COBOL, Link_Name => "xmpl16";
Yes, agreed on Ada.Interfaces and the FFI, it's one of the best. The only thing "missing" is auto-import of the definitions in C header files (but there be different dragons). gcc -fdump-ada-specs works fine, but it's effectively a duplication of (non-authoritative) information. That's fine if you're targeting one system, but when targeting multiple systems a single "with Interfaces.C.Syscall_H" quickly becomes a maze of alternative package bodies and accompanying conditional compilation logic.
> The best way to use Ada, IMO, is type-first: you define your problem-space in the type-system, then use that to solve your problem
I guess that goes to the core of the argument I was trying to make: not that Ada is bad, but that the low-level abstractions in Ada's stdlib are a case of premature optimization. Luckily, I take much less issue with the Numerics and Container parts of the standard library.
> To use the posix-flags, you use the Form parameter
Do you have any examples/documentation on the use of the Form parameter? According to the RM, it's a String argument so I wouldn't have expected it to support flags.
(Also, to correct myself on the signalfd issue: there is GNAT.Signals.Block_Signal to mask signals on the Interrupt_Manager thread)
Ada.Text_IO.Create (
File => File,
Mode => Ada.Text_IO.Out_File,
Name => "test.txt",
Form => "shared=no"
);
The "maze of alternative package bodies and accompanying conditional compilation logic" is an artifact of C's approach to 'portability' using the preprocessor. Typically, the conditionality should be stable once you abstract it (using the compiler's project-management to select the correct body for a particular configuration) -- As a stupidly trivial example, consider the path separator, for the specification you could have:
Package Dependency is
Package OS is
Function Separator return String;
End OS;
End Dependency;
-- ...
Package Dependency is
Package body OS is separate;
End Dependency;
-- Windows
separate (Dependency)
Package OS is
Function Separator return String is ("\");
End OS;
-- Classic Mac
separate (Dependency)
Package OS is
Function Separator return String is (":");
End OS;
-- VMS
separate (Dependency)
Package OS is
Function Separator return String is (".");
End OS;
-- UNIX-like
separate (Dependency)
Package OS is
Function Separator return String is ("/");
End OS;
Then in your the rest of your program, you program against the abstraction of DEPENDENCY.OS (and whatever other dependencies you have, likewise), and thus separate out the implementation dependency.
I think the most accurate classification is that wifi emulates a star topology at OSI layer 2 on top of a layer 1 bus topology.
reply