UBports Robot Logo UBports Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. Fuseteam
    3. Posts
    Offline
    • Profile
    • Following 0
    • Followers 3
    • Topics 3
    • Posts 59
    • Groups 0

    Posts

    Recent Best Controversial
    • RE: snap pop crackle! ....and nix!? The future of crackle

      thanks to the help of @ChromiumOS-Guy crackle is now not only able to set up nix home-manager, but also install, update, remove and list packages using nix home-manager:

      https://github.com/tuxecure/crackle/releases/tag/v0.5.2

      for cli applications they all seem to work so far, sans minor warnings (looking at you tailscale)
      for gui applications i have not figured out how to get it be picked up by the drawer, but early reports show them launching fine from the terminal so far

      So for anyone wanting to test it out, now the time to test out and see how far we can push the boundaries

      posted in General
      FuseteamF
      Fuseteam
    • RE: snap pop crackle! ....and nix!? The future of crackle

      @ChromiumOS-Guy thanks again, i'll take a look and test it out further

      posted in General
      FuseteamF
      Fuseteam
    • RE: snap pop crackle! ....and nix!? The future of crackle

      actually now i think about it, updates are easy enough with home-manager:

      nix-channel --update
      home-manager switch
      

      The "challenge" is more in figuring out how we add and remove entries under home.packages in ~/.config/home-manager/home.nix

      posted in General
      FuseteamF
      Fuseteam
    • RE: snap pop crackle! ....and nix!? The future of crackle

      @ChromiumOS-Guy said in snap pop crackle! ....and nix!? The future of crackle:

      @Fuseteam first let me say this is awesome, second if you want help I want to contribute to this.
      I used nixos for while before switching to FreeBSD is has been a joy, so I say this with confidence this is finally the point where we can actually use UT as a full on linux distribution, the influx of packages here will be amazing.

      if you don't mind aside from reading up on the code, I will make a UI QML app so end users can just pick and install/uninstall primitive but any UI is better then terminal when walking.

      looking forward to seeing a repo on gitlab.

      thanks, the script above is all that's needed to setup nix on UT on the latest focal devel.

      I agree with the UI idea, i believe it would be best if we add a plug in system-settings like so: https://gitlab.com/ubports/development/core/lomiri-system-settings/-/merge_requests/437

      if you rather see the setup script on gitlab you can find it here: https://gitlab.com/tuxecure/crackle-apt/crackle/-/blob/v0.5/crackle

      note that that's the only file i have so far, i'll be building that out further, based on the earlier iteration which can be found in the bash branch= but that's just for a cli interface

      I'm unsure atm how we will handle actual package management throught the UI tho but i'd say we can worry about that after we can at least setup nix via the UI

      posted in General
      FuseteamF
      Fuseteam
    • RE: snap pop crackle! ....and nix!? The future of crackle

      ok final last word; you may run into this error on focal devel:

      35b520fd-fc7d-40f1-8ab9-a45a76eb20cc-image.png

      don't worry it is noisy, but it harmless

      It will be fixed in noble see https://gitlab.com/ubports/development/core/hybris-support/tls-padding/-/merge_requests/4
      and possibly in focal soon™

      posted in General
      FuseteamF
      Fuseteam
    • RE: snap pop crackle! ....and nix!? The future of crackle

      Oh before i go, you may be wondering how to use this home manager

      well it's simple really.

      after running the script in the above post you should have a file in ~/.config/home-manager/home.nix

      in there you will find a section like this:

      # The home.packages option allows you to install Nix packages into your
        # environment.
        home.packages = [
          # # Adds the 'hello' command to your environment. It prints a friendly
          # # "Hello, world!" when run.
          # pkgs.hello
      
          # # It is sometimes useful to fine-tune packages, for example, by applying
          # # overrides. You can do that directly here, just don't forget the
          # # parentheses. Maybe you want to install Nerd Fonts with a limited number of
          # # fonts?
          # (pkgs.nerdfonts.override { fonts = [ "FantasqueSansMono" ]; })
      
          # # You can also create simple shell scripts directly inside your
          # # configuration. For example, this adds a command 'my-hello' to your
          # # environment:
          # (pkgs.writeShellScriptBin "my-hello" ''
          #   echo "Hello, ${config.home.username}!"
          # '')
        ];
      

      you can see the comment there explains what to put there, you here's how i edited mine

      # The home.packages option allows you to install Nix packages into your
        # environment.
        home.packages = [
          pkgs.vim
          pkgs.pipx
          pkgs.cargo
          pkgs.plasma5Packages.kdeconnect-kde
          pkgs.tailscale
          pkgs.gnumake
          pkgs.gcc
          pkgs.gdb
          pkgs.strace
          pkgs.valgrind
          # # Adds the 'hello' command to your environment. It prints a friendly
          # # "Hello, world!" when run.
          # pkgs.hello
      
          # # It is sometimes useful to fine-tune packages, for example, by applying
          # # overrides. You can do that directly here, just don't forget the
          # # parentheses. Maybe you want to install Nerd Fonts with a limited number of
          # # fonts?
          # (pkgs.nerdfonts.override { fonts = [ "FantasqueSansMono" ]; })
      
          # # You can also create simple shell scripts directly inside your
          # # configuration. For example, this adds a command 'my-hello' to your
          # # environment:
          # (pkgs.writeShellScriptBin "my-hello" ''
          #   echo "Hello, ${config.home.username}!"
          # '')
        ];
      

      then when done you run home-manager switch, and off you go

      It is switch because it is atomic, you can go back to a previous configuration— but it'll let you explore home-manager --help for the other options

      and yes, if i've tested all those, they all.....work expect for kdeconnect:

      12e1028e-3746-4e3e-8c9d-7f928eb434f0-image.png

      This is must closer than i got with crackle tho, i imagine there will be similar errors with other GUI apps, but CLI apps ought to work—

      posted in General
      FuseteamF
      Fuseteam
    • snap pop crackle! ....and nix!? The future of crackle

      Hey there, i'm fuseteam, but you may know me better as Tobiyo Kuujikai on Telegram.

      Almost 4 years ago i made post https://forums.ubports.com/topic/6283/snap-crackle-and-pop-readwrite-rootfs-is-overrated
      ...oh wow 11th of june, that was exactly 4 years and 5 days ago— gosh time sure flew

      At the time i was looking for way to run my favorite command line tools on UT, as i wrote back then it started with remounting as readwrite. As i'm sure many of you are quite aware that is not permanent, it gets overwritten by OTA updates, and there is a chance things will not break cue white screen of death

      So my motivation was, rather than fighting with the OS why don't i work with the OS and the journey at some point i past by nix, it looked perfect, if it was for it actually building the linux kernel on device to setup the thing— So i gave up on that.

      Now if you listened to the Q&A last saturday the sharp eared among you may have heard something related to nix was merged— yes that was me, nix finally does not need to compile packages it can actually install packages now! Wait so what's crackle about?

      Well. as nix wasn't viable at the time i search for other things. Did you know that .deb files are actually tar balls? that is you can extract them.....and the tools to do that are on UT

      so i played with that, it turns out you can download from the repository with apt without installing and you can tell apt where to download it. It hit me what what is actually doing in simplfied terms. maybe if i illustrate it, it will seem stupidly simple to you too— here's the firefox deb from upstream extracted:

      e6cb53b3-5e78-4722-bfc6-1d6d465a761f-image.png

      .....do you see it? Does the structure look familiar to you? where did we see that usr folder before— that's right in your / directory.....

      Yes, what you're guessing is correct, all apt really does, in simplified terms, is download the deb files, and extract it over your system. So how hard can it be to extract to somewhere else? Very easy, that is how ufirefox came about— we download the deb, we extract deb, we package de folder as click; yes click too is tar bal, in fact it is based on the deb format.....or so i am told.

      The challenge is telling the binaries to not look in / but somewhere else— but where? well there is specification from freedesktop (https://www.freedesktop.org/software/systemd/man/file-hierarchy.html#Home Directory) that we could use so i made mapping:

      /var/cache/           -> $XDG_CACHE_HOME  ($HOME/.cache/)
      /etc/                 -> $XDG_CONFIG_HOME ($HOME/.config/)
      {/usr}/bin/           -> $HOME/.local/bin/
      {/usr}/lib/{arch-id/} -> $HOME/.local/lib/{arch-id/} 
      /usr/share/           -> $XDG_DATA_HOME   ($HOME/.local/share/)      
      /var/log/             -> $XDG_STATE_HOME  ($HOME/.local/state/)
      

      and wrote a bash script, to move files to these locations, then i opted to move them to ~/.local/share/crackle and symlink them instead and then it worked— but libraries weren't loading.....and how do keep track of which files belong to which packages and ahhh— utlimately i did find solutions, but something else was also apparently, i was doing this mostly on my own, it took 3 years to figure out how to remove packages, not because it is difficult, but i didn't think of— giving each package their own directory and that didn't could clear unused libraries— after all those could be shared— and another year to spot a minor mistake which made linking the libraries properly a complete mess........ did mention that crackle was born....yeah that bash script is crackle: https://gitlab.com/tuxecure/crackle-apt/crackle

      At this point, i'm sure you can understand why, when i discovered that nix now no longer needs to build from scratch on arm64, i was both elated and sad
      elated because now i didn't need to deal with figuring out package managment, sad because i spend 4 years figure out package management.

      But all is not lost, crackle can still be used to build clicks— uh what else........ uh let's first get back to nix

      What is nix first of all? Nix is the package manager of nixos, it installs into /nix ok straighforward enough, it has 80k packages available— oh that's ni— 80000?! yes that's 4 zeros.
      my measily, in the four years crackle was out i've accumalate 16 packages that were test 😂 (https://gitlab.com/tuxecure/crackle-apt/cracklebin)

      And they work.......ok fine there are some limitations. first of all it cannot do system systemd services, you know the thing that goes in /etc/systemd/system, we'd have to write those manually.

      Now back to what was merged last week: as of right now /nix is writable by a phablet— that's about it. yes it is that simple, and that's all it took to make Nix installable— almost
      You see nix has 2 modes, multi-user mode and single-user mode.

      As we don't support multiple users on UT (yet) i opted for the simpler single user mode and that only needs /nix to be writable.......and adds the limitation of not being able to sudo vim— but you know.....i ran into this aswell with crackle.......the solution? make a symlink to /root/.local/bin which means i can sudo su and then vim just works— now sudo -i vim also works.

      But i'm rambling....point is i added function to crackle to do that— and this is still usable with nix.

      Wait did i say nix is almost installable? uh yeah about that, to install it we need both curl and xz......both of which are not shipped by default, and I don't want to increase the rootfs size— hey both of these work with crackle......

      I now took crackle apart once again and made a new bash script to install nix:

      #!/usr/bin/env bash
      # Configuration for Apt
      APTCACHE=${APTCACHE:-${XDG_CACHE_HOME:-$HOME/.cache}/apt};
      APTSTATE=${APTSTATE:-${XDG_STATE_HOME:-$HOME/.local/state}/apt};
      DPKGSTATE=${DPKGSTATE:-${XDG_STATE_HOME:-$HOME/.local/state}/dpkg};
      APTCONFIG=${APTCONFIG:-${XDG_CONFIG_HOME:-$HOME/.config}/crackle};
      
      # Configuration for Crackle
      PKG_PATH=${PKG_PATH:-${XDG_DATA_HOME:-$HOME/.local/share}/crackle};
      PKGS_DIR=${PKGS_DIR:-$PKG_PATH/$PKG};
      CRACKLERC=$APTCONFIG/cracklerc;
      CRACKLEENV=$APTCONFIG/environment;
      CRACKLECMP=${XDG_DATA_HOME:-$HOME/.local/share}/bash-completion/completions;
      CRACKDIR=${CRACKDIR:-$HOME/packages/$PKG};
      CRACKLEBIN="https://gitlab.com/tuxecure/crackle-apt/cracklebin/-/archive/master/cracklebin-master.tar.gz"
      PKG_PREFIX=${PKG_PREFIX:-$HOME/.local}
      
      # Configuration for Sudo -i
      SUDO_CONFIG=/root/.config
      SUDO_BIN=/root/.local/bin
      SUDO_STATE=/root/.local/state
      
      # Set up aliases for apt commands
      APTCONF="-o Dir::Etc=$APTCONFIG";
      APT_GET="apt-get -o Dir::Cache=$APTCACHE -o Dir::State=$APTSTATE $APTCONF"
      APT_CACHE="apt-cache -o Dir::Cache=$APTCACHE -o Dir::State=$APTSTATE -o Dir::Etc=$APTCONFIG"
      
      function pkgsetup(){
          [[ -d "$DPKGSTATE" ]] || {
              mkdir -p "$DPKGSTATE";
                  cp /var/lib/dpkg/status $DPKGSTATE/status;
              }
      
          [[ -d "$APTCACHE" ]] || mkdir -p "$APTCACHE";
          [[ -d "$APTSTATE" ]] || mkdir -p "$APTSTATE";
      
          [[ -d "$APTCONFIG" ]] || {
              mkdir -p $APTCONFIG/sources.list.d $APTCONFIG/preferences.d $APTCONFIG/trusted.gpg.d;
      
          ln -s /etc/apt/sources.list $APTCONFIG;
          [[ -n "$(ls /etc/apt/trusted.gpg.d)" ]] && ln -s /etc/apt/trusted.gpg.d/* $APTCONFIG/trusted.gpg.d/;
      }
      }
      
      urldecode() { : "${*//+/ }"; echo -e "${_//%/\\x}"; }
      
      function get_pkg_info () {
          pkg="$(basename "$1")";
          pkgname="${pkg%%_*}";
          pkgversion="${pkg%_*}";
          pkgversion="${pkgversion#*_}";
          pkgversion="$(urldecode $pkgversion)";
      }
      
      function link_path(){
          pkg_path="$1";
          xdg_lib_path="$2"
          while read file_path
          do
              ln -s $file_path $xdg_lib_path;
          done < <(find $pkg_path -type f -maxdepth 1)
      }
      
      function bin_install () {
          PKGS_DIR=${PKG_PATH}/${pkgname}
          mkdir -p ${PKGS_DIR} $PKG_PREFIX/bin;
          dpkg-deb -x "${package}" "${PKGS_DIR}";
          [ -d "$PKGS_DIR/usr/bin" ] && link_path $PKGS_DIR/usr/bin $PKG_PREFIX/bin;
      }
      
      function setup_curlxz () {
          $APT_GET update
          $APT_GET install --download-only curl xz-utils;
          while read package
          do
              get_pkg_info $package;
              bin_install;
          done < <(ls "$APTCACHE"/archives/*.deb);
      }
      
      function setup_home_manager (){
          sh <(curl --proto '=https' --tlsv1.2 -L https://nixos.org/nix/install) --no-daemon
          nix-channel --add https://github.com/nix-community/home-manager/archive/master.tar.gz home-manager
          nix-channel --update
          nix-shell '<home-manager>' -A install
      }
      
      function pkgunset(){
          rm -r $APTCACHE $APTSTATE $APTCONFIG $PKG_PATH;
          find "$PKG_PREFIX/bin" -xtype l -exec rm {} +;
      }
      
      pkgsetup;
      setup_curlxz;
      setup_home-manager;
      pkgunset;
      

      ok this has more cruft than it should.....but there is a reason for this.

      You see now i have crackle which has functions that make command line utils usable, on the other hand we have nix with way more usable packages.

      So what's the plan?

      The plan is take crackle apart for useful parts and build it around nix instead.

      So the goal for next iteration of crackle is

      • crackle click should continue to able to build click packages from apt
      • crackle setup should set up nix home-manager utilizing curl and xz from apt
      • crackle sudo should continue to be able to enable sudo usage with user installed packages
      • crackle sudok should continue to undo crackle sudo

      The above script installs curl and xz the crackle way, then sets up nix home-manager and then removes them again and wll serve as the base to build out the features anew

      If you made it this far in my post— thank you for reading my post despite its length! Feel free to use the above script to install nix on the latest focal devel and go wild. See what works and see what does not. And if something doesn't work— share logs, debug, explore options! I doubt i alone can solve these issues, but together as a community we can surely find solutions— if not maybe i'll post another rant in 4 years and 5 days 😛

      posted in General
      FuseteamF
      Fuseteam
    • RE: uWolf (LibreWolf)

      Do note that some of these issues are due to integration of the desktop browser into UT, not necessarily something that can be solved in the packaging.

      Some of these bugs will have to be taken up with upstream (e.g. menu and tabs going offscreen and setting pages not fitting the screen), others will have to solved in UT (e.g. right side being unusable in landscape)

      Some are being looked into e.g. right side being usable will afaict be fixed by https://gitlab.com/ubports/development/core/lomiri/-/merge_requests/207 and the settings page not fitting might be improve the new design lands: https://connect.mozilla.org/t5/discussions/firefox-settings-design-share-your-input/m-p/66629/highlight/true#M23625

      While i am sure that donations are appreciated, do keep in mind this won't brings fixes faster as there is only so much we can do.

      Have ideas how firefox (and by extension librewolf) can be improved for us? share ideas to upstream, but be nice and be mindful these things takes time* to fix and may not be their current priority. Showing genuine interest, doing research if something has been proposed before and sharing ideas so they may gain traction is highly appreciated

      * to help shape perspective It took 3 years (compare the date on https://connect.mozilla.org/t5/discussions/arm64-armhf-firefox-binary-tarballs-for-packaging-for-ubuntu/m-p/12847 with https://www.mozilla.org/en-US/firefox/136.0/releasenotes/) for them to finally package for arm64 in their own apt repo, in part because it took that long of sharing for it take traction but also in part due to changes they had to made

      posted in App Development
      FuseteamF
      Fuseteam
    • RE: Is there a better browser somewhere?

      @paulcarroty said in Is there a better browser somewhere?:

      uFirefox is still far from having an android-style mobile experience

      Still the best browser for modern websites on UT.

      I wouldn't call it the "best" given how the settings pages aren't convergent xd

      posted in Support
      FuseteamF
      Fuseteam
    • RE: Is there a better browser somewhere?

      @uxes said in Is there a better browser somewhere?:

      @domubpkm well sure, but not every latest build is allright
      https://gitlab.com/debclick/uFirefox/-/jobs/7676432640/artifacts/browse this should be pretty ok

      Oh wow this is really old, for clarity the latest artifact on the xmir-focal branch should be alright
      here's for firefox 136: https://gitlab.com/debclick/uFirefox/-/jobs/9342376608/artifacts/browse/build/aarch64-linux-gnu/app/

      posted in Support
      FuseteamF
      Fuseteam
    • RE: On the subject of Ubuntu Touch versioning scheme

      I would like to propose option 2 but keeping the "." between year and month

      so if the next version is released in may 2025 it would be called 25.05.0

      this has all the benefits of opton 2, feature releases and bugfix releases included while not distancing ourselves from the broader ubuntu community any more than we already have (identity wise)

      i think we can work around the confusion with the Ubuntu version we're based on by utilizing code names in the release announcement similar to upstream ubuntu

      e.g. Ubuntu 24.04 Noble Numbat vs Ubuntu Touch 25.03.0 Marvelous Moon

      the benefit of the scheme is that is easy to see when the version was released while keeping a distinction clear between feature and bug-fix release. keeps the version short and memorable while
      paying homage to the broader community

      posted in General
      FuseteamF
      Fuseteam
    • RE: Documentation temporarily offline

      Looks like the docs.ubports.com is now back thanks to @mariogrip turning off and on for the umpteenth time—

      posted in General
      FuseteamF
      Fuseteam
    • RE: Documentation temporarily offline

      @doniks said in Documentation temporarily offline:

      yes. both Cloudflare, but that was also true with the old setup. not clear what's different now

      I mean is the same user for http://docsubportscom.readthedocs.io/ and http://docsubportscom-gitlab.readthedocs.io/?
      could it be that to cloudflare docs.ubports is from one user and is now "hijacked" by another?

      i also tried running dig docs.ubports.com and i got this as output:

      ; <<>> DiG 9.18.30-0ubuntu0.24.04.1-Ubuntu <<>> docs.ubports.com
      ;; global options: +cmd
      ;; Got answer:
      ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 31353
      ;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1
      
      ;; OPT PSEUDOSECTION:
      ; EDNS: version: 0, flags:; udp: 65494
      ;; QUESTION SECTION:
      ;docs.ubports.com.              IN      A
      
      ;; ANSWER SECTION:
      docs.ubports.com.       300     IN      CNAME   readthedocs.io.
      readthedocs.io.         300     IN      A       104.16.254.120
      readthedocs.io.         300     IN      A       104.16.253.120
      
      ;; Query time: 287 msec
      ;; SERVER: 127.0.0.53#53(127.0.0.53) (UDP)
      ;; WHEN: Fri Jan 17 10:26:19 -03 2025
      ;; MSG SIZE  rcvd: 105
      
      

      But i am unsure if this is correct, as i don't have an output of how it was before

      posted in General
      FuseteamF
      Fuseteam
    • RE: Documentation temporarily offline

      hmmm according to the error this is the issue: The host is configured as a CNAME across accounts on Cloudflare, which is not allowed by Cloudflare's security policy. are the two separate accounts?

      it also says: If this is an R2 custom domain, it may still be initializing. If you have attempted to manually point a CNAME DNS record to your R2 bucket, you must do it using a custom domain. Could it be just dns intialization? do we have other logs in the dashboard?

      also http://docsubportscom.readthedocs.io/ still works, so perhaps that could be a stopgap until we figure this out

      posted in General
      FuseteamF
      Fuseteam
    • RE: OP5T removed from device list 20.04...

      @Luksus said in OP5T removed from device list 20.04...:

      Just need to figure out, why it was removed in the list of supported devices, maybe because of inactivity/no progress in the last year...

      to make it clear the short answer is: yes, a device that has reached the stage "Advanced Support" will be demoted to "Basic Support" when there is no activity for 6 months, if there is no further activity for another 6 months the device is removed from the list

      support in this case means: someone is activity fixing issues on the device
      Activity is the activity in the device repository

      posted in 20.04 Focal Fossa
      FuseteamF
      Fuseteam
    • Spotify arm snap on Ubuntu Touch

      With snap support being worked on and snap being the official supported way to install spotify via snap, this could open a way to install spotify on Ubuntu Touch!

      However spotify doesn't currently build an arm version for linux 😞

      so i submitted an idea to spotify to support arm :smiling_face_with_sunglasses:

      if you use spotify and want to use it on Ubuntu Touch. come on over and vote! https://community.spotify.com/t5/Live-Ideas/arm64-support/idi-p/6551110

      posted in General
      FuseteamF
      Fuseteam
    • RE: Beta Bug-Reports - CatWithCode

      @CatWithUT hmmm no hub, not sure then what it could be

      posted in Fairphone 5
      FuseteamF
      Fuseteam
    • RE: Beta Bug-Reports - CatWithCode

      @CatWithUT said in BUG: USB-OTG Hard Crashes Phone:

      @Fuseteam That is what beta tester are for

      hah! fair. I stand corrected XD

      posted in Fairphone 5
      FuseteamF
      Fuseteam
    • RE: I am about to give up and leave

      @jojumaxx said in I am about to give up and leave:

      There's Libertine and Snap support which don't help with the mobile experience. If I want to have a tablet or laptop, I use a tablet or laptop.
      Convergence is good as a bonus, if the basis works. It's called Ubuntu Touch, but touchable is nothing. Don't forget, that this is about phones.

      I am just a Linux user, but UT is the only system I encountered yet, that doesn't allow me to use a package manager freely. Everything would be perfect if that was possible...at least I guess so...

      These two concerns contradict each other

      on one hand you feel that snap support is missing the point, on the other hand you feel that install apps with apt would solve the app issue....

      Just as apps installed with snaps are not "touchable", apps installed with apt are also not touchable. The snap support is meant to address the issue have with the inability to use apps.

      If you have apps that would well on droidian via apt, packaging those as a snap would bring it over to ubuntu touch, that would be up to the developer of that app however.

      It is the same with banking apps— we can't have banking apps, if the banks behind those apps don't port them over to ubuntu touch

      The outdated browser is a big issue yes, there are multiple effort attempting to solve that, the current rebase to 24.04 might help eleviate that to some degree, alfred's mimi browser is a work in progress that will likely solve the issue aswell, once finished i suspect it'll replace morph altogether, there is also ufirefox which is PoC repackage of desktop firefox with all usability issues.

      If Ubuntu Touch doesn't fit your usecase, but other mobile linux distros do— perhaps you could outline those usecases. I would be particularly interested what apps you find useful on droidian that you would like to see on ubuntu touch, perhaps we can get them installed with snap or maybe repackaged for the open store 😉

      posted in General
      FuseteamF
      Fuseteam
    • RE: OpenStore payment system discussion

      The main idea here is: The OpenStore would not need to process the the payment, because it is done by multiple third parties (people who mine Litecoin or who have Litecoin nodes) and the OpenStore only provides an address and looks if there is anything transferred to that address. But the developer would probably need to take care of legal matters as taxes when he receives Litecoin to his wallet or later transfers them into "normal" money.

      And just to be clear: Litecoin was chosen here as one of many possible solutions, because it works and is well established. I could have also chosen Bitcoin, but the confirmation times and the fees are lower with Litecoin.

      The challenge here then becomes, if someone pays and wants a refund because they are not happy with what they get, where do they go? the first where they will go is the ubports foundation, then the openstore team, by the time they reach where they should be— the damage's already done.

      posted in General
      FuseteamF
      Fuseteam