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

At this point the primary thing that's keeping me from switching to Wayland (KDE) is lack of support for remote desktop software, especially with multiple monitors...

Hopefully AnyDesk and Remmina will address this issue before KDE ends it's mainline X11 support next year.


I've had a similar issue recently and I found that rustdesk[0] works pretty well for casual use despite wayland support being labelled experimental. I use it for pair programming with someone on multiple monitors while I'm on a laptop and all the switching and zooming required worked.

[0] https://rustdesk.com/


:) This is a feature of a wayland compositor: I don't want it able to do remote.


It doesn’t have to be like X11. Presumably, it’d be something you could disable if you’d like.

It’d be very handy if we had a performant remote desktop option for Linux. I could resume desktop sessions on my workstation from my laptop and I could pair program with remote colleagues more effectively.

In the past I’d boot into Windows and then boot my Linux system as a raw disk VM just so I could use Windows’s Remote Desktop. Combined with VMware Workstation’s support for multiple monitors, I had a surprisingly smooth remote session. But, it was a lot of ceremony.


OTOH, the enthusiasm for breaking legitimate features that people were using has not helped Wayland adoption.


It is optional: if you want it you will need to select a compositor which does have this expensive feature.

Don't forget, wayland is fully dynamic.


That's one of Wayland's other major faults IMO


It is a major improvement: many real life compositor implementations, discover dynamically the features of the compositor, some will have a remote desktop expensive feature.


I really struggle to believe that remote desktop is expensive to implement/run. And no, this isn't an improvement: It used to be that everyone used Xorg, so all desktops had largely the same features. There was, for example, a way to set keyboard layout that always worked (setxkbmap), and it always worked. Now there are endless different compositors, and they all have different features. Do you want to try a new option? Good luck finding out if it actually does everything you need! Do you need a particular feature? Well, I sure hope you like one of the specific desktops that supports it, because it's a toss-up which support what.


Actually it is a massive improvement: expensive niche features are now optional, features you have to discover and handle dynamically. This helps to avoid developer/vendor lock-in by 'tons of features required'.

If I am not too mistaken there are several "remote desktop network protocols", maybe the dev teams behind them could agree on a common network protocol.

And the more compositor implementations, the merrier, a bit like the x11 window managers.

I am coding mine for linux and AMD GPUs, as a hobby, in RISC-V assembly running on x86_64 via an interpreter (thanks to wayland being an IPC interface)... well until very recently, it has been more some kind of research and development of a "method" to code modular assembly projects with a minimal SDK, in other words to decide on various technical compromises requiring coding _real life_ software in order to hit the right sweet spot.


At this point I'm convinced that they're not a 'real person' and the 'Fabrice' is an operational code name for a very mature hacker collective.

Real people have to sleep at some point!


This sounds like an interesting project. Do you have any plans to publish a tutorial/journal article + source code?


> Why would someone in their right mind ever buy a Nintendo product?

Correction: Why would someone in their right mind ever buy a Nintendo product and use it accordance within the manufacturer's guidelines?

I purchased a first gen (rcm exploit) switch and I couldn't be happier with my investment.

I'm not concerned about being banned as it is never connected to the internet... for "reasons". :)


even if you do connect it to the internet and get it banned, it probably wouldn't matter if you're not planning on using it with Nintendo's online services anymore


I'm sorry... please take this adorable tribble as a consolation!


sounds like trouble


> The thesis is that immigrants have no constitutional rights because they aren't citizens...

The constitution is quite clear on this issue and it has been affirmed repeatedly over the last 100+ years by the high courts. Anyone and everyone in the world who is on US soil and subject to US jurisdiction is considered a "US Person". This status is regardless of their nationality/nation of origin, the manner by which they arrived on US soil, or any other circumstance.

As a 'US Person' they are protected by the US Constitution with only minimal exceptions; the right to bear arms[1], ability to run for public office, or vote in federal elections[2]

This is by intent and design and is a necessary cornerstone of US democracy!

This is laid out in - Article I, Section 8, Clause 18 "Aliens in the United States"

https://constitution.congress.gov/browse/essay/artI-S8-C18-8...

> The Court reasoned that aliens physically present in the United States, regardless of their legal status, are recognized as persons guaranteed due process of law by the Fifth and Fourteenth Amendments. Thus, the Court determined, even one whose presence in this country is unlawful, involuntary, or transitory is entitled to that constitutional protection

[1] Only citizens and permanent residents are allowed unrestricted access to firearms.

[2] Some districts allow pr visa holders to vote in local and state elections


You're preaching to the choir!

Despite this history, the Court is still going to have to reiterate this.


Note: original title was too long -- "Trump wants green card applicants already legally in the US to hand over social media profiles"


There's an issue with the flow you described; the party requesting verification shouldn't directly interact with the verifying agent (the state) as this leaks to the state the identity of the requesting 3rd party.

The correct flow for preserving anonymity is: the requesting party issues a challenge token to the user -- the token header describes the type of request (>=18yo?) and the token body is completely random(). The user then takes this token and has the challenge verified (signed) on their side, the signed token is then returned to the requester.

This way the state never knows the identity of the challenge issuer.

() Note that this scheme requires good faith on the part of the challenge issuer that the token body is actually random, although it would seem that a simple DH-key mechanism would patch this vulnerability.


I think it is a tradeoff between "everybody can request age verification" and "only state-licensed parties can request age verification". I don't think everybody's ID card should tell anyone if the holder is adult or not, especially wirelessly


What prevents the requesting party from saving the random bytes and then connecting with the signing party to link the user with the service?


Found a weird bug... I've got a 3 monitor setup and the background animations (rain + pinwheel) only appears on 2 of the monitors... If the window straddles two of the monitors the animations only play on one half of the window!


I was big fan of my HTC Evo, I found the 3D images to be immensely helpful when taking documentation photographs. I could take just two images and get all of the info I needed to capture vs taking ~8 from multiple angles and having to mentally envision the relative dimensions of the space afterwards.


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

Search: