I'm looking at megasimplesync, and from a code review point, I'm not a fan of magic-numbers e.g.:Īnd i assume its ok, but just in case, i thought to point out that there seems to be credentials hardcoded into the megasimplesync. D-BUS comes out of the box for QT see: or.
#Megasync register bonus not working Pc#
Its great, too I have MEGASync installed on my computer, which syncs files to my MEGA Account, so I can instantly continue playing on my PC what I started on my phone, and vice versa. That way megasync integration is available to anything that has a dbus library, and that can run a dbus service (linux, windows, and OSX). It works with various cloud hosting services, including MEGA and OneDrive. I would suggest it would be easier to implement extserver as a D-BUS listener for IPC rather than hand roll your own hand rolled listener. If i can give some constructive criticism, after reviewing the general approach and the code? I will look into it what i can do with it, i guess i can do something with the mega.socket after digging into the megasync code. In the source code of that tool you can see callbacks that provide the state of all files: We might provide a command-line tool to get that information in the future, but it isn't one of our current priorities, sorry.Īnother option would be to use megasimplesync, that is a command line tool that uses the same sync engine as MEGAsync. You can take a look at these files to see how it works: It would be possible to use the same interface as our extension for Nautilus to get that information. Currently, that information can only be seen in the GUI or in Nautilus thanks to our extension. We still don't have any tool to query the state of the service or individual files or folders.
Currently, MEGAsync only acceps -version and -debug (to print logs to stdout).
0 kommentar(er)
