A hint for anyone googling for this: make sure that the value of gcmSenderId in your AndroidManifest.xmlstill has the trailing backslash (\) after you’ve changed the project number to your own. Otherwise the value gets interpreted as int, when it should be a string, which is one way to trigger the issue of devices being assigned empty/null IDs.
(The building instructions do have this documented in bold, but it’s still very easy to miss, I know I did. Complicating the debugging was my Nexus 5X, which kept getting a proper device ID even when all other devices using the same broken build failed to.)
Sorry for necromancing, but because Google seems to like this thread, I just thought I’d add a mention that a check_data_directory_permissions option for config.php has since been implemented (and backported down to NC12), and it allows the admin to turn off the automatic permissions reset (by assigning it false).
This is discouraged however, and ACLs or other means of managing access are still the better option where available.
@skjnldsv The points you raise are about SEO, and (from what I linked to above) I believe those issues are already being worked on. In case I was unclear, I’m not arguing for my idea to supplant the SEO work currently in progress, but to augment it.
Obviously, if #915 gets implemented as requested, my issue becomes moot, but from reading the comments there I understand it’s not so cut and dried that it will be.
As discussed in #915 and #517, Google seems to prefer old versions’ documentation at the expense of newer ones for some reason. The issue was partly mitigated by the fix for #958, which added prominent links to the latest version on top of old pages.
But these links currently point to the manual root. Ideally, I’d like these links to point directly to the latest version of the specific manual page I’m viewing, if available.
For instance, a search for nextcloud occ (for me at least) currently yields the manual page for version 9 as the top result. The ”latest version” link at the top then takes me to the server manual introduction. This means it’s still easier for me to navigate to the latest version of the ”Using the occ command” page by manually replacing the version number in the current URL with ’stable’ (or the latest release number) than to follow the ”latest version” link and try to find the page there.
Producing specific links is probably more laborious than the generic top-level-pointing link. For instance, there may no longer be a corresponding page in the stable version. Detecting such cases should be automatable I think, but there may be other issues that aren’t.
This will be much less of an issue once the SEO issue is resolved, but I think direct links would still remain useful, as people can still come up with search terms that search engines think correspond to old documentation better than the latest.
Here’s a transcript of the interview by (and with interspersed comments from) a Finnish ex-JW; here’s the (relatively legible) Google translation (in English).
Oh god the auto captions on this are killing me!
”Temporarily switch back to old compose” -linkki löytyy ainakin minulla kokeilijana sen compose-popupikkunan oikeasta alanurkasta löytyvän väkäsen kautta avautuvasta valikosta. Mielenkiintoista kuulla löytyykö sitä sinun näkymästäsi.
Gmail tarjosi tuota kokeiltavaksi taannoin. Kokeilin, mutta palasin hyvin pian entiseen. Jotain pointtia uudessa paradigmassa muistaakseni mietin olleen, mutta se paradigma ei kohdannut minun käyttöparadigmani kanssa kovin hyvin.
Pointtina siis tässä, että jollei tämä nyt ole lopullisen käyttöönoton ensiairut (minulla tuo ei ainakaan vielä tätä kirjoittaessani ole tullut takaisin pakotettuna), voit ehkä vielä palata entiseen sinäkin, jos onnistut löytämään sieltä sen linkin. Muistaakseni se oli hyvin pienellä jossain nurkassa silloin kun minä uutta kokeilin (jokunen kk sitten). Jollei päänäkymässä niin asetuksissa.
Etsisin tarkat ohjeet kokeilemalla, mutta pelkään, että jos tämä todella nyt on lopullista, sieltä ei minullakaan enää ole paluuta jos erehdyn tuon ”new compose experience” -linkin nyt valitsemaan… Tai no menkööt, jos on lopullista niin sitten on.
I’ll be back.
Any chance of tweaking it so that I could give +1’s to articles irrespective of and in addition to sharing them in G+ posts? From what I can tell, giving +1’s isn’t currently supported by the plugin.
Google Reader had +1 tied to sharing so that in order to share on G+ I had to +1 it first. That was okay but not entirely optimal: +1 and posting on G+ about something could IMHO very well be two separate functions, so that you could
* only +1 something
* only share it in a G+ post
* do both if you like
Newsblur (joka on kuulemma perustettu jo vuosia sitten tätä päivää ennakoiden) vaikutti pikaisella kokeilulla lupaavalta, mutta tämän TSI-miehen vei lopulta Tiny Tiny RSS. Ennen Readeria käytin jonkin aikaa Netvibesia, joka on vieläkin olemassa. Readeriin tottuneen täytyy kylläkin Netvibesissa opetella tyystin erilainen tyyli kuluttaa sisältöä.