I have no specific knowledge to answer that but I would guess that it is a consequence of the open source software being used to implement those pages. (So, yes, if Purism had unlimited resources, they could fork / update the software in order to address your implied request - but I would rather they continued to work on the phone.) As you are perhaps implying, the functionality to make those pages a wiki requires lots of complexity that can’t be done (nicely) without scripting (not to mention some of the other dynamic content that is on that domain).
I suppose also there are philosophical and practical considerations to encourage non-Purism staff to put in effort to provide information in the wiki that is useful to the community. I among many others have done that - so it is unfortunate that you will never benefit from it.
An easier approach might be just to mirror the displayed content of the site on another site (at a minimum the FAQ and the Tips).
Or perhaps Purism could develop a script that packages up all the underlying documentation content - so that you could keep a local copy up to date via apt, with the downside that you then have the marked up content, not the displayed content. However the mark-up language in use is simple enough that you could still get useful information out of it without bothering to render it.
Partly answering my own question … the manufacturer’s page does say 802.11ax/ac/a/b/g/n and WiFi 6 but that is not the whole story - as it would need an appropriate driver, settings, … and WiFi 6 would need to have been tested. (My access points are only 802.11ac so even if I upgraded my Librem 5 WiFi module, even if WiFi 6 worked, it would only be an upgrade from WiFi 4(?) to WiFi 5 in practice for me - and I would not be able to test WiFi 6.)
So it still needs a statement from Purism that yeah we tested WiFi 6 in the Librem 5 and we are comfortable that it works reliably.
You may want to take a look at docs/puri.sm / phone.
When I get there, I get a popup asking if I want to translate the page.
NOTE:
I was not at any foreign page before hand, I was reading stuff in forums.
I don’t keep a cache, or History.
I do not have any such related stuff on my desktop. It’s the only page that does that - the landing page.
The page does not appear to contain Slovenian.
Tested with FireFox, Opera, Brave = was OK
Google Chrome browser is the culprit. Maybe ask someone else if they get the same, to be sure it’s not something in Chrome here.
I also noted a number of grammar and spelling errors.
Interesting observation but since I don’t have Chrome installed and prefer to avoid The Stalker’s Browser, I can’t test it myself in Chrome. What’s the exact URL of the page that is misbehaving?
Also docs.puri.sm is not maintained by the community. It is maintained by Purism and randoms like me can’t directly make changes. We can however create a branch of the page, make changes in the branch and then ask Purism to merge the changes. So if the density of grammar and spelling errors is high enough, it may be worthwhile.
That’s what I was thinking. I don’t know the details of how that would be done, but it would be nice if Purism mirrored the data onto one of their other sites that doesn’t require javascipt (like https://docs.puri.sm).
Same for me, but I ordered it anyway for the advertised speed improvements. I will upgrade my network to WiFi 6 eventually.
Google Chrome browser is effectively malware. I would suggest never installing it on anything you care about. I remember reading an article about the Chrome browser scanning the files on the host computer a while ago. Google’s search engine and browser used to outperform all competition, but that has not been the case for several years now. At this point, they are the worst options available.
OK, I looked into this a bit more and I don’t think your request would be easy. It looks to me that what happens when you view a page on that site is that the web server returns a JSON container and the contents therein are marked up text (using markdown syntax).
That’s why you have to have Javascript enabled. The document is rendered on the client side. (There is a clear benefit in server performance with that approach but a clear cost in terms of privacy.)
So your direct options would appear to be:
Display marked up text i.e. unrendered. (Even this is not easy because the text doesn’t have actual line ends. So the bare minimum would be to remove the JSON container and resurrect the line ends.)
Install a plug-in / extension / viewer of some sort into your browser that is directly capable of processing a document in the above format i.e. rendering it. (I did not search the web to see whether such a plug-in exists.)
It looks like they will be too busy with more important things for a while. They still haven’t removed google fonts from their store either. Maybe they will get around to these things in the coming years. I’ve seen others make similar requests, so I’m sure there will be more posts about this in the future.
Download the file ‘as is’, run a standalone converter program (outside of the browser) and then view the resulting HTML as a local file. (This is of course not as convenient but if you really want to get useful info out of the FAQ etc., it could be worthwhile.)
You can download the file right now. (I did that myself so that I could have a squizz at what the document format is.) Obtaining a suitable converter program would be up to you. I didn’t investigate availability but I think it would exist as open source (given that this forum uses the open source Discourse software and that posts made in this forum use markdown or some variant thereof). So in summary you could do that right now.
Copy the URL from that attribute (which in this case at the current time is /api/v4/projects/995/wikis/Tested-Accessories?version=11df774418f94e96f80c5e486ca702532085f084)
Close the source tab
Go to the address bar of the actual page and replace the part after https://source.puri.sm with the copied URL and press Enter
A bunch of JSON will come up. You can press Save.
The thing that was just saved is “markdown” markup language marked up text in a JSON container.
You would be looking to convert that to HTML.
That’s basically what happens every time someone reads a post that someone makes in the forum. The post is created in “markdown” (but because plain text is valid “markdown” you may not be aware of that). When someone reads the post, the post has to be converted to HTML (which happens on the server side in the case of the forum software).
The piece of the puzzle that I don’t know at this stage is whether the converter software will need for you to cut the markdown out of the JSON container and whether the software will need you to convert the line ends (\n to an actual line end).
Once you’ve converted to HTML, just double click that resulting file.
We intended to have all of our product pages updated with the new WiFi/BT information along with the announcement around the SparkLAN card, because we rightly assumed that some of our detail-minded customers would immediately check those pages to see if we had updated them.
Sadly the team wasn’t able to update them in time, but they are working on it.
That is good to know. And thank you for the response on this topic.
If I may ask a related question here:
Is there progress being made on the removal of the google connections on the shop page?
I recently noticed that if I unblock the googleapis domains, the Purism shop tries to connect to gstatic, which is very concerning to me. @amarok and I may know to block all google domains, but people that are new to privacy may not know to do that, especially on a trusted page like the Purism shop.
It is a constant issue we desperately want to correct and have been trying for a few years now. The challenge has been finding out which plugin is issuing the call, I believe at one point it was due to a particular Google font but I also believe the cause has changed over time. What happens is we track something down, resolve it (finally) and then later discover some new update, or new plugin we need to use, pulls a reference back in. It’s frustrating.
Google stuff is injected so ubiquitously into web software, if you aren’t writing everything 100% yourself it is challenge to find and root it all out, since everyone else who doesn’t share our scruples about it, sees no problem with relying on them for fonts or other helpers in their libraries.
I’ve only seen a few mistakes. Many, many years ago I worked as a beta tester - back when we got paid. Not so these days. But checking manual/docs is still in me.
OK, so I think that what is happening here is that
a) Purism is not specifying a language at all on that page, and
b) you have enabled automatic translation in Google Chrome (on by default?).
but better would be "Don’t use Google Chrome at all ! "
and if you do choose to use Google Chrome then first check that you have specified a reasonable default language (in your case presumably Canadian English or Canadian French or both), which is also covered by the config mentioned in the howtogeek article.
I hadn’t considered that it was an endless cat and mouse game, but your response definitely helped me understand the problem. I’m happy that the google stuff is easy to block, and I can safely make my purchases on the Purism shop without any google connections.
I wish more online shops were as good as the Purism shop.
Nope. Not my end. I said before, I will search best I can before jumping down any rabbit hole.
Business has to play with business - whether we like it or not.
Funny you provided the link to howtrogeek. I already read the same thing before mentioning it here.
Summary: It’s not the end user. It didn’t bother me, seeing other errors in typos and grammar, and simply obsolete stuff, or following a link I was handed, was a 404.
I just thought someone new might look at whole and think ‘Hmm, not good housekeepers’.
Here’s how I did it (in Firefox).