Iced is desktop and web only.
Slint for mobile is WIP for Android and not started for IOS.

https://github.com/slint-ui/slint/issues/46

For Flutter there’s also flutter_rust_bridge. But for Kotlin it’s pretty much the best you have without having to write your own bindings from scratch, alternatively there’s uniffi-rs but it can be tricky to get working with kotlin.

No full Rust toolkit exists yet, best you got is Kotlin-Rust & Flutterust.

You need to learn the definition of “endorses”.

Just admit there wasn’t a joke and you’re trying to backpedal.

Your point is void as the US government is not a single massive entity you can generalize. They’re are a plethora of different, separated branches, departments and offices each operating independently with their own unique functions, values, regulations, practices, etc.

All you’ve done here is presented a hyper-generalized claim as if all of the government enforces and endorses this practices while providing a single cherry picked counterexample without even knowing the actual reason why they use this practice to begin with or providing evidence of them endorsing the practice despite me asking you to do so.

The fact of the matter is the vast majority of US government entities do not have any such practice and there’s no evidence of your provided counterexample actually endorsing others to do the same let alone any other branches or departments. If you have evidence, I again ask you to provide it.

Metaphorically speaking, this is like judging a library’s entire collection based on a single book. Just as a library houses a multitude of books with different themes and purposes, the government comprises diverse entities with unique practices and reasons for their operational procedures. Making sweeping generalizations without considering the individual nuances of each entity is like judging an entire library by a single book on its shelf.

My entire point is that the SSA website inexplicably has operating hours. Those hours are posted on their website. That’s all.

Yes, but that has little to do with your initial claim which is my point.
Additionally, the White House does not control social security services.

If you’re unable to understand what I’ve written here, then just say that. There’s no need to be accusatory because what I’ve stated is contrary to your claim.

No. It’s does make sense, as cases of attacks outside of business hours are harder to deal with because employees are off work. This is further supported by the fact that cybercriminals target websites most especially during off hours and holidays as it buys them more time before they’re discovered. Turning off the servers outside of business hours would effectively prevent this attack vector, at the cost of profit margins.

Most businesses understand that this is a vulnerable period of time and is why most of them mandate that their IT & cybersecurity professionals must stay on call even if they’re taking time off.

I’m unable to find a source that supports the claim that the Social Security Administration states that “websites need to shut down outside of business hours”, please provide one.

The operational hours for the CBSV application and web services provided by the Social Security Administration are clearly outlined, indicating specific times when services are operational, including weekends and evenings. While software maintenance may occur on weekends, there is no indication that they encourage or mandate websites to shutdown outside of business hours as a standard practice; source.
Additionally, the Social Security Administration emphasizes that many services are available online and over the phone, even if local offices and the federal site are closed, highlighting the accessibility of online & offline services for individuals needing assistance; source.
The message on the “my Social Security” update page confirms that all services are currently available, with any planned maintenance activities or temporary issues being transparently communicated to users.

Therefore, while they have their own operational hours, there are a plethora of other services outside of the federally owned website including websites for local offices* and there’s no indication that the Social Security Administration mandates or advises other websites controlled by local offices to shut down outside of business hours, let alone any other branch of the US government.
In conclusion, you’re hyper-generalizing based on the practice of a single cherry picked department, in addition you have no knowledge on the actual reason they have operational hours in place to begin with and are speculating on pure assumption that it’s for security purposes when it could just be a matter of ensuring control without having to go through the usual red tape.

*(Local Social Security Offices don’t typically have their own separate websites but they can, the LSSO I use just so happens to be one of the few that do as they service a very large amount of people at any given time and are constantly short on staff.)

I mean cybersecurity wise it makes sense…
But business profit wise it makes no sense at all.
Also I’m not able to find a source of the white house saying that, please provide a source.

Sudo is for getting the necessary perms to write the data to the location after the > operator. Cat is just super fast, faster than dd infact as it’s not actually intended to write to disks, only to stout. We want as much speed as possible to do as much damage as possible by increasing our chances of trigging bugs.

/dev/urandom provides an unlimited stream of random data, the output is based on truly random data and doesn’t block regardless if the entropy pool is depleted.
It’s not the same as /dev/random which only returns random numbers from the entropy pool at a limited rate and can block if the entropy pool is deplete.

By using /dev/urandom and cat we’re blasting random data at much faster speeds then what /dev/random & dd are capable of which increases our chances of triggering a bug by quite a bit.

It blasts all virtual device files that directly represent the hardware of the system; from disks to audio devices and so on; with extremely random data potentially causing irreversible damage.

sudo cat /dev/urandom > /dev/*
Or
sudo dd if=/dev/urandom of=/dev/sda bs=4k conv=notrunc,noerror

P.s. sudo cat /dev/urandom > /dev/* can cause physical damage to all hardware components, not just destroy your drives data.

sudo cat /dev/urandom > /dev/sda*

&ersand;

Bevy is too new; the ecosystem needs to mature big time.
If you’re building anything with Bevy you should do so with the mind set of upstreaming as much as you can to help it grow.
It’s entirely possible to finish a project in Bevy but you’d have to plan as much as you can before hand and focus purely on that, avoiding scope creep as much as possible.
Godot is essentially a finished product, but Bevy still has a long way to go.