It is true I didn't market it, so possible it suffered a bit from that. Some of the 'Doesn't work on my device' comments were a bit unexpected (and unsolvable without $$$ to test on the devices), so I didn't want to spend money promoting it with issues. I was charging $3 I think, it has been awhile.
There was another seemingly popular paid ringtone app at the time, but I can't recall what it was. And a search now for 'android ringtone app' now brings up lists of 'Top X ringtone apps of 2018/2019' populated exclusively by free apps.
As a business idea I don't think it would take off. I had a somewhat related project idea to rotate ringtones.
Such an idea can be done on Android, but would have been impossible on iOS (at the time, have not looked into it since).
It was mildly popular for download on the store, but supporting issues on various phones was a hassle, and Android update occasionally changed the required APIs. Currently the project is broken and on the back-burner to get it fixed again. However, it is freely available if you want a look.
Not mentioned, but for node.js dev termux almost gets there, but just falls short. You can't hit a node.js server running in android/termux from a full fledged local ChromeOS browser tab. It doesn't have port access. Have to go run an android browser.
Alternatively, I've been just doing browser based dev. The free GCP google cloud shell lets me edit and host so long as I have a connection. If I wanted I could still keep it in sync with git running under termux.
> Github recommends using the same contact procedure for anti-circumvention takedown requests as for normal DMCA takedowns
I made this mistake to, Admiral's blog post does imply it. However, they were making a DMCA take down request, based off the reasoning it was for anti-circumvention.
However, that defense is a bit flimsy to me since the fall back to having the paywall blocked could/should be a "Paywall blocked, please disable your addblocker to gain access to our content" msg.
Anyhow, that is immaterial because so long as they don't actually serve adds, Easylist could/would have removed the line no problem. Admiral should have just said "Our domain doesn't serve adds, we work on paid content access" and they would have been removed without all this hassle.
I attempted to switch to Yarn immediately, but actually hit one of the few issues they ended up documenting (can't remember which now). Never actually ended up switching, so no need to switch back.
Study seems to exclude e-ink, (when grouping kindle with iPad, I assume they mean the android tablet) while many of the comments here are arguing about e-ink vs books.
I'm not surprised by the study. My 2.5 year old would much rather watch something if the tablet is available than read. Even the interactive and pictures + audio books aren't much competition.
Free f1-micro instance! That is nice. I was paying for one to dev test a webapp on. Not quite clear if it is per account or per project. Guessing per project.
Google Cloud Shell: Not sure that was free before? Looks like an excellent place to run ansible playbooks from. I could swear I had thought that before, but rejected it due to costs.
I can see myself giving some of the other services a try, not sure what didn't have free tiers before that do now other than the above.
Special weights to place in cars/bikes/vehicles with little inertial mass, but heavy gravitational mass would improve traction but not affect acceleration (on a flat plane).
If you took the opposite to extremes, high inertial mass with low gravitational mass...remember the whole planet is moving quite quickly! The reason it sticks together is everything is moving relative to everything else. So, such a material would likely not be able to exist free-standing on the planets surface, it'd be ripped away by inertia. It'd make an interesting fuel for lift off if it could be harnessed.
pfffft Bunch of yammering without any good analysis. Disappointing.
The new terms don't do anything except make explicit what they were already doing.
D.7 + D.4: They were already doing activities these terms explicitly give them the right to do. They are internally copying (backups), modifying (compressing and indexing), and displaying anything uploaded. If having it spelled out violates your license, I don't see how them just doing it without having it spelled out doesn't also violate the license. Maybe this just shifts where the license violation is occurring from GitHub's doing to a user's uploading, but it doesn't change the fact that a license is being violated somewhere on either the old or new terms.
D.5: This section was already in the old terms! The new terms actually clarify and limit what they mean by "fork". It still doesn't give the forking user a right to modify, just create their own copy within the context of GitHub. You already granted users the right to "fork" anything publicly submitted under the old terms.
D.3: The rant (the writers own tag, but I find it appropriate) is just nitpicking here. It om-mitts the reason why they would remove content, which is because it violates their policies. GitHub needs this right to enforce their content restrictions. Also, if GitHub ends up removing partial content such that it violates the license it was submitted with YOU aren't the one breaking the license. They are.
The new license grant to others is nicely explicit on what permissions are granted on an unlicensed repo vs the old vague "you agree to allow others to view and fork your repositories." Note that you CANNOT legally edit your fork of an unlicensed repo. That would be violating the original repos copyright.
Ansible brings inventory management to the table. I can have an inventory with my backend and frontend instances tagged, run my playbook, and it will copy/start the appropriate systemd units.
I've been telling friends and co-workers I think kubernetes has won the orchestration war. But even as I did so I wanted something simpler for my own purposes, and so was using fleet.
Luckily for me, I'd stuck with making all my units global and driving their deployment off of metadata. I think I'll just strip off the [X-fleet] section, and start deploying them straight to systemd with ansible.
Notice how the lines are stretched,
Not every hexagon in the tiling represents the same area if mapped back to a sphere. The non-polar edges of the tiles pictures are larger. If you actually printed it out, and tried to wrap it around a globe, the middles would have to expand or the edges would have to shrink for the tiles to join.
Edit: Basically he hasn't actually tiled a sphere with regular hexagons (which is what the proof said was impossible. He has titled a flat projection of a sphere with regular hexagons, which would have to be morphed to irregular hexagons if tiling a sphere when the projection was reversed.
Not taking away from the tiling, which is quite interesting in itself.
Looks cook tech wise, snappy. But there is an utter lack of information. Is it running locally, or submitting code to some remote server with no privacy policy? Submitter seems to be the dev? This is the 3rd time submitted in the last 26 days. Found a github account with nothing except a terse readme.
But this isn't a case of two different markets...Google makes no money off of Chrome. They make money off of advertising. The bottom line of Chrome is that it is just there to view advertising. The better they can make it, the more it will be used, and the more advertising will be viewed (hopefully Google's)