Hi all,
I would appreciate I you can test MicroCrypt for UX design,
usability etc. and let me know. I signed-up with Play Store
for a developer account and they recoment that I should test
my app with at least twelve people, prior releasing.
Here is the download link:
<https://drive.google.com/file/d/1CAD7B5TlNoGeS0DxJlsycH6YO975UWS5/view?usp=drive_link>
Any help and feedback would be very much appreciated!
I am especially interested if the GUI works fine under small
Android devices. Please note: The app is not signed yet and
it may give you a warning, when installing, which you can
ignore.
Stefan Claas wrote:<https://apps.fyne.io/apps/oc2mx.net.microcrypt.html>
Here is the download link:
<https://drive.google.com/file/d/1CAD7B5TlNoGeS0DxJlsycH6YO975UWS5/view?usp=drive_link>
Why should people do this without any further information?
Arno Welzel wrote:
Stefan Claas wrote:<https://apps.fyne.io/apps/oc2mx.net.microcrypt.html>
Here is the download link:
<https://drive.google.com/file/d/1CAD7B5TlNoGeS0DxJlsycH6YO975UWS5/view?usp=drive_link>
Why should people do this without any further information?
Andy Burns, 2026-02-26 11:44:
Arno Welzel wrote:
Stefan Claas wrote:
Here is the download link: <https://drive.google.com/file/d/1CAD7B5TlNoGeS0DxJlsycH6YO975UWS5/view?usp=drive_link>
Why should people do this without any further information?<https://apps.fyne.io/apps/oc2mx.net.microcrypt.html>
And where is the Android version? I only see code for the desktop.
Arno Welzel wrote:
Andy Burns, 2026-02-26 11:44:
Arno Welzel wrote:
Stefan Claas wrote:<https://apps.fyne.io/apps/oc2mx.net.microcrypt.html>
Here is the download link:
<https://drive.google.com/file/d/1CAD7B5TlNoGeS0DxJlsycH6YO975UWS5/view?usp=drive_link>
Why should people do this without any further information?
And where is the Android version? I only see code for the desktop.
https://github.com/Ch1ffr3punk/MicroCrypt
Stefan Claas, 2026-02-26 15:13:
Arno Welzel wrote:
Andy Burns, 2026-02-26 11:44:
Arno Welzel wrote:
Stefan Claas wrote:
Here is the download link: <https://drive.google.com/file/d/1CAD7B5TlNoGeS0DxJlsycH6YO975UWS5/view?usp=drive_link>
Why should people do this without any further information?<https://apps.fyne.io/apps/oc2mx.net.microcrypt.html>
And where is the Android version? I only see code for the desktop.
https://github.com/Ch1ffr3punk/MicroCrypt
Yes, this is what I mean. How to build an Android app based on this
code? I don't see any reference to golang.org/x/mobile/app etc.
Hi all,
I would appreciate I you can test MicroCrypt for UX design,
usability etc. and let me know. I signed-up with Play Store
for a developer account and they recoment that I should test
my app with at least twelve people, prior releasing.
Here is the download link:
<https://drive.google.com/file/d/1CAD7B5TlNoGeS0DxJlsycH6YO975UWS5/view?usp=drive_link>
Any help and feedback would be very much appreciated!
Stefan Claas <noreply@oc2mx.net> wrote:
Hi all,
I would appreciate I you can test MicroCrypt for UX design,
usability etc. and let me know. I signed-up with Play Store
for a developer account and they recoment that I should test
my app with at least twelve people, prior releasing.
Here is the download link:
<https://drive.google.com/file/d/1CAD7B5TlNoGeS0DxJlsycH6YO975UWS5/view?usp=drive_link>
Any help and feedback would be very much appreciated!
I tried opening the link on a Galaxy S4 running Android 11 but it wanted me to sign in to Google Drive, which I wasn't going to do.
(no idea why - the browser was also being funny about opening the link in
the first place and wanted to use the URL as a search term for Google instead)
Stefan Claas <noreply@oc2mx.net> wrote:
Hi all,
I would appreciate I you can test MicroCrypt for UX design,
usability etc. and let me know. I signed-up with Play Store
for a developer account and they recoment that I should test
my app with at least twelve people, prior releasing.
Here is the download link:
<https://drive.google.com/file/d/1CAD7B5TlNoGeS0DxJlsycH6YO975UWS5/view?usp=drive_link>
Any help and feedback would be very much appreciated!
I tried opening the link on a Galaxy S4 running Android 11 but it wanted me to sign in to Google Drive, which I wasn't going to do.
Arno Welzel wrote:[...]
Stefan Claas, 2026-02-26 15:13:
https://github.com/Ch1ffr3punk/MicroCrypt
Yes, this is what I mean. How to build an Android app based on this
code? I don't see any reference to golang.org/x/mobile/app etc.
It is explained here, for various stores:
https://docs.fyne.io/started/distribution/
I would appreciate I you can test MicroCrypt for UX design,
usability etc. and let me know. I signed-up with Play Store
for a developer account and they recoment that I should test
my app with at least twelve people, prior releasing.
Here is the download link:
<https://drive.google.com/file/d/1CAD7B5TlNoGeS0DxJlsycH6YO975UWS5/view?usp=drive_link>
Any help and feedback would be very much appreciated!
I tried opening the link on a Galaxy S4 running Android 11 but it wanted me >> to sign in to Google Drive, which I wasn't going to do.
Same here. The link is probably set up to share only with other Google users. That's indeed not very nice and AFAIK not needed.
P.S. I first tried it on my laptop where I was already signed-in on my Google account. Luckily your post warned me to look closely, so I could
bail out before going any further. Then I used another browser where I
was not signed-in on my Google account.
Stefan Claas, 2026-02-26 17:39:
Arno Welzel wrote:[...]
Stefan Claas, 2026-02-26 15:13:
https://github.com/Ch1ffr3punk/MicroCrypt
Yes, this is what I mean. How to build an Android app based on this
code? I don't see any reference to golang.org/x/mobile/app etc.
It is explained here, for various stores:
https://docs.fyne.io/started/distribution/
I see. So it this is a kind of cross compiler to create Android packages based on Go. Well, you can just run the create APK in an emulator which
comes with Android Studio. Did you already try this?
It is explained here, for various stores:
https://docs.fyne.io/started/distribution/
I see. So it this is a kind of cross compiler to create Android packages
based on Go. Well, you can just run the create APK in an emulator which
comes with Android Studio. Did you already try this?
Well, I do not use Android Studio, but will use the command-line tools
and then create the required file for the Play Store. Quite a bit to
learn for all these new things.
Stefan Claas wrote:
It is explained here, for various stores:
https://docs.fyne.io/started/distribution/
I see. So it this is a kind of cross compiler to create Android packages based on Go. Well, you can just run the create APK in an emulator which comes with Android Studio. Did you already try this?
Well, I do not use Android Studio, but will use the command-line tools
and then create the required file for the Play Store. Quite a bit to
learn for all these new things.
Long ago, I posted a dozen sequentially more difficult tutorials for
writing your own code and loading/testing it on your own phone.
I didn't delve into the uploading to Google part though, nor signing.
But it covers every single step of using Android Studio for assembly.
In addition, I wrote up a step-by-step method for assembling source code
off of, oh, I think it was github, using gradle, for, I think, ladb.
If they're useful then we can look them up. If not, no need to bother.
a. A dozen tutorials on using Android Studio to create apps
b. A tested sequence that "compliles" professional source code
Both require Android Studio.
I think we need some good tutorials to rebuild .apk to .aab, because
Google now requires this, as you can no longer upload to Play Store
.apk files. The other thing is sideloading from GitHub etc., which
will be made more difficult by Google this year.
Here you can sideload my signed MicroCrypt, from GitHub:
<https://github.com/Ch1ffr3punk/MicroCrypt/releases/download/v0.1.0/MicroCrypt-Android-Linux-AMD64.apk>
Stefan Claas, 2026-02-28 14:30:
[...]
I think we need some good tutorials to rebuild .apk to .aab, because
Google now requires this, as you can no longer upload to Play Store
.apk files. The other thing is sideloading from GitHub etc., which
will be made more difficult by Google this year.
Here you can sideload my signed MicroCrypt, from GitHub:
<https://github.com/Ch1ffr3punk/MicroCrypt/releases/download/v0.1.0/MicroCrypt-Android-Linux-AMD64.apk>
Since the whole application is only about 759 lines of code it may be
easier to rewrite the code for the app in Kotlin and create a native
Android application with Anroid Studio. All the crypto functions are available in Kotlin as well and Anroid Studio is available for free for
all major platforms (I used in in Windows 10/11 in the past and now in Kubuntu Linux 25.10 with KDE 6.5.5 without any problems).
Arno Welzel wrote:
Stefan Claas, 2026-02-28 14:30:
[...]
I think we need some good tutorials to rebuild .apk to .aab, because Google now requires this, as you can no longer upload to Play Store
.apk files. The other thing is sideloading from GitHub etc., which
will be made more difficult by Google this year.
Here you can sideload my signed MicroCrypt, from GitHub:
<https://github.com/Ch1ffr3punk/MicroCrypt/releases/download/v0.1.0/MicroCrypt-Android-Linux-AMD64.apk>
Since the whole application is only about 759 lines of code it may be easier to rewrite the code for the app in Kotlin and create a native Android application with Anroid Studio. All the crypto functions are available in Kotlin as well and Anroid Studio is available for free for
all major platforms (I used in in Windows 10/11 in the past and now in Kubuntu Linux 25.10 with KDE 6.5.5 without any problems).
Well, that is a possibility I may look into it in the future.
I will re-download Android Studio again.
It is now released for internal testing > https://play.google.com/apps/internaltest/4699732322065127392
Stefan Claas wrote:
It is now released for internal testing > https://play.google.com/apps/internaltest/4699732322065127392
Seems like you have to individually invite testers?
I couldn't find an email address for you ...
It is now released for internal testing (minimun 12 users and up to 100)
on Play Console. https://play.google.com/apps/internaltest/4699732322065127392
I would appreciate if some of you can test my app and keep it at least for
14 days and please do not opt-out as a tester in that period of time. You probably won't see on your device an app icon. This will be, as understood, happen once the app is officially available.
Arno Welzel wrote:
Stefan Claas wrote:<https://apps.fyne.io/apps/oc2mx.net.microcrypt.html>
Here is the download link:
<https://drive.google.com/file/d/1CAD7B5TlNoGeS0DxJlsycH6YO975UWS5/view?usp=drive_link>
Why should people do this without any further information?
Am 26.02.26 um 11:44 schrieb Andy Burns:
Arno Welzel wrote:
Stefan Claas wrote:<https://apps.fyne.io/apps/oc2mx.net.microcrypt.html>
Here is the download link:
<https://drive.google.com/file/d/1CAD7B5TlNoGeS0DxJlsycH6YO975UWS5/view?usp=drive_link>
Why should people do this without any further information?
404
File not found
Andy Burns wrote:
I couldn't find an email address for you ...
If you like to give feedback, you can do it either here or write me at: sacenator[at]gmail[dot]com.
Stefan Claas wrote:
Andy Burns wrote:
I couldn't find an email address for you ...
If you like to give feedback, you can do it either here or write me at: sacenator[at]gmail[dot]com.
Invite arrived ok, and recognised my play store logon, app installed and
did one trivial encryption, will test later ...
Stefan Claas, 2026-03-01 19:54:
[...]
It is now released for internal testing (minimun 12 users and up to 100)
on Play Console. https://play.google.com/apps/internaltest/4699732322065127392
I would appreciate if some of you can test my app and keep it at least for 14 days and please do not opt-out as a tester in that period of time. You probably won't see on your device an app icon. This will be, as understood, happen once the app is officially available.
You can use askaaron.jd@gmail.com for the invitation.
Am 26.02.26 um 11:44 schrieb Andy Burns:
Arno Welzel wrote:
Stefan Claas wrote:
Here is the download link: <https://drive.google.com/file/d/1CAD7B5TlNoGeS0DxJlsycH6YO975UWS5/view?usp=drive_link>
Why should people do this without any further information?<https://apps.fyne.io/apps/oc2mx.net.microcrypt.html>
404
File not found
The site configured at this address does not contain the requested file.
Why should people do this without any further information?
does the app icon is also only an emtpy white square
Stefan Claas wrote:
does the app icon is also only an emtpy white square
An empty white circle.
Arno Welzel wrote:
Why should people do this without any further information?
I wondered what it was myself, so I produce this below for clarification. Anything below can be wrong (and probably is).
MicroCrypt is a small, cross-platform symmetric encryption tool for desktop and Android. It focuses on simplicity, portability, and modern
cryptographic defaults while avoiding unnecessary metadata in encrypted output.
Features
Symmetric file encryption using AES-256-GCM
Password-based key derivation using Argon2id
ISO/IEC 7816-4 padding in 1 KB block multiples
Minimum 12-character password requirement
Simple graphical interface built with the Fyne toolkit
Works on Linux, macOS, Windows, and Android
Cryptography Overview
MicroCrypt uses the following components:
1. AES-256-GCM
Provides authenticated encryption, ensuring both confidentiality and
integrity of the encrypted data.
2. Argon2id
A memory-hard password-based key derivation function designed to resist
brute-force and GPU-based attacks.
3. ISO/IEC 7816-4 Padding
Data is padded to 1 KB boundaries before encryption. This helps reduce
metadata leakage about the original file size.
Installation
Option 1: Install using the Fyne toolchain
go install fyne.io/tools/cmd/fyne@latest
fyne install github.com/Ch1ffr3punk/MicroCrypt/MicroCrypt-Desktop@latest
Option 2: Clone the Git repository
git clone https://github.com/Ch1ffr3punk/MicroCrypt
Use Cases
MicroCrypt is suitable for:
Encrypting personal files with a simple GUI
Cross-platform workflows where the same tool is needed on desktop and
Android
Users who want strong encryption without complex configuration
Situations where avoiding metadata leakage is important
MicroCrypt is not intended for:
Public-key encryption or key exchange workflows
Enterprise or multi-user key management
Automated or scripted encryption pipelines
License
?
Arno Welzel wrote:
Stefan Claas, 2026-03-01 19:54:
[...]
It is now released for internal testing (minimun 12 users and up to 100) >>> on Play Console. https://play.google.com/apps/internaltest/4699732322065127392
I would appreciate if some of you can test my app and keep it at least for >>> 14 days and please do not opt-out as a tester in that period of time. You >>> probably won't see on your device an app icon. This will be, as understood, >>> happen once the app is officially available.
You can use askaaron.jd@gmail.com for the invitation.
Just added you. Thanks a lot!
Maria Sophia wrote:
Arno Welzel wrote:
Why should people do this without any further information?
I wondered what it was myself, so I produce this below for clarification.
Anything below can be wrong (and probably is).
MicroCrypt is a small, cross-platform symmetric encryption tool for desktop >> and Android. It focuses on simplicity, portability, and modern
cryptographic defaults while avoiding unnecessary metadata in encrypted
output.
Features
Symmetric file encryption using AES-256-GCM
Password-based key derivation using Argon2id
ISO/IEC 7816-4 padding in 1 KB block multiples
Minimum 12-character password requirement
Simple graphical interface built with the Fyne toolkit
Works on Linux, macOS, Windows, and Android
Cryptography Overview
MicroCrypt uses the following components:
1. AES-256-GCM
Provides authenticated encryption, ensuring both confidentiality and
integrity of the encrypted data.
2. Argon2id
A memory-hard password-based key derivation function designed to resist
brute-force and GPU-based attacks.
3. ISO/IEC 7816-4 Padding
Data is padded to 1 KB boundaries before encryption. This helps reduce
metadata leakage about the original file size.
Installation
Option 1: Install using the Fyne toolchain
go install fyne.io/tools/cmd/fyne@latest
fyne install github.com/Ch1ffr3punk/MicroCrypt/MicroCrypt-Desktop@latest >>
Option 2: Clone the Git repository
git clone https://github.com/Ch1ffr3punk/MicroCrypt
Use Cases
MicroCrypt is suitable for:
Encrypting personal files with a simple GUI
Cross-platform workflows where the same tool is needed on desktop and
Android
Users who want strong encryption without complex configuration
Situations where avoiding metadata leakage is important
MicroCrypt is not intended for:
Public-key encryption or key exchange workflows
Enterprise or multi-user key management
Automated or scripted encryption pipelines
Excellent! I should use this instead of my README, if you agree!
I will later do two small changes to MicroCrypt:
a) Minimum password length of 15 characters, according to the
NIST 800-63B publication https://pages.nist.gov/800-63-3/sp800-63b.html
b) Timeout increase to 5 minutes instead of 1, when the app is idle.
License
?
Apache-2.0 license
I should use this instead of my README, if you agree!
Excellent! I should use this instead of my README, if you agree!
This should also be part of the app itself in an "About" or "Help" page.
Stefan Claas, 2026-03-02 16:32:
Arno Welzel wrote:
Stefan Claas, 2026-03-01 19:54:
[...]
It is now released for internal testing (minimun 12 users and up to 100)
on Play Console. https://play.google.com/apps/internaltest/4699732322065127392
I would appreciate if some of you can test my app and keep it at least for
14 days and please do not opt-out as a tester in that period of time. You
probably won't see on your device an app icon. This will be, as understood,
happen once the app is officially available.
You can use askaaron.jd@gmail.com for the invitation.
Just added you. Thanks a lot!
Got it.
As a quick feedback:
1) The "reload" icon on the top right to change the theme between "dark"
and "light" is quite confusing.
2) A little "About" page to explain what this app is used for and how it works, would be helpful. This page could also contain a link to the Git repository.
Stefan Claas, 2026-03-02 19:12:
Maria Sophia wrote:
Arno Welzel wrote:
Why should people do this without any further information?
I wondered what it was myself, so I produce this below for clarification. Anything below can be wrong (and probably is).
MicroCrypt is a small, cross-platform symmetric encryption tool for desktop
and Android. It focuses on simplicity, portability, and modern cryptographic defaults while avoiding unnecessary metadata in encrypted output.
Features
Symmetric file encryption using AES-256-GCM
Password-based key derivation using Argon2id
ISO/IEC 7816-4 padding in 1 KB block multiples
Minimum 12-character password requirement
Simple graphical interface built with the Fyne toolkit
Works on Linux, macOS, Windows, and Android
Cryptography Overview
MicroCrypt uses the following components:
1. AES-256-GCM
Provides authenticated encryption, ensuring both confidentiality and
integrity of the encrypted data.
2. Argon2id
A memory-hard password-based key derivation function designed to resist
brute-force and GPU-based attacks.
3. ISO/IEC 7816-4 Padding
Data is padded to 1 KB boundaries before encryption. This helps reduce
metadata leakage about the original file size.
Installation
Option 1: Install using the Fyne toolchain
go install fyne.io/tools/cmd/fyne@latest
fyne install github.com/Ch1ffr3punk/MicroCrypt/MicroCrypt-Desktop@latest
Option 2: Clone the Git repository
git clone https://github.com/Ch1ffr3punk/MicroCrypt
Use Cases
MicroCrypt is suitable for:
Encrypting personal files with a simple GUI
Cross-platform workflows where the same tool is needed on desktop and
Android
Users who want strong encryption without complex configuration
Situations where avoiding metadata leakage is important
MicroCrypt is not intended for:
Public-key encryption or key exchange workflows
Enterprise or multi-user key management
Automated or scripted encryption pipelines
Excellent! I should use this instead of my README, if you agree!
This should also be part of the app itself in an "About" or "Help" page.
I will later do two small changes to MicroCrypt:
a) Minimum password length of 15 characters, according to the
NIST 800-63B publication https://pages.nist.gov/800-63-3/sp800-63b.html
b) Timeout increase to 5 minutes instead of 1, when the app is idle.
License
?
Apache-2.0 license
Is this a requirement? Otherwise I'd prefer GPL v3.
Stefan Claas wrote:
I should use this instead of my README, if you agree!
You're welcome to anything I write here on the topic, where this is in a better README.md format that you can use as a starter to edit.
I will add an even more detailed README after looking up some data.
MicroCrypt is a small, cross-platform symmetric encryption tool for
desktop and Android. It focuses on simplicity, portability, and modern
cryptographic defaults while avoiding unnecessary metadata in encrypted
output.
## Features
- Symmetric file encryption using AES-256-GCM
- Password-based key derivation using Argon2id
- ISO/IEC 7816-4 padding in 1 KB block multiples
- Minimum 12-character password requirement
- Simple graphical interface built with the Fyne toolkit
- Works on Linux, macOS, Windows, and Android
## Cryptography Overview
MicroCrypt uses the following components:
1. AES-256-GCM
Provides authenticated encryption, ensuring both confidentiality and
integrity of the encrypted data.
2. Argon2id
A memory-hard password-based key derivation function designed to
resist brute-force and GPU-based attacks.
3. ISO/IEC 7816-4 Padding
Data is padded to 1 KB boundaries before encryption. This helps
reduce metadata leakage about the original file size.
## Installation
Option 1: Install using the Fyne toolchain
go install fyne.io/tools/cmd/fyne@latest
fyne install github.com/Ch1ffr3punk/MicroCrypt/MicroCrypt-Desktop@latest
Option 2: Clone the Git repository
git clone https://github.com/Ch1ffr3punk/MicroCrypt
## Use Cases
MicroCrypt is suitable for:
- Encrypting personal files with a simple GUI
- Cross-platform workflows where the same tool is needed on desktop and
Android
- Users who want strong encryption without complex configuration
- Situations where avoiding metadata leakage is important
MicroCrypt is not intended for:
- Public-key encryption or key exchange workflows
- Enterprise or multi-user key management
- Automated or scripted encryption pipelines
## Planned Changes
The author notes two upcoming adjustments:
a) Minimum password length will increase to 15 characters, following
NIST 800-63B guidance:
https://pages.nist.gov/800-63-3/sp800-63b.html
b) Idle-time timeout will increase from 1 minute to 5 minutes.
## License
Apache-2.0 license
Arno Welzel wrote:[...]>> 2) A little "About" page to explain what this app is used forand how it
works, would be helpful. This page could also contain a link to the Git
repository.
The GitHub repository has a README, which will be replaced with Marion's README later. I do not wan't to add a pop-up in the app, to clutter the
GUI and once released later, in app stores, it will then show Marion's README.
Stefan Claas, 2026-03-03 09:42:
Arno Welzel wrote:[...]>> 2) A little "About" page to explain what this app is used forand how it
works, would be helpful. This page could also contain a link to the Git repository.
The GitHub repository has a README, which will be replaced with Marion's README later. I do not wan't to add a pop-up in the app, to clutter the
GUI and once released later, in app stores, it will then show Marion's README.
Well - then maybe a button "Github" or similar which will open the URL
with the repository. Does the platform you use allow using regular
Android menus? Then this could also be an entry in the menu as well.
You're welcome to anything I write here on the topic, where this is in a
better README.md format that you can use as a starter to edit.
Thanks a lot, much appreciated! I will of course later give credits
to you in my GitHub (and Gitlab) repository, with a clickable link,
from a Newsgrouper URL, so that people can see your name from this
thread, or if you have a home page I would add this link. I will
add Arno too.
Stefan Claas wrote:
You're welcome to anything I write here on the topic, where this is in a better README.md format that you can use as a starter to edit.
Thanks a lot, much appreciated! I will of course later give credits
to you in my GitHub (and Gitlab) repository, with a clickable link,
from a Newsgrouper URL, so that people can see your name from this
thread, or if you have a home page I would add this link. I will
add Arno too.
I'm glad you liked it. I don't need the credits. I don't even know who I am. I have real peer-reviewed journal articles that give me plenty of credit.
Maria Sophia wrote:
Stefan Claas wrote:
You're welcome to anything I write here on the topic, where this is in a
better README.md format that you can use as a starter to edit.
Thanks a lot, much appreciated! I will of course later give credits
to you in my GitHub (and Gitlab) repository, with a clickable link,
from a Newsgrouper URL, so that people can see your name from this thread, or if you have a home page I would add this link. I will
add Arno too.
I'm glad you liked it. I don't need the credits. I don't even know who I am.
I have real peer-reviewed journal articles that give me plenty of credit.
Well, I hope you don't mind including you in the README. It is also now reworked from your source and I like to leave it as it is now. I publish later the update and then all can review the repository again.
Thanks for your help,which is much appreciated!
Stefan Claas wrote:
Maria Sophia wrote:
Stefan Claas wrote:Well, I hope you don't mind including you in the README. It is also now
You're welcome to anything I write here on the topic, where this is in a >>>>> better README.md format that you can use as a starter to edit.
Thanks a lot, much appreciated! I will of course later give credits
to you in my GitHub (and Gitlab) repository, with a clickable link,
from a Newsgrouper URL, so that people can see your name from this
thread, or if you have a home page I would add this link. I will
add Arno too.
I'm glad you liked it. I don't need the credits. I don't even know who I am.
I have real peer-reviewed journal articles that give me plenty of credit. >>
reworked from your source and I like to leave it as it is now. I publish
later the update and then all can review the repository again.
Thanks for your help,which is much appreciated!
Ok, the repository (code and readme) is updated. I will later submit
v0.1.1 to the Play Store. I included you and Arno in the README. :-)
Thanks for helping me out!
| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 59 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 19:51:28 |
| Calls: | 812 |
| Calls today: | 2 |
| Files: | 1,287 |
| D/L today: |
20 files (23,248K bytes) |
| Messages: | 210,075 |