Here is an idea, don't abuse your users and you don't even have to show a cookie banner. Of course people treat it like spam - because that is exactly what it is. A giant fuck you to every single user.
I felt that way too, but having used it a few devices as an end user I enjoy being able to close the browser and have the whole stack disappear. Instead of having to install a creepy Logitech tool to pair a mouse with a receiver, as soon as that task is done, goodbye Logitech. I guess a real concern is manufacturers stop offering native drivers, but for the majority of hardware the PnP or the Linux kernel just handle it.
There's a real risk of losing the ability to control your device if the manufacturer stops hosting their propertiary WebUSB app, too.
Standard USB drivers aren't going to disappear from my disk and can be reverse engineered long after its manufacturer has dropped support or gone under.
The question is if users will consistently have the foresight to archive such web apps, especially if the manufacturer has set up their bots.txt such that The Internet Archive skips it.
Traditional programs are incedentally archived by nature of having to be downloaded. They sit in downloads folders, old backups, thumb drives, etc.
Not a single popup, didn't find any ads more than a text-only banner on top asking to subscribe. Some whitespace where ads might go though. No adblock.
I'm in EU though, maybe they actually respect GDPR. Or maybe it is just a glitch.
> Really the EU needs to apologize for those damned cookie popups and invest in a privacy-first browser.
I love them. They are not mandatory, only shady websites that rather sell users information than providing a barely functional homepage. Yes the popups suck, but I'm very happy that this exposes the behavior and priorities of the industry.
It is insane to see very ordinary web sites that have 100 trackers but part of that is that the advertising economy gives everyone the incentive to screw each other with the backdrop that of course the metrics do not match across the funnel because people fall out as you go down the funnel —- but if you have 100 trackers they can’t all be lying in a coordinated way.
Running background processes might motivate the use of NPU more but don't exactly feel like a pressing need. Actively listen to you 24/7 and analyze the data isn't a usecase I'm eager to explore given the lack of control we have of our own devices.
Working as intended? They openly state that how quickly your limit is reached depends on many factors (that you don't know) as well as current load on their systems.
I mean, it is arguably much easier to just write the HTML page and upload it with FTP and everyone can see it. I never understood why github became a popular place to host your site in the first place.
> I never understood why github became a popular place to host your site in the first place.
Easy: it was free, it was accessible to people that couldn't spend money for a hosting provider (read: high schoolers) and didn't impose arbitrary restrictions on what you were hosting.
Back then, your options as a high school student were basically to either try and reskin a closed off platform as much as you could (Tumblr could do that, but GitHub Pages also released in the time period where platforms were cracking down on all user customization larger than "what is my avatar") or to accept that the site you wanted to publish your stuff on could disappear at any moment the sketchy hosting provider that provided you a small amount of storage determined your bandwidth costs meant upselling you on the premium plan.
GitHub didn't impose those restrictions in exchange for being a bit less interactive when it came to publishing things (so no such thing as a comment section without using Disqus or something like that, and chances are you didn't need the comments anyways so win-win) That's why it got a lot more popular than just using an FTP server.
There are multiple reasons why FTP by itself became obsolete. Some of them I can think of off the top of my head:
1) Passive mode. What is it and why do I need it? Well, you see, back in the old days, .... It took way too long for this critical "option" to become well supported and used by default.
2) Text mode. No, I don't want you to corrupt some of my files based on half-baked heuristics about what is and isn't a text file, and it doesn't make any sense to rewrite line endings anymore anyway.
3) Transport security. FTPS should have become the standard decades ago, but it still isn't to this day. If you want to actually transfer files using an FTP-like interface today, you use SFTP, which is a totally different protocol built on SSH.
chrome and firefox dropped support for it 5 years or so ago, it has had a lot of security issues over the years, was annoying over NAT, and there are better options for secure bulk transfers (sftp, rsync, etc)
Depending on your hardware (SBC), FTP can also be several times faster than SFTP for transferring files over a LAN. Though I'll admit to having used other protocols like torrents for large files that had bad transfers or other issues (low-quality connection issues causing dropped connections, etc).
Finding an HTTP+FTP server was easier than finding github. Your OS probably has a FTP client installed already, but finding another one is easier than finding and most definitely easier than learning git.
And if you already knew how to write/make HTML you'd for sure already know all of that too.
This is definitely a matter of perspective. I have had a Github account since 2010, and git comes installed on Linux and macOS.
I don't always have a server available to host an HTTP+FTP server on. Or want to pay for one, or spend time setting one up. I can trust that Github Pages will have reasonable uptime, and I won't have to monitor it at all.
> And if you already knew how to write/make HTML you'd for sure already know all of that too.
This seems unnecessarily aggressive, and I don't really understand where it's coming from.
BTW, you can absolutely host plain HTML with Github Pages. No SSG required.
> And if you already knew how to write/make HTML you'd for sure already know all of that too.
That's a completely false statement. My kid took very basic programming classes in school which covered HTML so they could build webpages, which is a fantastic instant-results method. Hooray, now the class is finished, he wants to put it on the web. Just like millions of other kids who couldn't even spell FTP.
I touched on the issues with FTP itself in another comment, but who can forget the issues with HTTP+FTP, like: modes (644 or 755? wait, what is a umask?), .htaccess, MIME mappings, "why isn't index.html working?", etc. Every place had a different httpd config and a different person you had to email to (hopefully) get it fixed.
There was a lot of sites that provided some cpanel-like option as long as you're ok with yourcoolname.weirdhostingname.com. I believe they all came with a filebrowser and the always present public_html folder.
There was geocities (now gone) and a couple of *.tk domains that would inject their ads all over your page. Neither makes a great substitute for GitHub pages these days.
I just checked, I’m not using the feature but my current ISP still offers it: https://assistance.free.fr/articles/631 (10 GB FTP storage tied to the ISP-specific e-mail address).
Having looked it up, mine makes it an add-on service for 1,045円/month + 5,500円 set-up fee, at which point you might as well use a dedicated VPS service (which is probably what's actually going on behind the scenes anyway).
With the range as good as a modern EV the charge time already isn't a particularly that bad. I'd much prefer more chargers (so that you can combine charging with something else you were going to do anyway) than faster ones.
I tend to agree but I think the strategy here is to convert people who stubbornly cling to gas vehicles because EVs somehow defy their expectations. I have been approached many times at highway rest stops by people who are curious and slightly skeptical about the EV value proposition. They see me hanging around the vehicle for a half hour and think “ugh, no thanks” as if that’s all I do when I travel. What they’re not seeing is that I rarely use public chargers at all, because 99% of my charging is done either at home or at the charger in the parking lot at work. It’s really just road trips. Not to mention, if you’re an ICE owner hanging around long enough at a rest stops to notice that I’m hanging around, are you really that much faster on a road trip?!!
Back on topic, I am ok with losing a little efficiency in the fast charging process if it means that more people switch away from a horribly inefficient and polluting technology.
> Because we cannot name something leading with a trademark owned by someone else.
https://xcancel.com/richturn_ms/status/1245481405947076610?s...
reply