gnome-online-accounts issueshttps://source.puri.sm/Librem5/gnome-online-accounts/-/issues2023-10-22T17:21:36Zhttps://source.puri.sm/Librem5/gnome-online-accounts/-/issues/3Feature Request: Enable CalDAV and CardDAV independent of Nextcloud2023-10-22T17:21:36ZChris TalbotFeature Request: Enable CalDAV and CardDAV independent of Nextcloud However, there does not appear to be a way to connect to a CardDAV and CalDAV provider outside of Nextcloud (in my case, I use Fastmail). It would be nice to have those features broken out, so one can access a CardDAV and CalDAV provide... However, there does not appear to be a way to connect to a CardDAV and CalDAV provider outside of Nextcloud (in my case, I use Fastmail). It would be nice to have those features broken out, so one can access a CardDAV and CalDAV provider independent of Nextcloud. Nextcloud allows use of contacts and calendar through CardDAV and CalDAV, so the underlying functionality is present within GNOME, there just needs to be the GUI option added. https://source.puri.sm/Librem5/gnome-online-accounts/-/issues/12Can't setup Librem One connection2022-12-12T22:52:04ZDan ManCan't setup Librem One connectionWhen trying to login, I get the error: **TLS connection closed unexpectedly**. Interestingly, if I provide a wrong password, it tells me the credentials were wrong.When trying to login, I get the error: **TLS connection closed unexpectedly**. Interestingly, if I provide a wrong password, it tells me the credentials were wrong.https://source.puri.sm/Librem5/gnome-online-accounts/-/issues/13librem.one provider and adaptive patches need to be forward ported2023-06-21T09:10:27ZGuido Guntherlibrem.one provider and adaptive patches need to be forward portedhttps://source.puri.sm/Librem5/gnome-online-accounts/-/issues/11Squash patches2021-02-24T08:18:10ZGuido GuntherSquash patchesbefore:
- Add-Icons-for-Librem-One.patch
- Add-initial-Librem-One-provider.patch
- goabackend-Make-dialogs-resizable.patch
- goabackend-Reduce-margin-around-the-UI.patch
- libremoneprovider-Shorten-Librem-One-Address-to-Address.patch
a...before:
- Add-Icons-for-Librem-One.patch
- Add-initial-Librem-One-provider.patch
- goabackend-Make-dialogs-resizable.patch
- goabackend-Reduce-margin-around-the-UI.patch
- libremoneprovider-Shorten-Librem-One-Address-to-Address.patch
after:
- goabackend-Make-dialogs-resizable.patch
- goabackend-Reduce-margin-around-the-UI.patch
- Add-Icons-for-Librem-One.patch
- Add-initial-Librem-One-provider.patch (eats libremoneprovider-Shorten-Librem-One-Address-to-Address.patch)https://source.puri.sm/Librem5/gnome-online-accounts/-/issues/10Needs an adaptive and unsloppy build for byzantium2021-02-23T13:19:59ZGuido GuntherNeeds an adaptive and unsloppy build for byzantiumIf this package can't use the version in byzantium (currently 3.38.0-1) please provide an adaptive (working on laptop and phones) and unsloppy build. See pureos-store#4.
Besides adaptiveness patches we have the librem.one goa provider o...If this package can't use the version in byzantium (currently 3.38.0-1) please provide an adaptive (working on laptop and phones) and unsloppy build. See pureos-store#4.
Besides adaptiveness patches we have the librem.one goa provider on top.https://source.puri.sm/Librem5/gnome-online-accounts/-/issues/9Don't hardcode @librem.one2020-11-16T12:35:03ZGuido GuntherDon't hardcode @librem.oneThe current provider does that, we should make it default to @librem.one but allow users to specify their own domain
/cc @david.seawardThe current provider does that, we should make it default to @librem.one but allow users to specify their own domain
/cc @david.seawardhttps://source.puri.sm/Librem5/gnome-online-accounts/-/issues/8Document how to access GOA-based credentials2020-03-25T14:57:45ZDavid SeawardDocument how to access GOA-based credentials**User story:** I am a third-party developer. I want to authenticate my application against a Librem One server.
**Proposed solution:** Implement this in Liberty CLI.**User story:** I am a third-party developer. I want to authenticate my application against a Librem One server.
**Proposed solution:** Implement this in Liberty CLI.https://source.puri.sm/Librem5/gnome-online-accounts/-/issues/7Please use "ldh" for variables and "Librem One" for labels2020-03-13T14:15:26ZDavid SeawardPlease use "ldh" for variables and "Librem One" for labels**User story:** I am a third-party developer. I want to interact with Librem One components in a generic way, so that I can handle users who use a different provider.
**Background:** We distinguish between Librem One (the flagship brand...**User story:** I am a third-party developer. I want to interact with Librem One components in a generic way, so that I can handle users who use a different provider.
**Background:** We distinguish between Librem One (the flagship brand and domain for services provided by Purism SPC) and other Liberty Deckplan Hosts (which hypothetically offer identical services at different domains/brands/providers). Because these alternatives don't exist today, we make minor implementation decisions that allow us to deliver a product now without inadvertently creating vendor lock-in at a future date. To date we use this strategy:
* For user-facing labels, we hard-code "Librem One" branding, logos etc. At a future date we will investigate options to tweak this branding at a packaging level, but GOA implementers don't need to worry about this today.
* For developer-facing interfaces, we use the "ldh" prefix rather than "librem", "libremone" or anything like that. **This means that as branding gets tweaked the implicit api does not change.**
**Suggested solution:**
The developer-accessible variables such as provider type should be renamed to "ldh" rather than "librem_one". For example, from https://source.puri.sm/Librem5/gnome-online-accounts/commit/9bf83a785b47277925aa46deeaa7de9fa5cdecb2 :
```
# librem.one
AC_DEFINE(GOA_LIBREM_ONE_NAME, ["librem_one"], [ProviderType and extension point name])
AC_ARG_ENABLE([imap-smtp],
[AS_HELP_STRING([--enable-librem-one], [Enable librem.one provider])],
[],
[enable_librem_one=yes])
if test "$enable_librem_one" != "no"; then
AC_DEFINE(GOA_LIBREM_ONE_ENABLED, 1, [Enable librem.one data provider])
fi
```
becomes something like:
```
# Librem One or other Liberty Deckplan Host
AC_DEFINE(GOA_LDH_NAME, ["ldh"], [ProviderType and extension point name])
AC_ARG_ENABLE([imap-smtp],
[AS_HELP_STRING([--enable-ldh], [Enable Librem One or other Liberty Deckplan Host])],
[],
[enable_ldh=yes])
if test "$enable_ldh" != "no"; then
AC_DEFINE(GOA_LDH_ENABLED, 1, [Enable Librem One or other Liberty Deckplan Host])
fi
```
**Notes:**
* For user-facing prompts it is obviously much simpler to just refer to "Librem One" rather than the verbose "Librem One or other Liberty Deckplan Host". This is perfectly acceptable. We may revisit this in the future, but this is definitely the fairest, fastest, simplest way forward for now.
* Prompt for credentials. In user-facing prompts we ask for "Librem One address" and "passphrase" (or just "address" and "passphrase"). We don't refer to "name", "username" or "password".
* Validating address. The address must be a valid email address with no special characters. If your framework can already validate email addresses, just use that method. Otherwise use these simpel rules: alphanumerics, followed by `@`, followed by alphanumerics, at least one period, and more alphanumerics-or-periods.
* Determining host. We determine the host from the address by splitting at the single known `@`. So `prefix@example.com` becomes `prefix` and `example.com`. Never hardcode "librem.one".
* Once you have validated and decomposed the credentials you should have:
* Address. Full address used for authentication.
* Passphrase. Passphrase used for authentication.
* Host domain. Host domain, used to make online queries, attach subdomains, etc.
* The host will handle any further validation requirements (valid characters in username/passphrase, correct subdomain, etc).
/cc @tobias.bernardhttps://source.puri.sm/Librem5/gnome-online-accounts/-/issues/6Extend goa to handle xmpp (again)2020-03-12T18:36:07ZGuido GuntherExtend goa to handle xmpp (again)Support was there for telepathy (but that got removed), we want it for chatty/libpurple
/cc @andrea.schaeferSupport was there for telepathy (but that got removed), we want it for chatty/libpurple
/cc @andrea.schaeferhttps://source.puri.sm/Librem5/gnome-online-accounts/-/issues/5Extend librem.one provider to handle files/calendar/contacts2020-03-12T18:20:22ZGuido GuntherExtend librem.one provider to handle files/calendar/contactsDetails upcoming.
/cc @david.seawardDetails upcoming.
/cc @david.seawardhttps://source.puri.sm/Librem5/gnome-online-accounts/-/issues/4libreme.one dialogs not adaptive2020-11-14T08:52:08ZGuido Guntherlibreme.one dialogs not adaptiveThe account dialog is too wide (and basically copied from another provider) but the dialogs look out of place overall
@tobias.bernard is there design work already?
@mohammed.sadiq could you help with making it adaptive? It seems the g...The account dialog is too wide (and basically copied from another provider) but the dialogs look out of place overall
@tobias.bernard is there design work already?
@mohammed.sadiq could you help with making it adaptive? It seems the goaprovider base class could be improved already to use a full screen sized dialog instead of the tiny one?https://source.puri.sm/Librem5/gnome-online-accounts/-/issues/2enable librem one2020-01-30T10:06:37ZGuido Guntherenable librem onewe could then enable it in gnome-intial-setup on the librem5 as well: https://source.puri.sm/Librem5/gnome-initial-setup/merge_requests/2we could then enable it in gnome-intial-setup on the librem5 as well: https://source.puri.sm/Librem5/gnome-initial-setup/merge_requests/2https://source.puri.sm/Librem5/gnome-online-accounts/-/issues/1Remove $bigcorp names from list of online accounts to connect2020-04-17T11:55:17ZHeather EllsworthRemove $bigcorp names from list of online accounts to connectAs seen in [this video](https://youtu.be/kSexi9gX2c0), you still see a list of big companies whose accounts you can connect (Google, Facebook, etc.). This issue is to track the efforto to *remove* those unwanted companies from the list i...As seen in [this video](https://youtu.be/kSexi9gX2c0), you still see a list of big companies whose accounts you can connect (Google, Facebook, etc.). This issue is to track the efforto to *remove* those unwanted companies from the list in the GOA we ship.