[spacedesk Marcel]

This is a technical support forum.
This is not a discussion forum about business ethics.
We consider this post as spam.
We will block this user if he will continue to spam the forum.

• This reply was modified 1 day, 23 hours ago by spacedesk Marcel.

[spacedesk Marcel]

It has been observed that some USB cable drivers cause BSOD (Blue Screen of Death) when used with USB Tethering and spacedesk (probably they have issues with too heavy load). Nothing we can do about this. For Android, we have an alternative, though: We developed our own USB driver for native USB support. You only need to enable checkbox “USB Cable Android” underneath “Communication Interfaces” in spacedesk Driver Console on Windows PC.

[spacedesk Marcel]

This is a support forum.
We do not have resources to discuss general security fundamentals.
Very simple statement to wrap up this topic:
Everything can be hacked or privacy corrupted if the attacker has high enough skills, resources and focus.
All anyone can do is reduce attack surface.
Mouse/touch remoting attack surface is magnitudes less than keyboard.

• This reply was modified 3 weeks, 2 days ago by spacedesk Marcel.

[spacedesk Marcel]

Short comment to your statement 2) above:
Are you talking about Windows Software Keyboard?
The on-screen keyboard which needs touch/mouse to operate?
This does not have much of an attack surface for various reasons:
– Most important: Mouse and touch cannot be scripted to operate keyboard in an automated way
– Opening of Windows Software Keyboard will not go by unnoticed in mirroring operations
– etc.etc.etc.

[spacedesk Marcel]

You did not listen to what Christian was saying:
– We DO HAVE hardware encoding (h264) up and running experimentally (but not released)
– NO PERFORMANCE GAIN by hardware encoding for more than 80% of spacedesk users
– On some of the GPUS you mention, our current software encoding performs way better
– Release for less than 20% of the users needs to be precisely targeted

Don’t confuse users whith such a non-applicable statement:
“…no one is talking about… h264 format, because it is outdated….”
(public common knowledge quoted in the wrong context without understanding)

THIS IS TRUE ONLY for REGULAR STREAMING applications (e.g. Netflix)
No time limit for encoding in a studio.

THIS IS COMPLETE NONSENSE for REAL TIME STREAMING applications (e.g. spacedesk, Miracast, etc.)
Need superfast encoding to avoid immediately visible lag.

For REAL TIME STREAMING applications like spacedesk hardware encoding (typically h264/265) is still too slow on the vast majority of current GPUs in the market. CPU accelerated encoding can still perform better. Look: Today, in REAL TIME hardware encoding there isn’t much of a difference between h265, h264 and even MPEG2 (predecessor of the alledgedly outdated h264). That’s why e.g. Miracast until today still uses MPEG2 for hardware encoding.

PS: You might also want to understand the bottleneck in spacedesk is REAL TIME ENCODING performance – not DECODING. Thus it is not relevant what news you read in the press about fancy hardware accelerated DECODING.

• This reply was modified 1 month ago by spacedesk Marcel.
• This reply was modified 1 month ago by spacedesk Marcel.
• This reply was modified 1 month ago by spacedesk Marcel.

[spacedesk Marcel]

Please read the instruction manual underneath above page menu “Documentation” ( https://manual.spacedesk.net ). Chapter “UNINSTALL ON WINDOWS PRIMARY MACHINE” contains very detailed information about uninstall, troubleshooting uninstall and an overview of all spacedesk components.

We cannot understand your statement: “…installing and opening ice without permission.” What is this supposed to mean? How is it related to spacedesk? Nobody else reported anything like this before.

PS: There was a minor issue in some old spacedesk versions: A small user interface component was observed to survive Windows system reset. This did neither do anything bad nor anything good. Nor were there any functional spacedesk components left after Windows system reset. This issue should have been fixed quite some time ago. Contemporary spacedesk versions should be completely wiped out by Windows system reset.

• This reply was modified 1 month, 1 week ago by spacedesk Marcel.

[spacedesk Marcel]

Currently spacedesk does not support HDCP (High-bandwidth Digital Content Protection).
Evaluation and possibly implementation would be a huge effort.
We can only move into this direction if there is a large scale corporate customer who has enough budget for funding this (this is actually the way how most existing spacedesk features were developed).

[spacedesk Marcel]

Thank you very much for pointing out this issue.
We were not aware of this specific situation.
We intend to fix it in a different way:
We will support arrow keys even in free non-commercial version of spacedesk.
Thus TV remote control keys should work for all spacedesk licenses (no matter if business or non-commercial).
We will soon release spacedesk DRIVER version 2.1.15 which will include the above named fix.
Please let us know if this solves your problem.

[spacedesk Marcel]

This feature is already on our long term list of TODOs. It is not to be expected any time soon because of other short term tasks with higher priority.

[spacedesk Marcel]

No. Black and white color has nothing to do with license.
It is because the BETA version expired. Please look at the post below:

Black and White Image: EXPIRY of BETA VERSIONS!

• This reply was modified 3 months ago by spacedesk Marcel.

[Author]

Posts