helper
Joined 16 years ago
Joined 16 years ago
If you look at the history page you can see its not 100% for every month: https://status.slack.com/calendar
I've worked with a number of captive portal systems and they all basically work the same way. The AP/controller intercepts http requests and redirects to the captive portal page with identifying information about the device (ip,mac,ssid,ap_mac,etc.). The captive portal http server shows the user a splash page to accept terms or enter a username/password or a credit card. Once the captive portal server decides the user should be allowed onto the network it needs to communicate that back to the wireless hardware which is done with the user's mac address.
Based on the requests it looks like they have some ads/trackers on the splash page that are getting requests with a referer set to the original splash page url (which includes the client mac address). A no-referrer meta tag or an intermediate redirect would prevent this from happening.
I've not heard of JPEG XL before now. Why would you name it that? XL certainly doesn't make me think "wow that sounds like way better compression".
JPEG Blockchain: come on! Are you really so worried about being relevant that you have to talk about blockchains in your press release?
JPEG AI: I could image that this is real, but I'm fairly skeptical of anything that is taking about machine learning and blockchains in the same context.
Its so unnecessary too. A 3x quality improvement is massive. Why not just let that speak for itself? This press release makes me hope just a little bit that JPEG XL loses out to WebP or HEIF.
If you were building a kafka like system in house for private use only, then yes I agree with your sentiment. If you are building something to be used by hundreds or thousands of organizations then the cost benefit tradeoffs shift to where it probably makes sense to pull the consensus logic into the primary application itself.