iwd is dead

[inffy]

Intel has killed IWD development. We still have the ujust in our scripts.

What should we do about it. Plainly removing it would be pretty much a no-go as there might be some users that have switched to it and then they would have no easy way back.

Think bazzite did some kind service or script that will move users back to wpa_supplicant, not sure how well it has worked and its another failure point.

[renner0e]

This would lead to "all of a sudden my wifi networks got reset" right? Is there a way to avoid that somehow?

Do you mean also removing iwd from the image?

I presume #240 sparked this.

[inffy]

yes, the issue here is that if we do something like bazzite did, those wifi connections would be dropped and they would need to reauthenticate.

[renner0e]

It was opt-in for us so the people that are using iwd are probably in the low single digit percentage.

We could do this in the following stages/my thoughts on it:

• only warn if iwd is used with a notification, inform when the automatic switchover happens, link to some thing that explains this situation, some hardware only works with iwd, tell user how to switch now, tell them their network connections "break"
• after a couple months, automatically switch back to wpa_supplicant (remove iwd package, just recipe)

If we decide to do it this way I'd suggest an accompanied blog post regarding the handling of that.

The service should be straightforward, it is just removing/checking for a single file.

We could avoid most of the pains by figuring out how to not break the connections or immediately connecting to whatever we were connecting to before? Can we get the password (...) and do that step for the user?

I'm saying that the more boxes we tick here the better probably