Publish sources on github?

[indeyets]

Is there any chances that you could publish source files on github and move bundles to releases? it would be much easier to trace changes this way.

I see that install script:

1. decodes bundles with openssl
2. unpacks with tar
3. replaces "cache" files on the device

so, I suggest to put contents of tars in github, not actual "compiled" bundles

[Eeems]

Publishing the sources would be a good way to get reMarkable to take action against this.

ddvk/remarkable-hacks#496 (comment)

[mb1986]

I don't want to put publicly anything which may be visible as part of rm code hence unfortunately, it will not be possible to do what you are asking for.

Furthermore, you are right, the steps you have provided are exactly what install script does.

I'll try to use releases as you've suggested :)

[mb1986]

Is there anything else to discuss in relation to this issue? If not I'll close it soon.

[Gaibhne]

I think @indeyets like most people asking about this is mostly concerned with what happened with ddvk - the top/only maintainer burning out or vanishing, and the users being left standing in the rain. Is there any way you could clarify in what goes into creating the actual binary patch things in a way that would allow an interested party to take over or possibly even help with creating the patches ? If the issue is with the RM code itself, for example, maybe an approach would be to publish .diff files or something of that sort ?

If nothing like that is possible, and you feel like you can't or shouldn't provide any further details on how the actual patches are made, then it does seem like closing this might be the best option.

[mb1986]

I totally agree with you both, that is why I have started a Discord, meet with people to raise a team that there are more than one person knowing "the magic" ;) There are currently a couple folks working on that with me. Nonetheless, it is not possible to give access to everyone unfortunately. We/I will try to maintain this hacks as far as it is possible. On the other hand please understand that we are doing that in addition to our full time jobs and sometimes things will take some time to be developed/released.

On the .diff note - it is not as easy as that :P Happy to discuss that further ;)

[Gaibhne]

Totally understandable on all points.

One last item from me to add: I saw your call for the Discord, and considered showing up, but in the end I didn't because I thought "what are the odds that my skillset would match what is needed ?". So I would suggest that, if it seems wise, a rough list of technologies involved would be added to this issue or even the FAQ - something in the style of 'If you would like to help, and know some Python/Rust/Brainfuck, join the Discord'.

[ard0gg]

FWIW I have pretty basic coding skills, but I know my way around Linux pretty well, have an RM2 and occasionally some time. I was able to contribute just by testing out v0.01 on my RM2. No coding needed. There can be more ways to contribute than just writing code.