|
From a security/privacy standpoint, does this entirely replace the remarkable cloud connection on the device, or merely set up an alternate mirroring? |
Replies: 4 comments 1 reply
|
See README:
|
|
Sorry, I'm understanding that it functionally replaces the cloud, but from a security standpoint I'm trying to understand if the endpoint connection to remarkable cloud is fully replaced or this is running in parallel, where the user ignores remarkable cloud. Thanks for bearing with me.
…-------- Original Message --------
On 10/16/25 11:29 AM, Joedmin wrote:
See [README](https://github.com/ddvk/rmfakecloud#readme-ov-file):
> This is a replacement of the cloud, in case you want to sync/backup your files and have full control of the hosting environment.
>
> See the [project documentation](https://ddvk.github.io/rmfakecloud/) for setup and configuration.
—
Reply to this email directly, [view it on GitHub](#389 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AFNZ22EMYA2RPEQXPCSXZDD3X7BX5AVCNFSM6AAAAACJMLNR26VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTINZQGEZDCNI).
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
|
I see now what you mean. No it does not make any connections to the original remarkable server. Please see the https://github.com/ddvk/rmfakecloud-proxy project (it's the 1st part of using the rmfakecloud). This creates a proxy that redirects all requests to original servers using a custom CA certificate |
|
Excellent, thank you. I'll take a look. My read back at this point is that the tools here replace the tooling remarkable made for connecting to remarkable server, and it intercepts these APIs to instead point to a self hosted solution. I'll dive in more to better understand, but wanted to get an idea at a high level first. Thanks.
…-------- Original Message --------
On 10/16/25 12:30 PM, Joedmin wrote:
I see now what you mean. No it does not make any connections to the original remarkable server. Please see the https://github.com/ddvk/rmfakecloud-proxy project (it's the 1st part of using the rmfakecloud). This creates a proxy that redirects all requests to original servers using a custom CA certificate
—
Reply to this email directly, [view it on GitHub](#389 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AFNZ22ATJLX3B5NF5TCGMFL3X7I4JAVCNFSM6AAAAACJMLNR26VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTINZQGE3TIOI).
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
|
I guess reading though these two issues might give you a better idea about how it behaves (ddvk/rmfakecloud-proxy#5 and #381). It simply just redirects the requests trying to reach original server to the self-hosted one. Please note you can also enable disc encryption without any issues (I've done so myself, see #380). The only thing that cannot be fully self-hosted now is OCR (see #351) |
I see now what you mean. No it does not make any connections to the original remarkable server. Please see the https://github.com/ddvk/rmfakecloud-proxy project (it's the 1st part of using the rmfakecloud). This creates a proxy that redirects all requests to original servers using a custom CA certificate