usrlocal1023

The service doesn't seem to support IPv6 as there are no AAAA DNS records.

  $ dog A AAAA fonts.bunny.net
  CNAME fonts.bunny.net.      10s   "bunnyfonts.b-cdn.net."
    A bunnyfonts.b-cdn.net. 10s   195.181.164.130
  CNAME fonts.bunny.net.       9s   "bunnyfonts.b-cdn.net."
    A bunnyfonts.b-cdn.net.  9s + 195.181.164.130

You can get monthly snapshots free of charge which receive some testing compared to rolling builds. They currently have 1.3 RC builds https://vyos.net/get/snapshots/

When Slack launched video calls, it was using Chrome's own implementation of WebRTC which is called Plan B. So it worked in both their app which is electron based and Chrome. Not sure if it worked with chromium derivatives like Brave, Vivaldi, etc.

Firefox rolled out the standard based WebRTC implementation and chrome eventually did as well, but companies like Slack and various others didn't migrate instead just threw an error message saying calling isn't supported in Firefox and instead use their app or chrome.

Since Slack's partnership with AWS about 2 years ago, they migrated from their own call infrastructure to using AWS's Chime. Chime SDK has support for all major browsers https://docs.aws.amazon.com/chime/latest/dg/meetings-sdk.htm...

But their browser check still remains today and Mozilla started to spoof the user agent as a workaround so that Firefox users can make calls as Slack aren't willing to remove the check or properly add support.

Chrome is planning to remove WebRTC plan B soon, so this should force companies to use the unified WebRTC implementation and hopefully means Firefox support. https://groups.google.com/a/chromium.org/g/blink-dev/c/IY2am...

Also, one more thing to note, uBlock Origin works better in Firefox https://github.com/gorhill/uBlock/wiki/uBlock-Origin-works-b...

They tried but Slack weren't interested. Update from 2 years ago

To summarize my current understanding: Slack's video conferencing service only support Chrome's non-standard Plan B format for WebRTC calls. And our attempts to talk to Slack about changing that were kindly rejected (we met with them shortly after they had launched the calling feature). And my repeated questions in public events about adding Firefox support were also turned down.

Source: https://bugzilla.mozilla.org/show_bug.cgi?id=1626121#c4

Further clarification from last year https://bugzilla.mozilla.org/show_bug.cgi?id=1626121#c10

I have seen people mention that they have tried few more times to contact them, but Slack weren't interested.

My understanding as to why it works now, correct me if I am wrong, is because of Slack moving to using AWS Chime SDK for calls which has Firefox support and just faking the UA to Chrome tricks Slack into loads the necessary SDK/JS for calls and Chime SDK takes care of the rest.

It would be nice if it would integrate with a 3G/4G dongle. Huawei dongles (maybe ZTE as well?) already have an HTTP endpoint to get SMS and also their USB dongles have no battery, so it is much safer to leave it plugged into a wall 24/7 than a phone.

Most phones these days do have battery charging cut off, so they should be safe but still prefer to have one without battery for leaving it plugged in 24/7.

They now have a dual stack EC2 API endpoint. But you have to go out of your way to use as it is on a totally different domain, and also it is limited to few regions. us-east-2 region for example

  api.ec2.us-east-2.aws

https://docs.aws.amazon.com/AWSEC2/latest/APIReference/Using...

There is also Zen Internet who are cheaper than AAISP. They provide a static /48 subnet allocation that you can divide up into 2^16 /64 subnets.

Unfortunately IPv6 is opt in so after getting your connection you will have to contact them, they will then assign you a /48 and enable IPv6 on your connection.

Congratulations on the launch. Site looks nice and fast as well.

Just some comments.

1. At the moment you are forced to login if you want to change site theme or font size. It would be nice if you could without logging in. I am fine it with the settings persisting as long as I don't clear the cookies.

2. Are there any plans to support prefers-color-scheme so you don't have to manually set the color to dark?

3. Also, the links to news article aren't direct. Goes via https://newsandrumors.com/nar/go/<random-id-here>. Is it possible to opt out of this?

From a study conducted by Douglas J Leith from the School of Computer Science & Statistics at Trinity College Dublin, Ireland, they found that the new chromium based Edge is sending hardware UUID's back to Microsoft and there isn't an option to turn it off.

"From a privacy perspective Microsoft Edge and Yandex are much more worrisome than the other browsers studied. Both send identifiers that are linked to the device hardware and so persist across fresh browser installs and can also be used to link different apps running on the same device. Edge sends the hardware UUID of the device to Microsoft, a strong and enduring identifier than cannot be easily changed or deleted. Similarly, Yandex transmits a hash of the hardware serial number and MAC address to back end servers. As far as we can tell this behaviour cannot be disabled by users. In addition to the search autocomplete functionality (which can be disabled by users) that shares details of web pages visited, both transmit web page information to servers that appear unrelated to search autocomplete."

https://bgr.com/2020/03/11/microsoft-edge-browser-privacy-is...