Compare Chrome extensions: ChatWork Stamp vs LiveHosts

Stats ChatWork Stamp ChatWork Stamp LiveHosts LiveHosts
User count 376 10,000+
Average rating 5.00 3.47
Rating count 3 36
Last updated 2019-09-17 2022-03-29
Size 69.37K 59.17K
Version 1.1.13 2.0.0
Short description
ChatWorkのpreviewタグを入力する機能 Switch your host/IP mappings in real time without editing your hosts file
Full summary

ChatWorkのチャットで、アップロードした画像ファイルのpreviewタグを簡単に入力できるようにする拡張機能です。 スタンプのように使用することができます。

・選択できる画像は、チャットルーム毎に、直近アップロードされた200ファイルに含まれる画像(jpg,gif,png)ファイルです。 ・10MB超のファイル(プレビューが表示されない)の除外はできていません。

その他の機能として以下もつけておきました。 ・info,title,codeタグの入力補助 ・LINEのような外観になるスタイルシートを適用可能(1.1.11時点で、一部上手く表示されない部分があります)

https://github.com/ntkkni31/ChatWorkStamp

1.1.6 - 2017/7/20 チャットワークのタグclass名変更に対応。

See more

LiveHosts is a Chrome extension that aims at providing a working (even if sub-obtimal) solution to a common nuisance that many web developers have to deal with every day. If you have multiple versions of your websites sharing the same host names on multiple environments, you often need to switch the assignments in your OS hosts file.

Other extensions (like the life-saving HostAdmin) can help with the cumbersomeness, but changes to the hosts file usually take an inconvenient amount of time to actually affect the browser.

Unfortunately, there is no way to make Chrome direct requests for a hostname to a specific IP without a standard redirect - you could set up a smart HTTP proxy, but it's often not possible or not convenient.

This extension settles for a sub-obtimal approach: requests to the indicated hostnames are redirected to the chosen IPs with an additional Host header. The browser's address bar reflects this behaviour showing the hostname right after the IP (e.g. http://127.0.0.1/www.example.com/). The extension also tries to take care of all requests to either the IP or the hostname in a consistent way.

Issues

After the redirect, the user is effectively in a different domain that the one they expected. They may notice some functional differences:

  • depending on the server, parts of a web page referring to the site URL (like href and src attributes) could be different from the original
  • window.location has a different value that can potentially throw off JavaScript snippets
  • most Cross-Origin request won't work