fidzu : Maemo

This week, I had to go through the process of Android OS/Kernel building/installation. And it was a lot much better and 6 months ago (maybe, because I built it for a device and not for the emulator?). I compiled the images in Ubuntu 12.04 and I used a Samsung Galaxy Nexus device (maguro with tuna as kernel). Therefore, I decided to summarize the steps that I took. This mini-tutorial is a lot shorter and simpler (and really works!!).

1. Android OS

1.0 Setting up the building environment

Check this instructions (here and here) to set up the basic environment and download the code. I used the branch [android-4.3_r1.1].

1.1 Compiling the Android OS

a. Download and unpack the manufacturer drivers from this link. They have to be unpacked into the directory [android_source_code]/vendors -- but don't worry, as the .zip files contain a script that does all the work for you.

b. Once the drivers are in the proper place, run the following commands:

@desktop:$ cd [android_source_code]
@desktop:$ make clobber
@desktop:$ lunch full_maguro-userdebug
@desktop:$ make -j4

It takes a long time to compile the image.

After these steps, the Android OS is ready.

1.2 Flashing the device with the new Android OS

Now, you need two tools from the Android SDK: adb and fastboot. These tools are located in the folder [androis_sdk]/platform-tools.

a. Reboot the device in the bootloader mode -- hold VolumeDown and VolumeUp and then press the PowerUp button.

b. Connect the USB cable.

c. Run the following commands:

@desktop:$ export PATH=$PATH:[android_sdk]/platform-tools
@desktop:$ cd [android_source_code]
@desktop:$ sudo fastboot format cache
@desktop:$ sudo fastboot format userdata
@desktop:$ sudo ANDROID_PRODUCT_OUT=[android_source_code]/out/target/product/maguro/ fastboot -w flashall

After these steps, reboot the device. A clean installation will take place. To check the new version of you device, go to "Settings" - - > "About Phone" and check "Model number": now, it should be "AOSP on Maguro" (check attached image)

2. Android Kernel

Ok. Now, we have the AOSP in place and we need to compile a new kernel. But why do you need to compile and install a new kernel? Oh, well, let's say that you want to apply some patches or that you need to change the kernel to enable Linux module support (the default Android Linux Kernel does not support modules).

2.0 Setting up the building environment

If you have built the Android OS before, you don't need anything special for the kernel building. I used the official code from https://android.googlesource.com/kernel/omap.git, branch android-omap-tuna-3.0-jb-mr2.

2.1 Compiling the Kernel

First, you need to set some variables that are important for the building process (ARCH and CROSS_COMPILE):

@desktop:$ export ARCH=arm
@desktop:$ export CROSS_COMPILE=[android_source_code]/prebuilts/gcc/linux-x86/arm/arm-eabi-4.7/bin/arm-eabi-

Now, you have to generate a .config which contains all the options for the kernel building. By running the following command you generate a basic .config file for Android.

@desktop:$ cd [android_kernel_code]
@desktio:$ make tuna_defconfig

Sometimes, you need to set some specific entries of the .config to enable/disable certain features of the kernel. For this specific example, let's set the option CONFIG_MODULES to y (the entry in the .config file should be CONFIG_MODULES=y). With CONFIG_MODULES set to y, it is possible to insert/remove kernel modules. Now, let's build the kernel

@desktop:$ cd [android_kernel_code]
@desktop:$ make

(it takes some time to compile the kernel)

2.2 Preparing the kernel for installation

The kernel image is almost ready: it's still necessary to wrap it up properly to flash it into the device. The Android source code contains scripts that do the work for us. Consider that the image was generated at [android_kernel_code]/arch/arm/boot/zImage.

@desktop:$ cd [android_source_code]
@desktop:$ export TARGET_PREBUILT_KERNEL= [android_kernel_code]/arch/arm/boot/zImage
@desktop:$ make bootimage

At the end, a custom image is ready for installation at [android_source_code]/out/target/product/maguro/boot.img

2.3 Flashing the device with the new Kernel

Now, everything is in place and we can finally flash our kernel image. To do so:

a. You need to boot the device in bootloader mode (hold VolumeDown and VolumeUp and then press the PowerUp button)

b. Connect the USB cable

@desktop:$ cd [android_source_code]
@desktop:$ sudo ANDROID_PRODUCT_OUT=[android_source_code]/out/target/product/maguro/ fastboot flash boot [android_source_code]/out/target/product/maguro/boot.img

After these steps, reboot the device. A clean installation will take place. To check the new version of you kernel, go to "Settings" - - > "About Phone" and check "Kernel version": you will see a different name for you kernel image (as for the previuos image).


0 0

28 Jul 2014 7:06pm GMT

Firefox for Mobile Firefox for Android: Collecting and Using Telemetry - http://starkravingfinkle.org/blog... July 24 from Mark Finkle's Weblog » Mozilla - Comment - Like

0 0

25 Jul 2014 3:08am GMT

Meeting held on FreeNode, channel #maemo-meeting (logs)

Attending: Philippe Coval (rZr), Peter Leinchen (peterleinchen), Gido Griese (Win7Mac), Paul Healy (sixwheeledbeast), Ruediger Schiller (chem|st), Niel Nielsen (nieldk), Jussi Ohenoja (juiceme).

Absent: Joerg Reisenweber (DocScrutinizer05)

Summary of topics (ordered by discussion):
- Inaugural meeting of the new Maemo Council 2Q/2014
- Discussion on Council work media
- Comments by DocScrutinizer05>

Topic (Inaugural meeting of the new Maemo Council 2Q/2014):

• The meeting started at 20:01 UTC. The new council assembled, and juiceme welcomed the new members.
• The election results can be seen on the voting page. There was discussion on the vote counting algorithm (STV) and the number of ballots cast in the election.
• The council decided to continue the present practice of having weekly meetings on tuesdays at 20:00 UTC. All council members live on UTC, UTC+1, UTC+2 zones.
• There was some discussion of the roles in the Council. After discussion nieldk proposed peterleinchen as Chair & Secretary and juiceme seconded the motion. The vote was unanimous (4/4) and peterleinchen accepted the position.

Topic (Discussion on Council work media):

• There was discussion on how to handle the tasks and documents during council work; possibilities are to use piratepad or wikipage on Maemo for collaboration. The advantage of piratepad would be easy multiediting capabilities, on the other hand wiki is more secure.
• The council voted to use a wiki page as work medium but as wiki cannot be set up as private, email ans piratepad are kept as alternative for in-progress/confidental work.
• Sixwheeledbeast set up a wiki page for Council agenda.

Topic (Comments by DocScrutinizer05):

• Joerg came on the IRC channel later when the meeting was over, having been taken ill, but he had the following comments;
  • The Council has only one set of rules which define what the council is and what the council does.
  • The Council is not subject to directives from any other body.
  • Council work is generally done in the public, unless mandated by specific necessity. For confidental work there is the council members mailing list.
  • Since Hildon Foundation has accepted the Maemo Council as its Council, the Maemo Council is also the Council of the new unified Maemo e.V. that is going to take over the responsibilities of Hildon Foundation.

0 0

19 Jul 2014 1:58pm GMT

Discussion started last year about moving the US-based Hildon Foundation non-profit operations to Europe. After a positive reception to the initial proposal, some further planning by the community, and a lot of foot work, work is progressing on setting up a German e.V. (which was selected due to limited options available in Europe).
The move serves several purposes:

• It gets us out from under the cost and regulatory burdens of operating in the US. The US is expensive and difficult to operate in for small non-profits. Taxes and regulations from two major entities: the US Federal Government and the State of Pennsylvania (where the Hildon Foundation is registered), which both require annual paperwork be submitted on the fiscal operations of the entity, are expensive and time-consuming for an all-volunteer operation funded by donations.
• It brings the major operations of maemo.org all within a single regulatory environment. The operations of maemo.org are almost exclusively hosted at IPHH in Germany, bringing the organizational stewardship into the Euro-zone reduces the number of regulator issues which must be understood and dealt with by the foundation.
• Finally, it eliminates the large overhead involved with international money transfers. The hardware for maemo.org is hosted at IPHH (many thanks to them) in Germany, and with the billing currency in Euros, each transfer of the annual hosting-fee costs about $40 instead of the few cents it would cost wiring it from within the SEPA-Zone. Payments for hardware purchases, and other invoices are almost all going to entities in Europe, so eliminating the currency exchange overhead will significantly reduce costs for the continued operation of maemo.org.

The Hildon Foundation assets will need to be transferred to the new e.V. once its legal registration is completed. The Hildon Foundation will then be dissolved. This is slightly complicated by the aforementioned regulatory burdens in the US, but will hopefully be finalized by the end of the third quarter of this year. In terms of obligations, responsibilities and relationship to the community, this move has no effect: it is purely a technical measure to allow the Foundation to better manage the community's assets.

0 0

15 Jul 2014 10:37pm GMT

Dear Maemo community, I have the great honor of introducing the new Community Council for the upcoming Q2/2014 period.

The members of the new council are:

• Joerg Reisenweber (joerg_rw)
• Jussi Ohenoja (juiceme)
• Niel Nielsen (nieldk)
• Peter Leinchen (peterleinchen)
• Philippe Coval (rzr)

The voting results can be seen on the voting page

I want to thank warmly all the members of the community who participated in this most important action of choosing a new council for us!

The new council shall meet on the #maemo-meeting IRC channel today at 20:00 UTC for the formal handover with the passing council.

Jussi Ohenoja, Council Chair Q1/2014

On behalf of the outgoing Maemo Community Council

0 0

15 Jul 2014 5:38am GMT

Meeting held on FreeNode, channel #maemo-meeting (logs)

Attending: Joerg Reisenweber (DocScrutinizer05), Ruediger Schiller (chem|st), xes, Philippe Coval (rZr), Paul Healy (sixwheeledbeast), Peter Leinchen (peterleinchen), Gido Griese (Win7Mac), Tom Joyce (TomJ), dirkvl, Aaron McEwan (chainsawbike), Sebastian Krzyszkowiak (dos1), Martin Kolman (M4rtinK), Jussi Ohenoja (juiceme).

Absent:

Summary of topics (ordered by discussion):
- General orienteering for the new council election candidates

Topic (General orienteering for the new council election candidates):

• DocScrutinizer briefed the candidates on council tasks.
  • What the Maemo Council is, and what it does; http://wiki.maemo.org/Community_Council/FAQ
  • What are the rules of the Maemo Council; http://wiki.maemo.org/Community_Council#Council_work
• All candidates are urged to update their introduction/declaration to the Elections Wiki page; (http://wiki.maemo.org/Community_Council/Council_election_May_2014/Candidate_declarations)
• There was talk on the responsibilities and interfaces between Council, HiFo and Techstaff
• There are 10 candidates running for the new council: (in alphabetical order of TMO nickname)
  • chainsawbike
  • dirkvl
  • jackburton
  • joerg_rw
  • juiceme
  • Mariusmssj
  • nieldk
  • peterleinchen
  • rzr
  • TomJ
• The current Council voted on eligibility of candidates that apparently have not enough Karma. The vote was unanimous; chainsawbike was declared eligible to run for council.

0 0

03 Jul 2014 6:59am GMT

Meeting held on FreeNode, channel #maemo-meeting (logs)

Attending: Ruediger Schiller (chem|st), Gido Griese (Win7Mac), Joerg Reisenweber (DocScrutinizer05), Paul Healy (sixwheeledbeast), Jussi Ohenoja (juiceme).

Absent:

Summary of topics (ordered by discussion):
- Discussion on the handling of device donations
- Status update on the Maemo e.V. registration
- Discussion on the ongoing Maemo Council election

Topic (Discussion on the handling of device donations):

• chem|st asked juiceme to organize a rally to collect device donations to be used as prizes for future Maemo Contests.

Topic (Status update on the Maemo e.V. registration):

• The bylaws have been now signed by juiceme, nieldk and DocScrutinizer. Next going to warfare.

Topic (Discussion on the ongoing Maemo Council election):

• There are no Council candidates, and by original schedule there should be at least four candidates to enter voting phase.
• Due to lack of candidates the schedule is extended by one month. New candidates are being requested for nomination until 30th of June 2014
• Win7Mac and chem|st made a new banner on TMO to direct attention to ongoing elections.
• sixwheeledbeast updated the elections page on Maemo Wiki

1 0

08 Jun 2014 10:27am GMT

Firefox for Mobile Firefox for Android: Casting videos and Roku support - Ready to test in Nightly - http://starkravingfinkle.org/blog... June 6 from Mark Finkle's Weblog » Mozilla - Comment - Like

0 0

06 Jun 2014 3:45pm GMT

Matthew gets that developers need good equipment.

Glade, Scaffolding (DevStudio), Scintilla & GtkSourceView, Devhelp, gnome-build and Anjuta also got it earlier.

I think with GNOME's focus on this and a bit less on woman outreach programs; this year we could make a difference.

Luckily our code is that good that it can be reused for what is relevant today.

It's all about what we focus on.

Can we please now go back at making software?

ps. I've been diving in Croatia. Trogir. It was fantastic. I have some new reserves in my mental system.

ps. Although we're very different I have a lot of respect for your point of view, Matthew.

1 1

23 May 2014 4:58pm GMT

Meeting held on FreeNode, channel #maemo-meeting (logs)

Attending: Ruediger Schiller (chem|st), Jussi Ohenoja (juiceme).

Absent:

Summary of topics (ordered by discussion):
- Discussion on arranging the next Maemo Council election
- Discussion on maemo.gitorious.org

Topic (Discussion on arranging the next Maemo Counco election):

• Juiceme has made the announcement of the election.
• Woody has been very helpful and provided juiceme assistance on running the voting machine.
• Juiceme has not yet had time to create a test election.

Topic (Discussion on maemo.gitorious.org):

• HiFo was contacted by Nokia/Microsoft about the use of maemo.gitorious.org to the Maemo community and if it needs to be kept alive in this way as they want to discontinue the contract with gitorious.org.
• Chem|st approached Gitorious' staff about possible solutions working out for us and Techstaff is looking into proper backups of these gits and hosting them our own.

1 0

17 May 2014 9:21am GMT

Dear friends and Maemoans, it has been a busy six months, and again it is time to elect a new Community Council for us.

The last election finished on Saturday 14th of December 2013 so the new election should be done by Saturday 14th of June 2014.

The schedule of the voting is as follows:

• Nomination period starts now on the 5th of May 2014 and continues until 31st of May 2014.
• Contemplation period starts on Sunday 1st of June 2014 and continues until Saturday 7th of June 2014.
• Election period starts on Sunday 8th of June 2014 and continues until 14th of June 2014.

To get our community to continue strong, we need fresh people with fresh viewpoints to carry on the torch, so please think about volunteering for Maemo Council.

Currently there is lots of things going on, as the Maemo council is now the one unified Council, acting on behalf of the whole Maemo Community and its legal representation bodies, the Maemo e.V. (registered association, successor to HiFo) and the Hildon Foundation.

On behalf of the outgoing community council,

Jussi Ohenoja

1 0

05 May 2014 1:55pm GMT

Meeting held on FreeNode, channel #maemo-meeting (logs)

Attending: Joerg Reisenweber (DocScrutinizer51), Ruediger Schiller (chem|st), Sicelo, Jussi Ohenoja (juiceme).

Absent:

Summary of topics (ordered by discussion):
- Discussion on arranging the next Maemo Counco election

Topic (Discussion on arranging the next Maemo Council election):

• The constraints for the election are:
  • Nomination period: announcement ... 2014/05/31
  • Contemplation period: 2014/06/01 ... 2014/06/07
  • Election period: 2014/06/08 ... 2014/06/14
• Juiceme promised to write the election announcement.

1 0

05 May 2014 1:47pm GMT

While Nemo Mobile OS doesn't ship with udisks2 nor with the GLib/GIO GVfs2 modules that interact with it, we still wanted removable volume management working with the file indexer.

It means that types like GVolume and GVolumeMonitor in GLib's GIO will fall back to GUnixVolume and GUnixVolumeMonitor using GUnixMount and GUnixMounts instead of using the more competent GVfs2 modules.

The GUnixMounts fallback uses the _PATH_MNTTAB, which generally points to /proc/mounts, to know what the mount points are.

Removable volumes usually aren't configured in the /etc/fstab file, which would or could affect /proc/mounts, plus if you'd do it this way the UUID label can't be known upfront (you don't know which sdcard the user will insert). Tracker's FS miner needs this label to uniquely identify a removable volume to know if a previously seen volume is returning.

If you look at gunixvolume.c's g_unix_volume_get_identifier you'll notice that it always returns NULL in case the UUID label isn't set in the mtab file: the pure-Unix fall back implementations aren't fit for non-typical desktop usage; it's what udisks2 and GVfs2 normally provide for you. But we don't have it on the Nemo Mobile OS.

The mount_add in libtracker-common/tracker-storage.c luckily has an alternative that uses the mountpoint's name (line ~592). We'll use this facility to compensate for the lacking UUID.

Basically, we add the UUID of the device to the mountpoint's directory name and Tracker's existing volume management will generate a unique UUID using MD5 for each unique mountpoint directory. What follows is specific for Nemo Mobile and its systemd setup.

We added some udev rules to /etc/udev/rules.d/90-mount-sd.rules:

SUBSYSTEM=="block", KERNEL=="mmcblk1*", ACTION=="add", MODE="0660", TAG+="systemd", 
  ENV{SYSTEMD_WANTS}="mount-sd@%k.service", ENV{SYSTEMD_USER_WANTS}="tracker-miner-fs.service
  tracker-store.service"

We added /etc/systemd/system/mount-sd@.service:

[Unit]
Description=Handle sdcard
After=init-done.service dev-%i.device
BindsTo=dev-%i.device

[Service]
Type=oneshot
RemainAfterExit=yes
ExecStart=/usr/sbin/mount-sd.sh add %i
ExecStop=/usr/sbin/mount-sd.sh remove %i

And we created mount-sd.sh:

if [ "$ACTION" = "add" ]; then
    eval "$(/sbin/blkid -c /dev/null -o export /dev/$2)"
    test -d $MNT/${UUID} || mkdir -p $MNT/${UUID}
    chown $DEF_UID:$DEF_GID $MNT $MNT/${UUID}
    touch $MNT/${UUID}
    mount ${DEVNAME} $MNT/${UUID} -o $MOUNT_OPTS || /bin/rmdir $MNT/${UUID}
    test -d $MNT/${UUID} && touch $MNT/${UUID}
else
    DIR=$(mount | grep -w ${DEVNAME} | cut -d \  -f 3)
    if [ -n "${DIR}" ] ; then
        umount $DIR || umount -l $DIR
    fi
fi

Now we just have to configure Tracker right:

gsettings set org.freedesktop.Tracker.Miner.Files index-removable-devices true

Let's try that:

# Insert sdcard
[nemo@Jolla ~]$ mount | grep sdcard
/dev/mmcblk1 on /media/sdcard/F6D0-FC42 type vfat (rw,nosuid,nodev,noexec,...
[nemo@Jolla ~]$ 

[nemo@Jolla ~]$ touch  /media/sdcard/F6D0-FC42/test.txt
[nemo@Jolla ~]$ tracker-sparql -q "select tracker:available(?s) nfo:fileName(?s) \
     { ?s nie:url 'file:///media/sdcard/F6D0-FC42/test.txt' }"
Results:
  true, test.txt

# Take out the sdcard

[nemo@Jolla ~]$ mount | grep sdcard
[nemo@Jolla ~]$ tracker-sparql -q "select tracker:available(?s) nfo:fileName(?s) \
     { ?s nie:url 'file:///media/sdcard/F6D0-FC42/test.txt' }"
Results:
  (null), test.txt
[nemo@Jolla ~]$

1 0

22 Apr 2014 8:05pm GMT

As the versions of my apps on Nokia Store grow more and more outdated, I've decided to remove the apps from there and instead self-host them on my web page and/or put them on OpenRepos.net instead. A handful of apps stay on Nokia Store; those are mostly S40 apps or apps for which a Symbian version also exists.

Here's a list of my N9 apps that you can now get for free ("deb download" is as of posting this, for new versions visit the webpage or openrepos.net):

• Billboard Standby Screen (web page, deb download, openrepos.net)
• Volume+ As Camera Button (web page, deb download, openrepos.net)
• Headset Camera Button (web page, deb download, openrepos.net)
• Personal Web Server (web page, deb download, openrepos.net)
• Mustr (web page, deb download, openrepos.net)
• gPodder (web page, deb download, openrepos.net)

And here's a list of my N9 games that you can now get for free (again, "deb download" is as of posting this; new versions on the webpage or openrepos.net):

• qw The Game (web page, openrepos.net)
• Tennix! Redux Demo (web page, deb download, openrepos.net)
• Petals (web page, deb download, openrepos.net)
• Brain Party (web page, openrepos.net)
• Numpty Physics (web page, openrepos.net)
• Plonk (web page, openrepos.net)
• chro.mono (web page, deb download, openrepos.net)

Of these, the "greatest hits" and most useful apps/most fun games are (in my opinion): Billboard, Volume+ As Camera Button and chro.mono, but also give qw The Game and Petals a try :)

A list of all my apps on OpenRepos.net is also available.

Please note that unless otherwise noted, do not copy the .deb files and distribute them yourself, please always link to the project webpage (the page, not the file) or the openrepos.net page - this makes sure users can always download the latest version and from a known-good source (always be careful when downloading and installing .debs from random webpages). For end users who want to stay up to date and install the packages comfortably, the Warehouse client for OpenRepos.net is recommended.

For some of these apps (not games) that are not open source yet, I plan to clean up and publish the source at some point in the future, so interested developers can have a look, add features and/or port it to new platforms. 2 0

19 Apr 2014 6:03pm GMT

Some words about hedging

The Bitcoin market is pretty fresh and unstable at the moment. It is greatly affected by any news on this market. We expect slow grow of exchange rates in the long-term. This assumptions is based on the following facts:

• The world requires anonymous currency. It is used not only for illegal transactions (like buying/selling drugs, weapons etc.), but also as a currency which is free from any political influence, not affiliated with any country, etc.
• Close-to-zero transaction fees. If an operation is made within the Bitcoin infrastructure you have no additional fees for running a bitcoin account
• Deflationary nature of bitcoin. The emission amount is fixed and could not be extended. Since (like any other currency) bitcoin's will be lost - the price of the rest should increase to compensate that

Unfortunately, all other *coins (Litecoin, Dogecoin, etc.) have close-to-zero influence on bitcoin exchange rates, while bitcoin exchange rates affects this currencies greatly. Detailed analytics of exchange rates dynamics on 3 different exchange markets revealed 0.00037% probability of getting profit by running exchange operations between different *coins (mostly due to exchange fees of sites)

Our opinion is that it is a nice time to start getting bitcoins :) It's exchange rates have still not recovered after the MtGOX failure, but recent research revealeds that MtGOX may have money on it's account, so we expect constant growing exchange rate of Bitcoin in next 3 months

What needs to be implemented?

This section describes a scope of the project. The main target of current project is to provide an easy way to perform easy transactions within system. So we need just three points of functionality:

• Adding money to amount (cash-in)
• Transferring money to other person's account
• Cash-out

Additionally to simplify people's life transferring money to other person's account should track "friends list" to simplify multiple transactions to other persons.

Since world is mobile now - all that operations should be available both from web-interface and mobile apps.

What will be great to have in future?

This section describes functionality outside initial project scope, but could be considered in future.

• "Send me money" button. When user click's it a popup appears on site where person could send money in one click
• QR-send. Using mobile you could scan a QR-code and confirm sending money in one click

What about security?

Security is a main concern of the project. Since we're building a system on top of bitcoin - there is no way to reverse any transaction.

So let's review possible approaches.

(rejected) Single bitcoin account managing all users accounts

We have just one bitcoin wallet, which contains all coins owned by our users. All in-system transactions are tracked by our system, same applies to account balances.

Pros: + Very easy to implement + Extremely fast (since there are no "real" transactions when we pass money from one person to other)

Cons: + extremely risky. Let's imagine situation when hacker was able to access account. He will be able to move all bitcoins to other address resulting in system crash

(rejected) Separate bitcoin wallet for each user

Each user has one bitcoin wallet. All transactions are performed by real bitcoin transactions

Pros: + Simplifies client logic. We do not need to "count" money - just retrieve them from bitcoin wallet and display to user + Way more secure - user have no real access to other uses wallet

Cons: + harder to implement + When we make transaction from one user to another we need to receive confirmation from bitcoin network which is not immediate. + risky. If hacker was able to compromise not account, but access to system same risks as previous options apply

Separate bitcoin wallet + cash-in-out wallet

The main problem of the previous approach is that a possible hacker has access to all bitcoins in the system, including bitcoins used by the cash-in and cash-out wallet. The solution is to run the system using 2 separate modules (ideally on two different network machines) - one for in-system transactions and one for cash-in/cash-out. The second one should accept just two operations "Give X BTC to user Y in system" or "Take X BTC from user Y". Since the code of second module will be simple and straightforward - it's easier to make it secure. Compromising client accounts will not compromise real money

How that will work?

AAA (Authorization, Authentication, Accounting) is always a compromise between usability and security. We suggest the following approach:

• User registers with his phone number. He may (or may not) enter recovery email address
• When user signs-in into the application two-factor auth is used by default - login, password + OTP (one-time-password) sent by SMS. Two-factor auth may be disabled in the settings by the user
• Each transaction higher than X$ is confirmed by OTP. If total sum of transactions within one hour exceeds X$ - each transaction is confirmed by OTP (that is done to prevent stealing money by millions of small transactions)
• Password recovery - user will have two options - send recovery info to email or to phone. If he selects phone - recovery information is sent within next 48 hours (but not earlier than 24 hours). That is done to ensure that if phone is stolen - user has enough time to block sim-card.

What is the status of development?

We're currently working on server-side stuff - bitcoin's transferring between two separates system. This part of system will be covered by unit tests to ensure security and reliability. Code should be ready soon if anyone is interested

1 0

26 Mar 2014 9:10pm GMT

Meeting held on FreeNode, channel #maemo-meeting (logs)

Attending: Joerg Reisenweber (DocScrutinizer05), Ruediger Schiller (chem|st), Gido Griese (Win7Mac), Niel Nielsen (nieldk), Robert Schiller (lowkyalyr), kerio, Titilambert, Paul Healy (sixwheeledbeast), Martin Kolman (M4rtinK), Falk Stern (warfare), Aaron McEwan (chainsawbike), Jussi Ohenoja (juiceme).

Absent:

Summary of topics (ordered by discussion):
- Kickoff meeting for Meamo Community e.V.

Topic (Kickoff meeting for Meamo Community e.V.):

• There was discussion about the voting engine used to prepare/handle/tally the votes in Maemo community matters. As it happens woody is the only one who knows how the system operates, so in the future woody needs to either continue to maintain it or pass the knowledge of it to other people capable of using it.
• This time the Maemo Council meeting was held with a differnt topic as usual, so the rest ot the meeting was conducted as formal Kickoff/Inaugural meeting of the new Maemo Community e.V.
• Win7Mac had prepared the following meeting agenda, which was presented to the attendeeds:
  • 1.)Commentary and vote on the Statutes and General rules
  • 2.) Election of the board of directors and acceptance of the internal board regulations
  • 3.)Election of the council
  • 4.)Agreement about member-fees
  • 5.)Organizational enactments
  • 6.)Miscellaneous
• chem|st opened the meeting on March 18 2014 20:32 UTC and welcomed the participants.
• Meeting attendees introduced themselves by stating their real names for record.
• chem|st was appointed the Chair of the meeting, and juiceme was appointed the Secretaty.
• The assembly accepted articles of incorporation and the association rules unanimously. Thus Maemo Community Association is founded by the present company, and all present are named active members of the community.
• juiceme, nieldk and chem|st were nominated for directors of the association. All accepted the nomaination and were voted unanimously for the position.
• The directors accepted Board's Internal Regulations unanimously
• chem|st was nominated as board's Chairman, juiceme was nominated for Secretary and nieldk was nominated for for Treasurer. All accepted the position and were voted for unanimously.
• The current Maemo Council, consisting of DocScrutinizer05, chem|st and juiceme was nominated for the Council of Maemo Community Association. The vote for council was unanimous.
• juiceme was nominated as Chairman of the Council. He was voted for it unanimously and accepted the nomination.
• It was decreed that with reference to the Statutes and Association Rules passive membership generally is free of any charges. Any payment of fees for active or honoured members is suspended for the time being.
• The board of directors was assigned to do all nescessary steps to register the association at the district court.
• The chairman thanked all assembled and closed the meeting at 21:27 UTC

1 0

24 Mar 2014 7:30am GMT