As of June 8, 2023, WPSD is offered in three disk image “flavors”/platforms: Raspberry Pi, OrangePi Zero, and NanoPi NEO. As we acquire alternative platforms to develop and test against, we release official images for them.
Recently some unofficial/unsanctioned (“forked”) disk images and code repositories of WPSD started appearing in the wild, specifically for the BananaPi platform, and possibly other platforms.
Additionally, there are some creators / vendors of hotpots, shipping their BananaPi and other hotspots with these unsanctioned disk images/software, which is actually not good for the user; and we also do not support the software on these hotspots.
Hints: if you ever see my code on GitHub, it’s not mine - I don’t host the
official code there and I never have; and we also don’t have BananaPi official
disk images released. Also, if you downloaded a disk image from a domain other
m17labs.org, it’s not an official WPSD disk image.
IMPORTANT: These are not official WPSD project images / software, and we do not support them (more on this later).
There are quite a few issues with these disk images and non-official software I will lay out for you:
The unofficial disk images are HUGE. As in the order of 7+GB. This is indicative of a poorly-created / manually-created disk image, and a poor disk image-creation process.
The base operating system used in some of these unofficial disk images are based on the 2017 Debian upstream version 9.x (code-name: “Stretch”), and has been end-of-life since 2020. That means no security or other updates have been available since July of 2020. WPSD has deliberately never supported Stretch. Read: It’s incredibly old, it’s unsupported and severely outdated.
The unofficial disk images and vendor hotspots with the unofficial software are using severely outdated WPSD code. WPSD is a rolling release/continuous delivery software; which means updates are frequent and rapid. As of this writing, the unofficial disk images are using code from approximately 8 months ago (this is considered “old code”). So old, that…
Because of #3, users of unsanctioned disk image/software are unable to keep up-to-date due to the code and infrastructure changes we made about 6 months ago.
While I and my small team of developers and contributors are rabid Open Source advocates (which is why all my code is open), and we encourage improvement, innovation etc.; there are some back-end things that exist and work behind the scenes of WPSD in order to keep it up-to-date and maintain a properly-working system. And these processes and infrastructure components are not open, for reliability and security reasons.
Example, when you run a manual update or your hotspot updates nightly automatically, how and where does this happen? It happens from my servers; which contain lots of back-end code, host and ID file generation tasks, etc. Guess who pays for this? I do and my sponsor(s) do.
So what this means, is that all of these unofficial WPSD images and software installations are pointing to the same infrastructure that my/our official software uses. That’s a lot of traffic I never agreed to, and worse, the creators of these unsanctioned disk images never consulted me regarding this traffic, etc. Kinda shitty. All of this extra unauthorized traffic isn’t fair to the users of the official WPSD software and disk images.
Update - 10/23: I see the maintainers for some of these unofficial versions are now pointing to some of their own server resources, fortunately. Regardless, all other traffic from these unofficial forks is, and has been blocked.
While I’m very flattered that hostpot vendors want to ship my awesome software with their products, it’s not a simple as just using the code or disk images from my website. It’s best to work with me directly, so that we can help get your product(s) working perfectly for your hotspots and users with my software.
Otherwise your users won’t have the “Real Deal” WPSD software and they won’t be able to update, nor will they ever be able to receive support. Working with me and my project team ensures a better and more supported user experience.
If you insist on creating unsanctioned versions of the software for your hotspots, create your own back-end infrastructure to update them - don’t use mine.
Please support your own software and remove references of “
W0CHP/WPSD” from the
code. I don’t want my name/call sign associated with old and insecure software.
See next section…
Without mentioning names (yet); some prominent hotspot vendors and creators
have been working with me on custom versions and disk images for their
products. This is the way to do it, and I applaud the vendors for working
with me…it’s best for the users. You will begin to see these official WPSD disk images for these hotspot
products soon, and these hotpots will contain/ ship with official WPSD software. When released, we will make an official announcement in the various and official mediums.
- Update: 11/20/2023
- Update: 8/25/2023
WPSD is now the official software for BridgeCom’s SkyBridge MAX Hotspots, and they are shipping their new SkyBridge MAX hotspots with WPSD pre-installed. We also have a custom SkyBridge disk image available for previous models of SkyBridge Plus Hotspots (this image is designed for/works with both the MAX and Plus models).
- Update: 6/11/2023
I will not apologize on behalf of the vendors providing you with outdated and unsupported software - they should have known better and worked with me and my team like other vendors do/did. If you are affected from this unsupported and outdated software, speak with them, and lobby them to work directly with the WPSD team and me.
And unfortunately, the maintainers of these unofficial WPSD forks didn’t think about the adverse user support ramifications and confusion they have created; that we cannot possibly, and will not support these installations/users. We can only support the software which we write and maintain.
Thanks for reading and 73,