Github messages for voidlinux
 help / color / mirror / Atom feed
From: MechDR <MechDR@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Package request: RustDesk
Date: Mon, 30 Jan 2023 18:55:11 +0100	[thread overview]
Message-ID: <20230130175511.NiGleb2ON1zIF9FsxwxjSCGuHsC0EAaz2IlLF7_7rWc@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41107@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1463 bytes --]

New comment by MechDR on void-packages repository

https://github.com/void-linux/void-packages/issues/41107#issuecomment-1409065787

Comment:
Well, it's open source, one can always make a fork and fix the issue, while still making the client/servers backwards compatible, so that the fork can also connect to the free servers.

To be honest, I would still use it. I use it for mostly home stuff, some remote assistance, but I'm far from paranoid. It solves an issue many people have been having with AnyDesk, like no new builds for Linux x86 (the current builds still work, but no one knows for how long), and since AnyDesk is not open source, it may suffer from similar issues, but we have no idea, since the source is not available.

If it doesn't make it in the repo, so be it, I would probably make the template myself and make a new repo on my GH. I understand the concern for security, but people have real world problems that need cheap or free solutions ASAP. I have 4 headless RPis and 2 headless rigs (a NAS and an encoder). I might set up a local RustDesk server on one of them, for my personal needs, but if I only had the 2 headless rigs, then no, probably not, I would just use the free servers. Not to mention that one of the Pi's is involved in a robot project that I sometimes test on the field and I can't bring the RustDesk server every time I test outside, that's just impractical, so yes, in that case, I'll use the free servers (shrug).

  parent reply	other threads:[~2023-01-30 17:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-15 12:44 [ISSUE] " MechDR
2023-01-05 19:36 ` notramo
2023-01-25 15:23 ` MechDR
2023-01-27 18:05 ` notramo
2023-01-30 17:55 ` MechDR [this message]
2023-02-04  4:44 ` superiums
2023-02-08 21:02 ` notramo
2023-02-09 20:00 ` MechDR
2023-02-09 21:38 ` notramo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230130175511.NiGleb2ON1zIF9FsxwxjSCGuHsC0EAaz2IlLF7_7rWc@z \
    --to=mechdr@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).