perkeep/clients
mpl 965aeaca33 clients/android: bump targetSdkVersion to 26
Because it is mandatory as of nov 2018:
https://android-developers.googleblog.com/2017/12/improving-app-security-and-performance.html

As the default Notification.Builder constructor is deprecated in API 26,
this change also adds the use of the new constructor, which requires a
notification channel Id.

Note: since the users are now in full-control of the notifications,
they can now choose to completely block the auto-upload notification
channel. Given that the main goal of the notification was to keep the
app in memory in order for auto-upload to work, one could expect that
blocking the channel would defeat the notification's purpose. However,
as far as I could test, auto-uploading seems to still be working even
after disabling the channel, and letting the activity die (tip: in
devoloper options, one can tick "Don't keep activities"). In fact,
Perkeep Uploader still always runs as a service.

Also build pk-put shipped in the app with Go 1.11.

Fixes #1202

Change-Id: I8f98e0df742915cb504b6c1cfaa42ca6dc7b6189
2018-09-22 02:40:40 +02:00
..
android clients/android: bump targetSdkVersion to 26 2018-09-22 02:40:40 +02:00
chrome/clip-it-good Fix permissions for files 2016-04-28 21:15:09 +02:00
curl client: fix blobserver path in curl and python clients 2013-01-01 00:27:11 +05:30
ios-objc Rename import paths from camlistore.org to perkeep.org. 2018-01-01 16:03:34 -08:00
js commit js client sketch 2010-11-04 23:05:20 -07:00
osx Merge "clients/osx: use Keepy for all app icons" 2018-09-06 18:59:08 +00:00
python all: update copyright holder from Google Inc to The Perkeep Authors 2018-01-03 16:52:49 -08:00
web/embed server/perkeepd/ui: replace pudgy with keepy 2018-06-29 21:48:11 +02:00