A static site may use JS, but doesn't require server-side logic (PHP, databases, or any other type of dynamic content). In this case OP implies that it doesn't even require a build (because you may create a static site through a build process -like Jekyll does, for example-).
OP shared an opinion backing it with links to more information. What are your disagreements? Could you give a fundamented counter-opinion besides your snarky response?
At this point wouldn't it make sense to just rewrite it from scratch? I'm sure there are projects already doing this (take a look at this one for example! https://webamp.org/)
Last.fm allows you to track your whole listening history (and you can export it or play with their API). I agree it could be interesting to infer something valuable from what a person likes (musically), but I don't know if there's much to read between the lines other than "if user likes artist X probably will like artist Y". You may infer my location (from local artists listened), and from that paired with timestamps you could tell some of my habits (work, school, commuting). Personal taste can hint an age group and gender as well, but it wouldn't be precise at all. Perhaps mood? I don't see much value on that info, compared to what you can gather from navigation history, messages or other services.
As someone who lives in a city where ~15 mbps is the max you can get... this is accurate. Streaming in 1080p with high quality may not work. Downloading a game over 80gb requires a couple of days. Oh, and I have just 1mbps upload, so syncing a video from my phone to Google Photos may take a couple of hours as well. ISPs need competition.
Because it was convenient and powerful. Ever since Google Reader shut down I lost track of technology news. Yes, I can read the same sites/blogs I read before one by one, or subscribe to their newsletter, or follow them on Twitter... but it's not the same. And the tools that were available to replace Reader were always short in some aspect. Google Reader was killed in favor of Google+ (which failed horribly). After that RSS went downhill.
RSS readers were useful because you had all the news/posts in one place (instead of many browser tabs/newsletters/social accounts). You read, curated and shared from the same place, and you were able to easily choose what categories you wanted to read and when.
I'm not a person who uses to return products, and I had mine for just two weeks. It was constantly reading/writing to disk. All the time. It wasn't indexing: the QNAP system has a lot of small services and some of them write logs to disk or do god knows what. Given the particular architecture of the NAS processor I wasn't able to install cli tools to analyze the problem further, but at this point I realized the NAS wasn't doing what I wanted in the first place: ease my life and allow me to automate backups.
I ended up adding one of the disks to my PC and the other to a home server.
I must admit though that the QNAP solutions look very helpful if you disregard the abusive disk R/W activity and the inconsistent UI. You may be able to set up complex backup schemes quite fast with it.
If you are interested in virtualization and advanced usage, be sure to get one with an ARM processor at least, because it may be difficult to get packages for it on other obscure architectures.
It's worth noting that AEM is often very badly set up, following requirements from managers who have no idea or concern about web development, and later maintained by low cost content editors who barely know some HTML. Moreover, this CMS seems to be a standard for big sites even though the licenses are costly, development is slow and complicated, and it adds a lot of human hours to the site maintenance.
Google Reader was free. I can't afford 50 usd/yr just to read RSS feeds (yes, there's a free plan, but it's limited and at that point I'd rather stick with RSSOwl or similar -free- tools).
Thanks for your reply! But it doesn't answer my question: I'm worried about how you will sustain your platform in the long run for all those free tier users.
Learning a new tool -even if it's friendly and has a community around it- takes time and effort. We want to know it will be there in the future. That's why I'm interested to know: how are you planning to keep Pipedream alive for, let's say, the next 5 years?
It looks like an interesting alternative to Zapier (or its open source counterpart n8n [1]).
As a potential user, before even trying the tool I'd like to know how are you planning to monetize it. Free sounds awesome, but you'll get to a point where it costs you actual money to keep all this working. I don't want to waste my time creating pipelines in a tool that won't exist in a year or two -or that will become paid and break my existing workflows (or make me expend money unexpectedly)-.
Zapier is propietary and prohibitively expensive. Yes, I like it -- but I'd rather support small projects like this one, even if it requires a bit more of time.
In my experience, phones break more often than chargers, so you end up having several chargers laying around. Using the Pi for DIY projects, computing experiments (e.g. clusters) or learning, it makes sense to recycle those chargers (specially if you are in a budget). Being in a third world country I can assure you that getting a simple Pi-branded charger can get difficult and/or expensive.
I wonder, however, if smoothing skin makes for a lighter (compressed) image, resulting in bandwidth savings. We don't need to see skin details in a work conversation, just expressions.
Perhaps the feature should just be renamed/rebranded to something like "smartly reduce image details to save bandwidth"?
The browser itself continued working fine. Are you aware of any life-depending extension? Leaving this particular issue aside, your hypothetical "browser extension for people in the middle of the ocean" was doomed from its inception if it was designed to run as a browser extension (though it opens the door for an interesting discussion about similar scenarios that are happenning, like pilots relying on ipads)
OP didn't say it was a decision, just the message perceived. If you live outside the US, hearing stories or reading what happens to others is enough to know these things happen, anyway.
This reminds me a lot of Google Wave. While I have my concerns about a format brought by Google (who may be defining a bit too much of the web these days), adding richness to emails will be refreshing. As long as we keep the idea that a message is something that will not change and be accessible as long as we can access our inbox, I'm all in for improvements. I just hope it evolves into something beyond Google's control.
It's neat, but if a person is learning I think it's good to have that little extra verbosity. A new user may even get confused because its editor doesn't convert symbols.
At $20/mo there are alternatives (Zapier comes to mind) that may cover your needs as well. There's also Node-RED for those wanting something self-hosted (though it won't be as straight-forward).
The interesting thing about Pipes for me was that I could correct small things quite easy (and read my feeds later using Google Reader -oh, those were the times!-), and besides it being free it was maintained by a "familiar" site. At this point I'd rather invest my time in a tool I can control!
They are subnetwork masks! It's a formal way of expressing in which range you will find the addresses of a given network (for example: 3.0.0.0/8 is like saying "3.x.x.x addresses"; or, for common home networks you will find something like 192.168.1.0/24, which means "192.168.1.x"). I'm not an expert on the subject, but this site seems to have a complete explanation: http://www.steves-internet-guide.com/subnetting-subnet-masks...
I had a different experience: after some updates, around build 7 or 8 I lost cellular connectivity completely. It said there wasn't carrier data available and that I should update. To update, I needed to verify the download... which failed because it didn't have access to the modem/carrier data, even though wifi should have been enough. Long story short, I had to do a restore from iTunes (another nightmare for me -Linux user-), and after that discover that my backup "wasn't compatible" (fortunately I had made a manual backup of my photos and other content, but all the settings got lost). I've been using iOS for a year now and I definitely miss Android, even if it isn't as polished as iOS.