So they invaded their own internationally recognized territory. Wonderful. By that standard Ukraine invaded Donbass after they declared themselves independent of Ukraine.
>Syria
Even more outlandish claim, considering they were invited by the government. Whether the west considered the government illegitimate or not didn't matter.
>Moldova
>Georgia
in both conflicts in protection of a minority, on whose territory a larger state laid claim using Soviet drawn borders and dissolution of the USSR. Since the Ukrainian conflict started I observed lots of enthusiasm for Soviet borders on the side of Russia's detractors, which were often drawn with territories assigned as a form of favoritism, simply because communist leadership in Moscow had better a relationship with the communist leaders of one of the ethnicities in question. That way historic Armenian land of Artsakh was assigned to Azerbaijan for example -- the recent ethnic cleansing outcome of that is well known.
If there had been something like this standardized in Markdown from the start, it might have had a chance for wide adoption. Right now, learning to see and use LaTeX math as easily as more ASCII-like notation is just more convenient since it is widely adopted (in GitHub, in VS Code, etc.). It's harder, but it also provides the added benefit of maintaining your LaTeX skills.
I think Google's Chrome team's choices of priorities bear a significant portion of the blame for this. They refused to implement MathML for the longest time, and even when it was implemented, it was partly done and financed by a third party. Without MathML, LaTeX-to-HTML JavaScript hacks became the norm, solidifying LaTeX as the standard even for non-typesetting use cases. Had MathML been implemented by Chrome early on, a more direct and easier translation from something ASCII-like to MathML would likely have been adopted.
Its funny I started writing this tool over 10 years ago (show HN from March 2015 https://news.ycombinator.com/item?id=9235139) where I intended it to be used in Markdown. AsciiMath proper back then (just like AsciiMath today) didn’t compile to MathML so I was forced to write my own
I'd happily never customize a theme again if there were any other easy way to actually pick the background and foreground colors on all of my apps. I like having white text on a black background, not a "dark" gray background and white text (and certainly not some off-white background with some dark but not fully black text, which I find even worse than just a typical black text on white background theme). I'm well aware of the fact that it probably does nothing in terms of actually affecting the battery life of my devices, and that dark gray is considered "better" from design perspective, but I don't care, because I happen to like the way the color scheme I describe looks, and I don't see why it should matter whether it does to anyone else if it's just going to be on a device that I'm the only one who ever uses. For whatever reason, this is next to impossible to do without rolling my own GTK theme (not even just using one that someone else had made, because I literally couldn't find one that just changed the background to black without having a bunch of other opinionated decisions on icons and padding and stuff), so that's what I do. I'm grateful that this is even possible though, because apps that aren't GTK (or Qt, which is also possible to theme) often don't provide any ability to theme whatsoever. With the exception of coding editors, I'm not sure I've ever found an Electron app that actually lets me pick a fully black background color, so despite not being particularly dogmatic in my opposition to them, I always try to run stuff like Slack and Discord in the browser so I can theme them with custom CSS. (I'm vaguely aware that this might be possible to do with the electron apps as well by running in some sort of developer mode, but I can't be bothered to spend a bunch of time trying to replicate what I already have working in the browser for their sites).
Expressing their argument as "don't use custom themes" just makes it less convincing when there aren't really any other easy ways to get the flexibility from them that doesn't cause any of the issues they cite. It would be like finding out that a friend or relative uses the same password for every site, and then trying to get to them to install a package manager by uninstalling Windows and switching to Linux at the same time. Mixing together subjective personal preferences with objective technical advice just dilutes the latter to the point where it's impossible to find it compelling.
I hadn't heard of this, but from googling, if you mean this (https://www.omglinux.com/gnome-accent-colors-are-coming/), that doesn't seem to do what I want. It doesn't affect the background color, and it hard-codes a list of colors that don't include what I want as my background color anyhow, so it wouldn't help me even if it did.
Open source is about taking back control over your software. The sentiment of that website is absurd to me. What I do on/to my own system is nobody else's business. (Though I don't really change much of the theming myself. Changed a few colors slightly and of course the desktop wallpaper.)
The sentiment still stands. I can't fault distros from wanting to theme their distro to match their branding. Like, Ubuntu wouldn't be Ubuntu without their signature orange and aubergine colors, Mint and openSUSE have their greens, and SteamOS' have their polished Vapor theme etc. And as an end user and a perpetual distro-hopper, I really appreciate that. I like the consistency that well-made distro themes provide, plus it makes you feel like you're actually using that distro, as opposed to some generic Linux with a vanilla GNOME/KDE shell on top.
Sounds fine to me, but these applications are already open source. If you're going to modify and repackage them, at least update the links to the bug tracker to your own.
The consistency is nice and all, but more than once have I seen distro replace a "stop" button with something they deemed similar enough that didn't make any sense in several applications that used them. I've also seen themes mess with spacing, hiding button rows or stretching them in weird ways. On a glance it all looks nice, but when you're using them applications look weird and broken.
Themes are nice, but unless there's an official theming feature (like with the new Gnome accent colours) it's the duty of a distro to inform their users that theme related UI glitches are the distro's fault, and I have seen none of them bother to communicate that.
In the mid 2000's, I loved trying different themes. These days I just take whatever is the default for Gnome, which is remarkably sane, usually more comfortable than a Mac, and consistent.
Some themes solve real problems, especially for the visually impaired, but that's not the norm. It's a fun work of art, but the utility is always limited. More often than I like to admit, I was left with a broken desktop after attempting to uninstall a theme that didn't work well enough (or at all), and that couldn't be fixed by installing another on top of it.
There are more pressing issues in Gnome than to provide a stable theme API.
Servers with NVIDIA H200 GPUs (Supermicro ones for example) have power supplies that have 54 volt rail, since that gpu requires it. I can easily imagine a premium ATX (non-mandatory, optional) variant that has higher voltage rail for people with powerful GPUs. Additional cost shouldn't be an issue considering top level GPUs that would need such rail cost absurd money nowadays.
A server is not a personal computer. We are talking about enthusiast GPUs here who will install these components into their existing setup whereas servers are usually sold as a unit including the power supply.
> Additional cost shouldn't be an issue considering top level GPUs that would need such rail cost absurd money nowadays.
Bold of you to assume that Nvidia would be willing to cut into its margin to provide an optional feature with no marketable benefit other than electrical safety.
>Nvidia would be willing to cut into its margin to provide
Why would that be optional on a top of the line GPU that requires it? NVIDIA has nothing to do with it. I'm talking about defining an extended ATX standard, that covers PSUs, and it would be optional in the product lines of PSU manufacturers. The 12VHPWR connector support in PSUs is already a premium thing, they just didn't go far enough.
>What does this have to do with the First Amendment?
Because obviously changing the owner-editor of a media outlet has everything to do with their editorial policy. The SCOTUS just said that censorship is ok (and forcing the change of the editor is censorship, there is no doubt about it), as long as it's against another state's editorial preferences potentially having a significant audience in the country.
The government doesn't care about the editorial policy so long as if it's not managed by a foreign adversary or proxies of a foreign adversary, which obviously fall out of scope of the First Amendment. This is consistent with the wholly uncontroversial indictments of the owners of Tenet Media who allegedly conspired with Russia. Meanwhile, the commentators on the channel, such as Tim Pool and Dave Rubin, claimed to have had full editorial control over their content that just so happened to align exactly with Russian propaganda, yet they were free to go.
>which obviously fall out of scope of the First Amendment.
It obviously doesn't. That would mean the US Government can ban all foreign press, just by designating countries as "foreign adversaries". And "foreign adversaries" is a euphemism for "countries that don't submit". The SCOTUS just invented another exception to the absolutist interpretation.
>wholly uncontroversial indictments of the owners of Tenet Media
>were charged with failing to register as a foreign agent
This entire narrative together with the banning of Tiktok is wholly hypocritical, given the American media, tech, and NGO's influence/dominance around the world.
The moment someone achieved what the American entities have been doing around the world, the non-stop wailing of "foreign adversaries this, foreign adversaries that" started.
Meanwhile in Georgia, a country bordering Russia, the law requiring foreign-financed NGOs to register was declared to "stigmatize organizations that serve the citizens of Georgia" with accompanying travel bans for the authoritarian evil doers who passed said law by the US state department.
Tiktok algorithms could be considered a form of editorial position(be it foreign government influenced one, or just the type of content they elevate / not remove), and in this sense it is similar to banning a newspaper(which would obviously be censorship) -- journalists could publish in other newspapers. Therefore banning TikTok absolutely is censorship.
>This isn't like China where the government bans any services they can't control
This is literally like this, and done precisely due to the lack of control due to the illegality of overt/direct speech regulation, and the fears that China would elevate content that isn't in the interest of the US in the broadest sense, but that is still legal according to the 1st amendment. The US Government has tremendously more influence on the local/western platforms, and on people who work there. (There is already an appeals court decision about Biden administration overstepping in communicating with online platforms about what content they don't like). The logic goes "We can't regulate speech like we want to, order what we like and what we don't like, but at least we can remove/censor individual owner-editors that we suspect might harbor some harmful intentions. That means no owners from 'evil' countries". That's about it.
It's censorship and also import controls and also turning off one propaganda faucet.
> On December 6, 2024, a panel of judges on the U.S. District of Columbia Circuit Court of Appeals unanimously rejected the company's claims about the constitutionality of the law and upheld it.
>Rust does not have a culture of "microdependencies"
It absolutely does by the C/C++ standards. Last time I checked the zed editor had 1000+ dependencies. That amount of crates usually results in at least 300-400 separately maintained projects by running 'cargo supply-chain'. This is an absurd number.
Some amount of the risk from the "dependency jungle" situation could be alleviated by instituting "trusted" set of crates that are selected based on some popularity threshold, and with a rolling-release linux-distro-like stabilization chain, graduating from "testing" to "stable". If the Rust Foundation raised more money from the large companies, and hired devs to work as additional maintainers for these key crates, adding their signed-offs, it would be highly beneficial. That would have been a naturally evolving and changing equivalent to an extensive standard library. Mandating at least two maintainer sign offs for such critical set of crates would have been a good policy. Instead the large companies that use rust prefer to vet the crates on their own individually, duplicating the work the other companies do.
The fact that nothing has changed in the NPM and Python worlds indicates that market forces pressure the decision makers to prefer the more risky approach, which prioritizes growth and fast iteration.
It's somewhat similar to 'recoll' in its functionality, only with recoll you need to index everything before search. It even uses the same approach of using third-party software like poppler for extracting the contents.
By the way Recoll also has a utility named rclgrep which is an index-less search. It does everything that Recoll can do which can reasonably done without an index (e.g.: no proximity search, no stem expansion etc.). It will search all file types supported by Recoll, including embedded documents (email attachments, archive members, etc.). It is not built or distributed by default, because I think that building an index is a better approach, but it's in the source tar distribution and can be built with -Drclgrep=true. Disclosure: I am the Recoll developper.
Wow this is a gem of a comment. I use Recoll heavily, it's a real super power for an academic, but I had no idea about rclgrep. Thank you for all your work.
What rclgrep does is run the recoll text extraction and do a grep-like operation on the extracted texts. If you want to give it a try, don't hesitate to contact me if you have any trouble building or using it, or think it could be improved. It's more or less a (working) prototype at the moment, but I'm willing to expand it if it looks useful. The "Usage" string is much better in the latest git source than in the tar, and it sorely needs a man page.
I think an index of all documents (including the contained text etc) should be a standardized component / API of every modern OS. Windows has had one since Vista (no idea about the API though), Spotlight has been a part of OS X for two decades, and there are various solutions for Linux & friends; however as far as I can tell there's no cross-platform wrapper that would make any or all of these easy to integrate with e.g. your IDE. That would be cool to have.
So they invaded their own internationally recognized territory. Wonderful. By that standard Ukraine invaded Donbass after they declared themselves independent of Ukraine.
>Syria
Even more outlandish claim, considering they were invited by the government. Whether the west considered the government illegitimate or not didn't matter.
>Moldova >Georgia
in both conflicts in protection of a minority, on whose territory a larger state laid claim using Soviet drawn borders and dissolution of the USSR. Since the Ukrainian conflict started I observed lots of enthusiasm for Soviet borders on the side of Russia's detractors, which were often drawn with territories assigned as a form of favoritism, simply because communist leadership in Moscow had better a relationship with the communist leaders of one of the ethnicities in question. That way historic Armenian land of Artsakh was assigned to Azerbaijan for example -- the recent ethnic cleansing outcome of that is well known.
reply