I'm still not entirely sure why anyone would load fonts from a 3rd party link that's bound to break sometime. Just add it to your assets like a normal person and Cloudflare will cache it for you anyway.
The license is non-standard too, something called SIL. I'm not gonna bother looking up what that weird thing permits when I can get thousands of CC0 fonts from like a dozen sites.
> The license is non-standard too, something called SIL. I'm not gonna bother looking up what that weird thing permits
It's the same as Google Fonts (because they're the same fonts). Most of the fonts are released under the terms of the SIL Open Font License 1.1, and a handful of them released under the terms of the Apache License 2.0.
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/
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.
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.
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.
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.
Sadly, this behavior is somewhat common for many sites that block firefox based on the user agent. At least form some webcompat bug issues I've looked at.
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.
A simple PowerPoint timer set to be on 1 hour out of every 12 works pretty well to stop wall mounted iPads from doing that “swell up the battery until the screen pops out” thing.
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
Our reason for this is that customers may have IP-based rules in their IAM policies. If we silently turned on IPv6 for existing endpoints, those policies would suddenly break without notice. Hence new names and SDK options for dual-stack.
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?
1) Are you sure you cannot change the font and and site theme without logging in? I just tested it and it works fine for me in private and incognito modes.
I purposely designed it so a lot of the settings are available via the quick action bar for non-logged in users.
If you have no-script active or have disabled javascript, then the only option would be to login to change them via the Settings page.
Otherwise, you should be able to toggle those easily via the quick action bar above the search results.
2) Definitely. I probably should have already done that.
3) I am still thinking on this. My plan was to soon remove it for upgraded accounts. There is no user-specific tracking, but by anonymously tracking clicks in general it helps with ranking and generating "popular" search results order.
Most users have JS enabled, you could just track clicks making an Ajax get call with a click listener on all links before navigating if you don’t want to use something like GA.
The Settings page requires that you login, which only requires an email address.
The quick action bar on the search results page also has a smaller cog icon and other icons on it that will allow you to change several settings without logging in, but you must have javascript enabled to access them.
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."
