leetnewb

Perfect is the enemy of good. There is no scenario where cars are getting banned in most of the world where EVs are being sold.

If safer is a realistic outcome, perhaps things would further evolve. Ride share cars today are dual-use vehicles that typically carry driver + no passenger or driver + one passenger with the capacity for 3-5. If future autonomous ride share cars turn out to be dedicated to ride share, maybe most would end up being 3-wheel with just one or two seats. Shrinking the size of a substantial potion of cars on urban roads could be beneficial to road safety, power/carbon intensity, road capacity/density (which could also lead to more equitable road use for bikes and pedestrians).

ShieldsUP is fine. Also check out: https://www.routersecurity.org/testrouter.php

You could also just port scan yourself with something like nmap.

Even just watching other open source projects go through it is demoralizing to me, and I'm not a contributor.

Also attributed to burnout.

Apple has turned out to “prevent the chrome monopoly” far more effectively then firefox has.

Turns out that owning the platform (Android, iOS) counts for a lot. I like having an independent option.

Pretty sure he is a meaningful sponsor of PHP.

edit: https://thephp.foundation/ https://opencollective.com/automattic

Technically true, but FOSS isn't "free" in the sense that someone is contributing labor to build and maintain the software. Free to use, but not free to make. I personally wouldn't expect or shame a person for using FOSS without contributing. But if you make a profitable business off a FOSS project, it seems reasonable to expect some form of contribution back to the project - not because it is technically required, but because who better to sponsor a project than someone profiting from it?

If you can host thelounge on your LAN and access it over VPN on the go, it makes for a very nice IRC experience.

Otherwise, ssh (termux or whatever) to your irc host running irssi or weechat

I haven't used either command, but based on what I see in the manual, rcd tells rclone to start listening for remote commands whereas rc is used to issue remote commands.

Try it out by going to a folder with some files and typing: rclone rcd .

That should open a tab in your web browser with a list of your files.

There are situations where being able to send commands to rclone remotely would be helpful, but I'm not sure that you need to do that in this case.

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.

All three of those links are very outdated - I do not recommend trying to use any of them.

Can you be more specific about what you are trying to do exactly? I know rclone is confusing to get started on, in part because it does so many different things and the documentation requires some background/outside knowledge.