intiface / intiface-tutorial Goto Github PK

see https://stackoverflow.com/questions/51639850/how-to-change-page-titles-when-using-vue-router

Make sure people haven't paired with their operating system, otherwise we won't be able to see devices.

There are times (at least on my linux box) where the adapter needs to be replugged before it will connect to devices. This usually shows up as a scanning error. We should make these obvious to the user.

Use the hardware lookup widget that we're building for the buttplug/intiface websites, so people can see if they have compatible hardware.

water fox 56.2.10.1
Secure Connection Failed, An error occurred during a connection to localhost:12345. SSL received a record that exceeded the maximum permissible length. Error code: SSL_ERROR_RX_RECORD_TOO_LONG

chrome 74.0.3729.169 (Official Build) (64-bit)
This site can’t provide a secure connection localhost sent an invalid response.
Try running Windows Network Diagnostics. ERR_SSL_PROTOCOL_ERROR

errors come from clicking "Click here to open a new tab and accept the certificate."

also "when trying to connect again"
The connection failed. If you look at the server dialog, you may see something like this:
This means we need to set up the self-signed security certificate in your browser.
To do this, we'll need to visit the websocket server, then accept the certificate.

Tell people to turn on Experimental Web Features on chrome in linux.

Detect domain and post warning if on dev/beta.

Epic for finishing conversion from twine to vue, so we can finally point people at an updated tutorial instead of the old one.

See #7 (comment). This wasn't a problem with intiface-node-cli after all, as playground connects fine from localhost.

Stack trace:

Apologies! An error has occurred. You may be able to continue, but some parts may not work properly.

Error: <<removeclass>>: no elements matched the selector "#devicediv".

Stack Trace:
value@https://tutorial.buttplug.world/:2272:17102
handler/<@https://tutorial.buttplug.world/ line 2272 > eval:1410:9
./node_modules/events/events.js/EventEmitter.prototype.emit@https://cdn.jsdelivr.net/npm/[email protected]/dist/web/buttplug.min.js:8:40382
ParseMessagesInternal@https://cdn.jsdelivr.net/npm/[email protected]/dist/web/buttplug.min.js:23:47404
ButtplugClient/this.ParseMessages@https://cdn.jsdelivr.net/npm/[email protected]/dist/web/buttplug.min.js:23:44441
./node_modules/events/events.js/EventEmitter.prototype.emit@https://cdn.jsdelivr.net/npm/[email protected]/dist/web/buttplug.min.js:8:40382
ButtplugBrowserWebsocketConnector/this.ParseIncomingMessage@https://cdn.jsdelivr.net/npm/[email protected]/dist/web/buttplug.min.js:23:40122
ButtplugBrowserWebsocketConnector/this.Connect/</</</<@https://cdn.jsdelivr.net/npm/[email protected]/dist/web/buttplug.min.js:23:39655

It appears that the device added/removed events are not being handled correctly.
Device removal fails to remove the device on either the device scanning page or the send command page. Re-adding the device again causes duplicate devices on the scanning page and the above stacktrace on the send command page.

Originally reported via Discourse https://metafetish.club/t/error-during-interactive-tutorial/403/3 by zas

Ping matomo on each router move.

Specifically the link to metafetish.github.com/buttplug-tutorial