| Blog |
|
| Releases |
Page:
0 1 2 3 4 ... 5 ... 10 ... 15 ... 20 ... 25 ... 30 ... 35 ... 40 ... 45 ... 50 ... 55 ... 60 ... 65 ... 70 ... 75 ... 80 ... 85 ... 90 ... 95 ... 100 ... 105 ... 110
| Scribe native export | |
|---|---|
|
Date: 8/3/2023 Tags: scribe | There has been a long running branch of Lgi and Scribe to remove the old synchronous way of doing dialogs as part of the work to re-enable Haiku support. And I decided the cost of keeping the branches separate was too high and merged all those changes into the main dev branch of those projects a few weeks back. This means that a bunch of old functionality that I haven't touched in a long time is now broken. For instance the Scribe mail3 export function. So I spent the last few days fully re-writing that to use the modern patterns and also optimize things a bit. Which has all been reasonably successful. It even has a nice new completion dialog: In that example I'd run it earlier and the replication had nothing to do. It's designed so you can use it to backup your folders and it's reasonably intelligent about replication of items. In terms of when there'll be a new release. There are a bunch more dark corners of Scribe that I never test, and they all need to be looked at. I'll keep working me way through them. |
| (0) Comments | Add Comment | |
| i.Disk on Haiku | |
|---|---|
|
Date: 20/2/2023 Tags: i.Disk | 
|
| (0) Comments | Add Comment | |
| Phabricator fork and the Scribe code base. | |||||||||
|---|---|---|---|---|---|---|---|---|---|
|
Date: 3/5/2022 Tags: scribe opensource | No one cares, but the announcement on 1st April wasn't a joke. Scribe is actually going open source. It's just taken way longer than I expected to create a new mercurial repository and have the hosting work correctly. Part of the issue is that my Phabricator install was misbehaving and it took a while to fix. I've had to create a fork of Phabricator and fix the passing of arguments to hg's web-server. I also had to clear out all the proprietary stuff in the Scribe code base, do some cleanup and get it all building again. Mostly that boils down to the OAUTH2 client secrets (good bye Gmail support) and the InScribe key checking code. That work is mostly complete now so I can publish the code base. It lives here: https://phab.mallen.id.au/source/scribeopensrc/ I'll be adding some more info on how to get it to build and updating the Scribe home page over the next few weeks. But it's slow going cause I have very little energy at the moment. I'm on day 14 since I got my first covid symptoms. Which have all cleared up bar the tiredness. Fortunately no one else in my family got it. Oh yeah, I've moved the versioning for the open source tree to "v3.x.x" just to make it clear where the new builds come from. The v2.4.22 changes will be rolled into a v3.0.0 build soon. As I won't make that build off the proprietary code base. Well ok, but how do you build it? hg clone https://phab.mallen.id.au/source/scribeopensrc/ code/scribe/trunk python code\scribe\trunk\build.py Should get you most of the way there. That currently just supports Windows but I will extend that support to other OS's as soon as I can. Requirements look like:
| ||||||||
| (2) Comments | Add Comment | |||||||||
| Scribe... | |
|---|---|
|
Date: 1/4/2022 Tags: scribe | ...is going open source. There will no free / paid versions. Just the full build available for free. Donate if you like. |
| (0) Comments | Add Comment | |
| i.Disk cross platform release | |
|---|---|
|
Date: 2/3/2022 Tags: idisk | i.Disk is now available on all 3 platforms: Windows, Mac and Linux. There is a roll up of all the changes over the last 2 years. Mostly aimed at better updating of status during a scan and cleaner listing of folders and drives including their free space and total size. This also marks my first attempt at distributing a Linux based appimage. It would be interesting to see if it runs on a variety of Linux systems. |
| (3) Comments | Add Comment | |
| IMAP Gmail support in Scribe | |
|---|---|
|
Date: 15/8/2021 Tags: Scribe Google | This is an update on the support for Gmail IMAP connections. I'm sure that if you have tried to connect to Gmail with Scribe you get a warning about the app being "unverified". You can click into the advanced section and bypass that warning to get access. But as of right now that is limited to 100 users (of which 81 have taken advantage of bypassing the warning). So very soon that will not be a valid path to gaining access to Gmail from within Scribe. So this verification process? What's involved? Well you have to tick certain boxes. Things like having a homepage that meets certain criteria, having a privacy policy that states what you'll do with the user's data. And also using certain "scopes" that Google deem responsible. And that's where the trouble starts. Because Google (more specifically the app verification team) on one hand wants the apps to use fine grained scopes like "https://www.googleapis.com/auth/gmail.modify" but if you actually try and implement that you find that the OAUTH2 process fails with a scope error. If you then revert to using the more broad scope of "https://mail.google.com/" you can create a connection but the app verification team won't accept the app on the basis of the scope being too broad. They then contend that you should re-implement your client using the native Gmail restful API. The native API? Really... just implement a whole backend to support one company's server? The whole point of IMAP and SMTP is that the client supports ONE protocol used by everyone. This would be a lot of work to support just one service. And even then Google states that you SHOULDN'T do that here: https://developers.google.com/gmail/api/guides. What is one to do? Well right now. Nothing. Nothing can be done, Google have painted all the email client developers into a corner where there is no way forward. Some mutually exclusive options that don't work for us. What should they do? Probably enable the gmail.modify scope for IMAP and then allow apps to use than and be accepted for verification. Is that going to happen? Probably not. For reasons unknown. Google is now far to large and political to get things like that right. So at some point Gmail support will just cease to work anymore and there is nothing I can do about it. I'm considering just yanking it out completely. The office 365 support has also been borked for a long time for extremely similar reasons... "use our proprietary API not this well known standard". And beyond Google and Microsoft there aren't any other OAUTH2 services I tried to support. (Am I missing something?) |
| (1) Comment | Add Comment | |