The Open Web language and region policy


The Open Web is focused around services related to Japan and the UK.
Due to this, the main languages used are and will continue to be English and Japanese.
From hereon, announcements will mainly be done in both English and Japanese at appropriate times for audiences of those languages and related regions.
British English will be prioritized. However, in certain circumstances regional English may be used where appropriate OR American English may be used where common(for example, programming related topics.).
Services will also be provided in both Japanese and English. If a whole or part of a language is not available, please feel free to request it be provided.


Other languages may be provided for services and important help. For other less important areas, translations will generally not be provided, excluding any user-created translations.
The ability to share user-created translations will be prioritized and allowed generally for any language as long as a reliable quality check system can be prepared.
If you have any questions or want to help with translations, please feel free to enquire.


Due to the location of The Open Web business, services will often focus on the Kansai region, Osaka prefecture, Sakai city areas.
Services related to the UK are also a priority, and any services that deal with both Japan and the UK will be further prioritized.
Areas outside of Japan and the UK are to be treated as low priority at least for the time being. However, expansion of existing products into other regions especially where profitable would be happily considered.

Data Converter Initial α Version Conversions

Data Converter has been released with many simple initial conversions.
Many more, especially, complex functions will be added in future versions.
At this point, I would like to introduce the kinds of conversions already added.

DOM Element conversions

DOM Elements are HTML elements used in HTML web pages.

Casting conversions

Casting is converting from one type to another.
For example, text is known as the “string” type.
Casting conversions can generally be done by using “Format” to choose the input format.
Cast conversions without using “Format” will generally be supported in the future.
Common cast conversions include: Date ⇒ String, String ⇒ Number, Boolean ⇒ String, etc.

Japanese conversions

Different types of text and language conversions will be added over time, but for now some important Japanese conversions have been provided.
Japanese number to number conversions are possible. For example, 十三 ⇒ 13.
Japanese to Braille conversions are also possible. For example, こんにちは ⇒ “⠪⠴⠇⠗⠥”.

Measurement unit conversions

Many unit conversions have been provided.
This includes common SI units and other commonly used measurement units.
Units generally use their displayed unit name. For example, grams to kilograms can be done by converting from “g” to “kg”.

Shell conversions

Command line shell display conversions are provided to easily convert between shell input/outputs and commonly used input/outputs elsewhere.
For example, multi-line and single-line conversions, and “$ command” to actual inputtable commands.

A large number of additions to the above conversion types, and completely new conversion types, will be added in future versions.

Please try it out at the link below.

Home-page version: 1.0.3 Released

Home-page version: 1.0.3 Released

# Features

  • Additional websites
  • Name fixes
  • Go to active website homepage functionality


# Changelog

## [1.0.3] – 2021-04-21
### Added
  • Additional websites (Additional important global websites)
  • ALT + Enter: Opens active website homepage.
  • ALT + click on website icon: Opens website homepage.
### Changed
  • Clicking active website icon changed from opening search page to opening homepage.
  • Website names improved.

Introducing Data Converter

Data Converter is a web application for converting from one format to another.
It is currently in α(alpha) stage which means there are occasional issues and functionality is prioritized over UI/UX.
The goal of this project is to provide a mechanism for easily converting from one format to another, without the difficulty of searching for the correct type or, converting multiple times to get to the desired format.

Features of this project(some in progress):

  • Utilizes client(in browser) conversions where appropriate.
  • File and user input conversions.
  • Node functionality for complex multi-step conversions.
  • Large number of varying conversions.
  • Output history for easy copying of multiple calculation results.
  • API linking.

Similar competitor services do exist, but they often only provide slow server-side only conversions and are limited to a few conversions of file formats.
This project converts arbitrary data so in addition to file conversions, can also convert from user input or even in page elements.

Additional functionality and fixes will be provided in future versions.

Please try it out at the link below.

If you have any feedback please feel free to get in contact.

Data converter version: 1.0.0-alpha released

Data Converter version 1.0.0-alpha Released

# Features

Data converter released in alpha version.
Features many conversions, input and output formats.
※ Due to alpha stage, bugs may be encountered.
Data Converter

# Changelog

## [1.0.0-alpha] – 2021-01-24

### Added

– Convert between different formats.
– Load text, file, other
– Output or download

Help with WebRTC, Webcams and getUserMedia.

WebRTC and rendering help.
This article provides help on video/audio streaming, webRTC troubleshooting, webcams, setup, and more.

Recommended environment

  • Development environment: Windows 8/10 + Chrome
  • Caution: Make sure to use the latest version of the browser you are using.
  • Supported browsers: Usually, in addition to Chrome, any Chromium based browser (For example: Brave, Edge, and more: and Firefox is also supported. Firefox is usually very similar to Chrome, but small differences can sometimes lead to bugs and performance issues. ※ Update (2022/05/13): New versions of Edge use Chromium, so has generally the same features as Chrome.
  • IE: Internet Explorer should be avoided.
  • Other browsers: Old versions of Edge have better support than IE, but Chrome and Firefox are preferred. It is important to be especially aware that Edge used to use ORTC not WebRTC.
  • OS: There are usually no problems using another OS, but hardware related bugs may occur in rare circumstances.

Plugins and extensions

Internet Explorer(IE):

Does not support WebRTC, but there is a plugin for supporting WebRTC in IE: Temasys

Screenshare in Chrome:

At the time of writing this document, obtaining screen data in Chrome without an extension was not possible.

However, this is now (2022/05/13) possible using “getDisplayMedia”. Support for this can be checked in this getDisplayMedia Demo

API information can be found here:

An extension can be independently developed, or a stream can be obtained by using the extension below.

How to use HTTPS required functions when using HTTP

Functions that might not reveal private data are progressively requiring encryption.
The best counter-measure for this is obviously to switch your website to https.

Details below:

However, if not supporting https, then the following counter-measures are available:

Use an old browser

Due to vulnerabilities and inconvenience, this method is NOT RECOMMENDED. If going to use this method, a limited secure environment(Local, single domain) should be used.
Information can be found below, but compared to previously, this method has become difficult.

It is necessary to find the installation file from before the function limitation was added from the app history page.

Https only support for getUserMedia happened in version 47 for Chrome and version 46 for Chromium.
The portable version is better than the installer version of Chromium to use because there is no auto-update
Use version 45 from the link below for the appropriate Chromium (Portable).
For the Installer version of Chromium, each is grouped by commit number, which is difficult to determine from the version number. Important versions are 45 and below (Commit number < 31****).

Https support changes for Firefox in the link above were posted in April 2015 so versions 35.0 and before should be fine.
However, at the time of writing(2017/08/09), it seems getUserMedia can still be used on HTTP pages.

Old browsers tend to have webRTC and getUserMedia bugs and specification differences, which may result in code not working.

Install file


Flag permissions

Chromium: –allow-running-insecure-content
The flags below can be used. Refer to the links below for command line information:


Setting exceptions via flags

Currently (2017/08/09), Chrome supports using flags, Firefox has no problems without flags.

Use another browser

Firefox can be used at the current time of writing (2017/08/09).
Functions only available in https for Chrome have been available using HTTP for a while in Firefox.
This is subject to change in the future.


Counter-measure below for 「Secure Connection Failed」 in Firefox issue:
security.tls.insecure_fallback_hosts = 「」

Microphone/Webcam permissions

Due to this feature possibly revealing private information, please refer to “Permission required functions“.
The permissions mechanism allows separate access to device audio and video. Both simultaneously access the audio/video from the same and separate device is possible.
Depending on the environment, an error may occur if the function settings and the allowed device statuses do not match. If a problem occurs, both the settings and permission statuses should be checked.
Depending on the browser (Confirmed in Chrome), default devices may be available. This is not very useful for accessing media, but this may fix specific errors when you want to allow a media type but do not have the correct device.
The available permissions that can be selected may change depending on installed software (Audio management software).

Microphone/webcam problems

  • Fail to acquire audio from device with multiple functions: Depending on the browser(Occurred multiple times in Firefox), audio of a device can not be acquired. For
    example, both video and audio functionality exists for a webcam, but audio can not be acquired. In this case, there is a chance that the application will stop, depending on the source code. This can be solved by using a separate device for each function.
  • Unsupported browser: Check whether your browser can use getUserMedia:
    Update to a new browser.
  • No device: There is a chance the device is not inserted. Please check the device is properly inserted.
  • The environment does not support the device: Check whether the device can be used on other websites.
    If the above fails, check whether it can be used in other browsers or elsewhere in the OS.
    If the device does not work on the OS, try reinstalling the drivers and contacting the manufacturer.

Permission required functions

Functions that might reveal private information often require permissions due to standardized specifications.
Permissions are mainly controlled via displaying upon execution, in-app flags or setting files.
The easiest method is “displaying upon execution”. When the function is executed, a pop-up should be displayed.
The selection made should be usable across the session. When on an https URL, it is common for the selection to be remembered.

Web camera environment

When using a webcam, the following is recommended to play clear video:

  • Brighten the room. When there is little light, the image quality becomes rough and loses sharpness. It especially causes issues for image recognition.

Microphone environment

When using a microphone, the following is recommended to play clear audio:

  • Do not output audio too close to the microphone. When audio is outputted too close to a microphone, the audio from the microphone is inputted into the microphone again, causing a howling effect.

WebGL support

Pages with a canvas (Image rendering functionality) often use WebGL. Even more so when rendering in 3D.
In order for the code to work and performance not to drop, WebGL should be enabled.

Chrome: chrome://flags/ Enabled by default, but should check each WebGL flag.
Firefox: about:config Make sure webgl.disabled = false + about:support WebGL rendering details are correct.

WebRTC issue report tools

WebRTC issue reporting

The following information should be provided when reporting WebRTC issues.
It becomes a lot easier to handle issues as more accurate data is provided.

  • OS (Including version number)
  • Browser (Including version number)
  • Web camera (Source of video)
  • Microphone (Source of audio)
  • Network speed
  • Network topology
  • Allowed and blocked ports for TCP and UDP
  • ICE Candidates log(If available)

WebRTC ports

WebRTC uses the following ports.

  • Signalling: 80 or 443
  • STUN/TURN: (default)3478, (Google STUN)19305 or 19307, (TLS)5349, (HTTP)80 or 443
  • P2P: 0~65535 (Often, 50000 and above)


Please consider trying out the Commew Web App for P2P communication, trying out WebRTC, testing out webcams, and more.

First post

The Open Web info. Introduction to services, data, and more.

This post will be used as the main come-to post for any important information.

Main website:
Business website:

Home page startpage web service: https://theopenweb/app/home-page
Data converter web service: https://theopenweb/app/data-converter