1,010 karma · joined February 16, 2014
President & Managing Member of Plyint, LLC (https://plyint.com)
https://gs.statcounter.com/os-market-share/mobile/united-sta...
1) Amazon has been running there own app store successfully and that has worked out well enough for them that they continue to do so and a lot of Kindle Fire owners seem to enjoy that experience.
2) Few companies are Amazon though and the ability to operate 3rd party software outside of the purview of Google's own store is severely hamstrung for most others. This has also been called out by Epic Games previously.
https://www.theverge.com/2020/4/21/21229943/epic-games-fortn...
Google puts software downloadable outside of Google Play at a disadvantage, through technical and business measures such as scary, repetitive security pop-ups for downloaded and updated software, restrictive manufacturer and carrier agreements and dealings, Google public relations characterizing third party software sources as malware, and new efforts such as Google Play Protect to outright block software obtained outside the Google Play store.
So even Google may eventually face legal issues regarding their anti-competitive app store practices. If big tech is forced to legitimately compete with other app stores, then continuing to charge a 30% fee will become untenable.
I don't think the author's description of GitHub Sponsors is exactly correct. Technically, the sponsorship is at the user/organization level, so if you make a donation it goes to the organization/user, which may have MULTIPLE projects going on. This is the way I have set it up for our company Plyint (https://github.com/sponsors/plyint).
Although I would very much like GitHub to implement a pool of organizations/users, which is maybe what the author meant?
Does your synology utilize BTRFS? If so, what is your experience with it? I'm currently using a FreeNAS box that runs on ZFS that has been very reliable for me over the years. I can't really see giving up the power/reliability of ZFS to move to a synology setup, but I like to keep tabs on BTRFS progress.
Since, we were on Keybase already for employee identity and chat, we created an extension to encpass.sh to use Keybase for our secret storage. (https://github.com/plyint/encpass.sh/blob/master/extensions/...) It has been working really well so far, as when we add someone to a Keybase team, that person immediately has access to that team's secrets. No extra setup required.
(1) Setup Resilio sync on my NAS
(2) Shared the folder holding the kdb file via Resilio Sync
(3) Entered the code into the Resilio Sync mobile app
(4) Performed an initial sync of the folder to my phone
(5) Downloaded Strongbox and pointed it to the kdb file under the "Sync" location in Files on iOSI gave this up though as Resilio will detect conflicts and prevent overwriting in case that did happen and I make automated nightly backups of my password file, so I can restore the file if I ever did "lose" a password. I've been running with my current setup and haven't had to restore yet.
Also, I don't use Resilio's proxy servers either, so all of this is 100% running on my own infra. I have Wireguard setup on my home network, so if I am away from home, I can "VPN" in on my phone and then open the Resilio Sync app to sync up remotely.
By having the help documentation in a function in the middle or towards the end of the file, I don't have to page down through the help documentation to get to the code that is actually doing things. If I'm really interested in the help documentation, then I'd prefer to look at the nicely formatted version output by the script (<script> --help or whatever) rather than looking in the actual script code anyway.
Admittedly, this may be more of a subjective personal preference item.
I also like to feed a heredoc directly into man, which allows you to achieve nicer formatting for the help documentation. Something like this...
man -l - << EOF
.\" Manpage for encpass.sh.
.\" Email contact@plyint.com to correct errors or typos.
.TH man 8 "06 March 2020" "1.0" "encpass.sh man page"
.SH NAME
encpass.sh \- Use encrypted passwords in shell scripts
...
EOF
See encpass.sh for a working example of this -> https://github.com/plyint/encpass.sh/blob/master/encpass.shDid you start to experience performance issues as team size increased? Did you have a lot of issues or data held in the issues? Or was there another issue that you think led to the slowness?
I'm interested in your insights as we went with JIRA initially, since it was pretty much the gold standard and we thought it would scale nicely as we added team members, but if it is not going to do so, then it may not be worth the JIRA premium.