whylo

Unfortunately the 'for' doesn't match the ID of the input element, so it won't work - for example on the inches-centimetres converter demo the first label should have for="inches" (as the input has id="inches"), but it has for="submissions_values_inches"

A bit of feedback on accessibility. By the looks of your demo page, you're not using the 'for' attribute to associate form labels to their fields. This makes the forms very difficult to use for users of assistive tech, including screen readers. Screen readers read out the appropriate label when an input gets focus, but without the 'for' attribute it has no way of knowing which label is intended for which input.

Thanks for your response. It's great to hear you're improving accessibility - I look forward to trying it out when it's released

If anyone else is interested, I found the relevant GitHub issue: https://github.com/unoplatform/uno/issues/1141

Unfortunately it looks like the output, at least on the web, is completely inaccessible. The DOM of the Simple Calculator example (https://calculator.platform.uno/) and the gallery (https://gallery.platform.uno/) is a div soup with no use of HTML-native widgets for buttons, radios, checkboxes etc. Nothing is keyboard-focusable and there's no screen reader support at all. I'm not sure how it fares on desktop but I would strongly urge people not to use this in its current state for web applications

Yep, same. I used to get a message saying I'd been rate-limited, now I just get a generic error.

The headline's a little misleading IMO - this article isn't about making Linux render text like macOS does (hinting and anti-aliasing methods etc), it's just about replacing the default fonts

Edit: Headline's been changed, it was "Get macOS like font rendering on Linux"

> But isn't it dangerous? How does it know you re not preloading the "please delete everything" link?

In a perfect world no-one would be using links for actions which modify state - they should always be a POST behind a button, not a GET behind a link.

But in the real world this is probably a legitimate concern. They do have methods to mark links as non-preloadable (https://instant.page/blacklist), but anyone using it should definitely do a thorough test, not just copy and paste and hope for the best

Unfortunately screen reader support isn't great at the moment, but using HTML instead of canvas is definitely going to make it easier for you to improve. I'd encourage you to download the free NVDA screen reader (https://www.nvaccess.org/download/) and compare DataGridXL with Excel, or Google Sheets with screen reader support enabled (Tools > Accessibility settings). Announcing the column, row and cell content as you navigate the sheet with the keyboard would be a great start. Google Sheets does this by updating the content of a visually hidden ARIA live region (https://developer.mozilla.org/en-US/docs/Web/Accessibility/A...) as you navigate.

Transport for London have a fairly comprehensive API that has all kinds of live journey and network information: https://api.tfl.gov.uk/ - the article mentions that this project is using the API

Edit: Looks like TMB also have an API. I'm not sure how it compares to TfL's: https://developer.tmb.cat/

The algorithm used is defined in WCAG: https://www.w3.org/WAI/WCAG21/Techniques/general/G18.html#te.... It does attempt to calculate the luminance but you might be referring to a more accurate algorithm.

Personally I don't find pure red on white very readable, but I have noticed some oddities such as pure black on orange (#ff6a00) passing the check while pure white on orange fails, despite being much more readable to my eye.

I've had various issues with Revolut, but there is human support available (eventually) - if you type 'human' in the bot chat you get connected to an agent.

The fact that it's the only support channel available - no phone - is frustrating, and it's even worse that it's in-app only. It gets tiring trying to type up your problem on a phone keyboard, especially when it takes multiple chats to get resolved.

B.F. Skinner trained pigeons to pilot bombs during World War II: https://en.wikipedia.org/wiki/Project_Pigeon

I agree with your prediction; for context, Larson has objected to his cartoons being posted online for decades, so this would be significant even if we're not getting new material: https://www.comicmix.com/2008/03/07/gary-larson-and-our-far-... https://www.techdirt.com/articles/20101230/02545312468/dear-...

I was able to add the tracking code to my site without signing up and could see the stats without any authentication (see my other comment: https://news.ycombinator.com/item?id=18024886). Is that by design?

It says there's the ability to make them public, but it doesn't mention that they'll be public by default. Maybe it's different if you sign up first before adding the tracking code, but it's odd that I can use the tracking code without signing up for the trial.

Yeah, I saw that too. Someone tested for XSS in the referer too (<script> tag) but luckily it was escaped

This is a great idea and I love the design.

It looks like anyone can see the stats for any domain using the service without any authentication. I added the tracking code to my domain and was able to hit https://simpleanalytics.io/[mydomain.co.uk] without signing up or logging in. I was also able to see the stats for your personal site.

Is that intentional? If it is, it seems like an odd choice for a privacy-first service. If not, it seems like quite a worrying oversight in a paid-for product.

There are quite a few JS Ambilight demos out there. Here's one that works pretty well: http://media.chikuyonok.ru/ambilight/

The signup form also takes you back to the homepage if you happen to click anywhere on the blue background