Sorry, if I'm understanding but you still mean for syncing with the Android device? No, as we said there is not even any file to do that with. It's in a little database which cannot be used the same way. This makes it efficient for the limited Android system. This is why it's not what you want, and I'm not convinced that you totally understand. Sure if you're a developer you could try writing an app (not from this codebase) that handles it as the same xml as windows, try to make it compatible with MLO, and then use the file-sync method (assuming you can with limited resources), but it is not possible for them to do with the current MLO for Android. BTW there is a different team, "the Android team" apparently who created that app, not the team who works on Windows version so it's even more complicated.
I recommend solving the WiFi sync instead. I forgot to mention an important limit to this FTP sync I described is not anything like the cloud sync or wifi: It is only entire data of one device or the other. There can be NO two-way sync of individual tasks this way, in case something even unrelated was changed on both. You would lose everything you did on the device that didn't have the latest change. Can only use one at a time, save it, sync, then use the other. Tedious and the WiFi sync is similar, not automatic nor seamless. Yes I would like to see them build an entirely different thing so we can solve our sync limitations as well as the scripting support I keep mentioning for years, but I doubt they can find a way to profit from it, so why spend the millions? We would profit by no need paying them for the other stuff (I keep forgetting I could not use free MLO for Android in order to wifi-sync). I guess that's why it's up to us. It's just not easy to do, I don't think it's worth building our own thing "like MLO" but I think you agree just something to interface but that's where the need for scripting or API comes in, which is what they haven't designed MLO to work with. We're not talking "add a feature" in any case here. I wish I had the protocol specs for the WiFi Sync so I could communicate my own sync with Android MLO. I actually started MyLifeOrganized at the very first release (was no version number) before smartphones existed (dumb phone was just called my phone) and it was cool using a Windows-based PDA (I used iPAQ) because we did have a file to sync (and did more than just copy the file) but if I recall, it was a mini-version of data file, stripped down to smaller size so couldn't have everything in it. Of course that's because the PDA also had very limited resources. So, about taking responsibility to solve these, I agree with you. That open-source thing is what I am suggesting at least as something that works with MLO hopefully not need to replace it. That's why the WiFi Sync protocol seems important to understand. On Sunday, July 28, 2024 at 6:00:14 PM UTC-6 Hugo González Castro wrote: > Hello imajeff, > > The FTP sync you describe, is exactly what I want and what would solve all > my issues. That's why I suggested it. I personaly only use one device at a > time, but need to sync several devices at different locations, that > sometimes are not turned on at the same time. The easiest solution for me > is having a centrallized place to have the latest version of my file. Each > time I use any version of the app, it would be enough for me just to check > the date and keep the latest version. I have no need of complex individual > task sync. Just a place to keep my latest file. The FTP sync currently > works fine for Windows devices, but it is not implemented for Android > devices. That is just what I would love to have, and it is as simple as I > described: the full file in a common XML format (for Windows and Android > devices) in a centralized place. > > I totally understand the issues that may happen with that kind of sync, > they already have them under Windows devices... I just suggested including > the Android devices to that. The reason why the WiFi sync is not valid for > me is because that requires both devices to be turned on at the same time. > As I said, some of mine are at different locations and would be a huge > inconvenience to keep them turned on just for syncing... it is more > convenient just having a centralized place for the latest version on the > cloud. Of course, I can use my own NAS to have my own cloud and my own FTP > server, no need to use a VPN nor somebody else's cloud. > > About doing the stuff myself and taking responsability, I think that > fixing the source code of an open-sourced project myself to be able to > export my data to MLO is somehow good enough. I would be glad to fix the > source code of MLO myself to implement this stuff, as I work as a senior > developer... but it is not reasonable to expect the MLO team could give me > access to their source code... I don't blame anyone, I just suggested a > feature that would make a lot of sense for me. Of course, they can reject > the suggestion, no problem with that. > > Human nature is funny indeed, especially when assuming things about other > people... > > El domingo, 28 de julio de 2024 a las 17:34:06 UTC+2, imajeff escribió: > >> Hi, I hope that I can help clarify something I think is missing in the >> discussion. There is a big reason to say the FTP "would not work" and we >> are not at all saying "oh the feature just hasn't been written yet". >> >> The FTP feature on desktop, or should we say the feature that can sync >> with any external ml file, is not doing what you think it is doing (I >> suspect). Yes if you synchronize tasks instead of a file, say in the form >> of exchanging XML elements then I think that's a good idea. You don't need >> MLO to do that for you as you already have the .ml file which is XML. In >> fact years ago they were encouraging us to do whatever we want by >> processing and editing the XML so even the company won't complain. >> But as I was saying, the FTP is not doing anything whatsoever like that. >> The feature has no clue what is inside of the ml file, no need for knowlege >> of XML elements for it to just say basically this: >> Connect via FTP and look at two files by name. >> Which file has a newer timestamp? >> OK transfer that via FTP and overwrite the other file. >> This is the only reason it is not possible to use any of that feature, >> what-so-ever, in any implementation to sync with Android version. >> >> So, why not just use the WiFi Sync feature? It really has nothing to do >> with wifi but to use the TCP or UDP instead of FTP and actually sync tasks >> instead of just whole ml file. Should have been called LAN Sync instead. >> LAN stands for Local Area Network, and people just think of it as the >> internet in their home or work but of course only local. >> That is actually what you are looking for, and I used it regularly to >> avoid the cloud. >> There still is a limitation being local, that the Android IP address has >> to be on the same local subnet as the desktop, but hey you can fix that >> using your own VPN, which I think is the most useful thing VPN has ever >> done. This is all about security, so either this is what you want, or you >> are really fine just using somebody else's cloud for synchronizing MLO. >> >> I would be happy to help point others in the right direction to learn all >> these details, but to be secure you really need to do the work yourself. >> Here it is, the most important thing you need to protect yourself, but why >> do so many avoid the responsibility by saying some other company should be >> securing them... so we can blame them instead when it goes wrong? heh, it's >> a funny thing in human nature. >> On Friday, July 26, 2024 at 3:23:36 PM UTC-6 Hugo González Castro wrote: >> >>> Hello Alex, >>> >>> Thank you for your explanations! Actually, I am not trying to use the >>> FTP to sync with Android, mainly because the Android app doesn't have that >>> feature. It was more like a feature suggestion... >>> I understand the formatting issue, but they do not need to upload the >>> native binary file from each platform... I was thinking in a standard file >>> format they could have in common (the desktop and mobile apps), like the >>> XML export. >>> >>> I personaly have a batch file in desktop to export my tasks to XML and >>> keep those in a version system, where I can check and compare individual >>> changes on the files and so on.I personally migrated my data from >>> AbstractSpoon >>> ToDoList to MyLifeOrganize, via XML ( >>> https://www.youtube.com/watch?v=iPk2ZN5e27Q ), so I always keep >>> everything in XML just in case MLO goes out of business, in order to be >>> able to migrate back my data to TDL... Sorry but my data is the most >>> valuable asset for me, I cannot put all eggs in one basket... >>> >>> Of course, if they implement something like that, I'd better use Dropbox >>> or similar, but FTP still have the advantage of privacy, as you said.But it >>> would be enough for me that the Android app just where able to select a >>> different local file to open in XML format, one that I can take from >>> Dropbox for example. That way I could at least read with the mobile app the >>> changes I made with the desktop app... Do you know any way to import data >>> from a file in Android, without using the MLO Cloud? >>> >>> Regards, >>> >>> Hugo >>> >>> El viernes, 26 de julio de 2024 a las 20:23:58 UTC+2, Alex escribió: >>> >>>> Hi Hugo, >>>> >>>> Unless I misunderstood what your trying to do, based on my >>>> understanding FTP sync for desktop to Android would not work. MLO desktop >>>> database file is different format from Android database file. I believe >>>> when you sync to MLO cloud there is most likely some sort of conversation >>>> service running which converts data received from desktop database into >>>> proper format necessary for Android database file. If MLO android used >>>> same >>>> database file as the desktop version than we wouldn't need FTP sync as >>>> there are various sync type apps which are much better than FTP, enable >>>> direct push sync from desktop to mobile, but unfortunately the database >>>> files are different. >>>> >>>> Personally I would love to see MLO release a sync app that advanced >>>> users can install/run as a sync service on their local network that does >>>> not depend on AWS MLO Cloud while offering same capabilities and benefits >>>> that MLO Cloud sync does. I wouldn't mind paying yearly subscription for >>>> support of sync app just like you would need for MLO Cloud sync. The value >>>> I see in this is for those that are more privacy security conscious and do >>>> not wish to depend on 3rd party cloud service. Last few weeks we saw >>>> significant amount of tech systems go down which affected many >>>> organizations relying on cloud type services including situation that >>>> impacted major dealership groups as well as the recent event with >>>> Crowdstrike. Of course I realize that resources are needed for alternative >>>> options and I assume MLO team has other priorities in mind. Staying >>>> hopeful. >>>> >>>> Regards, >>>> Alex >>>> >>>> On Friday, July 26, 2024 at 3:14:59 AM UTC-4 Hugo González Castro wrote: >>>> >>>>> Hello, >>>>> >>>>> I've noticed that the Windows app offers the option to sync files >>>>> through a personal FTP site, which is a really impressive feature. >>>>> However, >>>>> it appears that this option is not available on the Android app. It would >>>>> be fantastic to see FTP sync support implemented in the mobile apps as >>>>> well. >>>>> >>>>> I'm currently subscribed to the MLO Cloud, but I've been experiencing >>>>> some synchronization issues recently. Having the ability to use an >>>>> alternative service like FTP sync would be extremely beneficial, >>>>> especially >>>>> during times when the primary service is facing challenges. >>>>> >>>>> Thank you for considering this suggestion! >>>>> >>>>> >>>>> -- You received this message because you are subscribed to the Google Groups "MyLifeOrganized" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/mylifeorganized/bbc666bc-31b1-4da2-a042-c724ba7dfb5an%40googlegroups.com.
