Hacker Newsnew | past | comments | ask | show | jobs | submit | alphafredo's commentslogin

I have the same idea each time I read something about backlights;

How easy would be to place a cheap LCD at the back of the main screen and mirror the same output (in horizontally inverted mode)?

Technically it might require synchronizing the frame latency differences between the two devices, but would such a hack improve the perceived quality?


Hisense Dual Cell might be what you're talking about.


The cheap LCD will probably not be able to produce enough light to brighten up the main display, and if the two panels are not of equal size, you will need to add some depth to the unit and come up with a projection system to "blow up" the light map to cover the entire image.


Uber seems to have weaponized senior public officials and MPs in many European countries.

This a scandal of huge proportions.


I remember playing Lock and Load 2 [1] in high school during that era against my classmates via Bluetooth.

It was pretty fun! Symbian has been a great OS, something I reaffirmed when I studied Tanenbaum's circus book in college.

[1] https://www.youtube.com/watch?v=-fC1xI3oGPU


Symbian was not a great from a development standpoint I understand.


At my company we are using dockerized mailcow on a Hetzner VPS and it has taken us some time to have the IP whitelisted in all major e-mail providers.

The easiest to work with have been Microsoft and Yahoo. I still haven't found a way to whitelist our IP on centurylink.net, charter.net and att.com (please let me know if you have any ideas)

Some links that might be of help to others:

[1] https://sendersupport.olc.protection.outlook.com/snds/data.a...

[2] https://io.help.yahoo.com/contact/index?page=confirmation&lo...

[3] https://postmaster.google.com/u/0/dashboards#st=userReported...

[4] https://support.microsoft.com/en-us/supportrequestform/8ad56...

[5] https://www.mail-tester.com/


Cannot upvote you enough for the yahoo link.


From the link you shared it looks like they are restoring the functionality:

https://bugs.webkit.org/show_bug.cgi?id=230382


T￸h￸￸i￸￸￸s c￸o￸￸m￸￸￸m￸￸￸￸e￸￸￸￸￸n￸￸￸￸￸￸t s￸h￸￸o￸￸￸u￸￸￸￸l￸￸￸￸￸d￸￸￸￸￸￸n￸￸￸￸￸￸￸'￸￸￸￸￸￸￸￸t b￸e e￸a￸￸s￸￸￸y t￸o r￸e￸￸a￸￸￸d b￸y s￸c￸￸r￸￸￸e￸￸￸￸e￸￸￸￸￸n r￸e￸￸a￸￸￸d￸￸￸￸e￸￸￸￸￸r￸￸￸￸￸￸s


With NVDA on Windows, when I read the comment normally, it's spelled out. When I read it character by character, I get "symbol FFF8" for each of the hidden Unicode characters. And when I move line by line through NVDA's linear representation of the web page, the hidden characters count against the length of the line for the purpose of word wrapping.

Narrator's behavior is weirder. If I turn on scan mode and move onto the line with the up or down arrow key, Narrator says nothing. If I read the current line with Insert+Up Arrow, Narrator spells it out like NVDA does. When moving character by character, Narrator says nothing for the hidden Unicode characters. And because Narrator doesn't do its own line wrapping but defers to the application to determine what counts as a line, the text only counts as one line.

Disclosure: I used to work on the Windows accessibility team at Microsoft, on Narrator among other things.


It is difficult to see on an iPhone, but it sounds fine in Voiceover.


yep, it is not.


> jQuery, Prototype, ExtJS/Sencha, Backbone.js and Angular all seemed promising, but none took enough of the pain away.

I feel the same. Coming from MooTools, Prototype, Dojo I have found that modern frameworks like Vue and Svelte make my life so much easier.

The whole JavaScript ecosystem with Node.js and npm has helped such ideas/implementations/frameworks bloom and I'm grateful for that.


There's a great resource on the techniques the bots and the bot detectors use, beside rate limiting IP addresses (creepjs is a personal favorite). [1]

[1] https://bot.incolumitas.com/ Expand all Sources/Links under 'More Sources/Information'


Support for Wayland is getting up there. Just five days ago the bounty to support Wayland in Barrier was funded [1]

[1] https://github.com/debauchee/barrier/issues/109#issuecomment...


> Support for Wayland is getting up there.

After almost 13 years of development the progress is rather embarrassing.


It's a hard problem to solve. Wouldn't you agree?


Taking screenshots/streaming is not a hard problem. However Wayland artificially turns something as simple as taking a screenshot into a hard problem what was before a simple function call to XGetImage(). As exercise I recommend to implement a native screenshot application in both X11 and Wayland.


I think you're completely ignoring the security implications of "a simple function call to XGetImage()".


What are the security implications? Programs that call XGetImage() when sandboxed in a Xpra/Xephyr session will get back nothing.


Will get nothing... that means the screenshot won't be taken.


They are all engineers in disguise.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: