• 0 Posts
  • 15 Comments
Joined 1 year ago
cake
Cake day: June 1st, 2023

help-circle



  • I’m far from an expert, but I don’t know of rclone doing versioning, or a continuous sync like syncthing. Also haven’t used proton, so take my thoughts with a grain of salt.

    Stage 1 Run rclone config to set up the proton remote. rclone config should take you through a wizard and will eventually ask you to authenticate somehow with the remote. Once that is done and saved, you’ll exit the rclone config wizard and be back at the command line.

    Then you would run a test command like: rclone ls :

    If it worked, you should see a list of files/folders on Proton. If not, you’ll have to go back to rclone config and edit the remote to fix whatever went wrong.

    Stage 2

    Test out copying the folders with a command something like: rclone copy localfile/folder remotename:remotepath

    Do some testing to get the hang of the command, but it is pretty straightforward.

    Stage 3

    I don’t know how many files or how big the files are, but I assume not too many and not too big. I also don’t know which version of Linux you have, but I assume you have access to systemd, cron, or both.

    You’ll make a basic shell script that runs the command you practiced in stage 2. Easy peasy, put it in a text file with a shebang at the beginning, make it executable, and give it a go. It should run exactly how it did when you typed the command out manually.

    Finally, you will write a systemd timer or a cron/crontab entry to execute that script at some frequency.

    So just to summarize:

    1. Setup the proton remote in rclone using rclone config
    2. Test out copying files to proton through rclone
    3. Write a basic shell script that runs the command to copy files from the desired local folders to the desired proton folders.
    4. Use one of the tools on Linux that lets you schedule the execution of scripts to automate running your copy to proton script as frequently as makes sense to you.






  • Amazon is moving away from Android. This move isn’t exactly surprising. It is disappointing though, imo. From my limited testing, I was able to side load an xmpp app on Android and message, voice call, video call seamlessly. In theory, the ability for developers of some types of apps to target Android and reach Windows without writing a touch of Windows-specific or accommodating code was a huge opportunity for open source developers to effortlessly reach cross-platform audiences.



  • I did back of the envelope math a while back where if active users of large self-hosted communities (such as /r/selfhosted) put $5/month into donations to the most used self-hosted software projects, ~20 projects could get ~$75,000/year of income. Not enough to build a company around, but enough to live well on in many parts of the world as a sole developer or enough for a maintainer to pay for other developer contribution.

    I think the open source community fails to organize around the fact that development and maintenance isn’t free, but that as a massive user group, it takes minimal contribution from each to make an impact. Can better messaging and “structure” break the free rider problem?