I can't use my #laptop onboard #intel #wifi #iwlwifi as an access point using #hostapd for #rdex after all:

```
iw list | grep "Supported interface modes" -A 8
```
does not list "AP" :(

Would have saved me literally hours if this had been the first line of the guides - "first check that it's possible".

The spare USB dongle I have is not supported by Linux, apparently the chipset is supported via #ndiswrapper but I'm not keen, just so much easier to use an old ADSL router to host the wifi...

#rdex server from almost a decade ago works with two small changes:

in `rdex.wsgi` replace
```import Image```
with
```from PIL import Image```

in `/etc/systemd/system/multi-user.target.wants/mysql.service` add `--thread_stack=1048576` to the `ExecStart` command (it is no longer supported as a configuration file option it seems...)

need to tweak the client at some point, it's saving a lot of uninteresting images, not sure why...

#rdex

I resumed work recently on my reaction-diffusion explorer #audiovisual stuff (project started 2008 or so).

Minor improvements to the #opengl #graphics code, mainly using texture arrays instead of separate textures or atlases, which as a bonus allows mipmaps to be used too for much smoother appearance.

I also added an #OSS backend to the #audio code, because #JACK really dislikes my laptop's onboard sound card, xruns all over. OSS works fine at similar latencies.

Next steps include getting the rdex-server side of things running again (probably need to port from #Python 2 to Python 3, and #MySQL has been replaced by #MariaDB in #Debian I think).

Followed by setting up a WIFI hotspot from the machine's card with captive portal to the rdex-server website, and an Android app to access it in fullscreen (because the browser UI adds unsightly scrollbars that aren't necessary if the address bar is hidden).

https://rdex.mathr.co.uk
https://code.mathr.co.uk/rdex-client/shortlog/refs/heads/2.devel