Maybe it's time to bring ftp search engines back.
And yes I know there's some niche support still, just as FTP will live on.
Is that really the case though? Wordpress ( Love it or Hate it ), both .com and self hosted is still thriving.
And if people are writing less blog, I think it has more to do with Social Media ( Facebook ) than RSS or Google Search / Reader.
The big problem at the time was there was no good options, even a year or so after and I gave up trying. Everything was 90% of the way or too fancy for such a simple service.
However I have been wanting to selfhost more so evaluating moving to either FreshRSS or TinyRSS,
Why using email? I switch between phones, OSs etc and it was a bitch to find decent clients for the self hosted options on each OS. I can generally get my email everywhere, via ActiveSync on my phone, WebUI, thunderbird etc. And since I host my mail, the data never leaves my network :) It works really well, though I do sometimes feel like RMS having web pages emailed to me lol
You mean no one knows that FTP is plaintext except a minority of users which happens to be on HN.
Google is optimizing its browser for the majority, chrome is not a power-user browser. Maybe they'll add an option to enable ftp or something.
> drivers, which I'd say are a significant part of FTP use
I'm not sure how that's true. Every time I used FTP, it was not for drivers. All the drivers I downloaded were over http(s), from constructor websites.
That is a problem. We have browser engine duopoly, and really everyone is doing whatever Google wants anyway. So as they're optimizing against power users, they're making the whole web much worse.
I tend to agree with you, but would you mind fleshing this out a bit. Or, if you've written this before please point to it.
Chrome is a duopoly, and Firefox tends to get forced in the same direction as Chrome over time -- it's not powerful enough to push the web as a whole in a different direction.
If Chrome was not a duopoly, this would not be a problem. There's nothing fundamentally wrong with having a browser that's highly optimized for nontechnical users. However, because Chrome has such control, pushing technical users out of Chrome has the effect of pushing technical users out of the web entirely. By putting itself into a dominant market position, Chrome has put itself in the (unenviable) position of needing to be everything for everyone.
In other words, if Chrome doesn't support power users, and if Firefox doesn't have the guts to refuse to make the changes they advocate for, then power users have no where to go. This is why monopolies and duopolies are bad even if the companies behind them are good. Its completely unrealistic for a single product to be everything for everyone, so single products by their very nature exclude certain users.
----
So who cares if power users abandon the web?
This is a problem because historically, power users have been incredibly important for the web's development. They've been important not just in the sense that they've pushed the web forward technically, but also because the web was designed to be a democratizing medium. The web is designed to be a publishing platform where people can build weird things without asking anyone's permission.
Even non-technical users benefit from this -- it's in their best interest to have lots of providers providing lots of solutions for publishing because (repeating what I said above) no one platform can be everything for everyone. A non-technical web that is optimized for ordinary people to the exclusion of power users is going to be less creative, less interesting, and less useful even for ordinary people.
Whether or not FTP in particular is critical to that -- I don't know. I don't know enough about FTP to make a strong argument on that. I will say I have used FTP a lot as a consumer, especially when downloading packages, and I have used FTP on internal networks. I'm not an expert, but the arguments package maintainers make about why SSL is unimportant to FTP ring true to me. My understanding is that package signing prevents modification attacks, and that looking at request sizes is enough to identify resources even with SSL.
As a policy, deprecating URL types that don't support encryption seems at first glance to be a really dumb move, and I'm not sure the security arguments justify it. But I'm not an expert.
----
I'm on Firefox, and I'm hopeful that Firefox is going to see a resurgence of usage pretty soon, particularly among power users. If Firefox refuses to deprecate FTP, I'm not so worried, since honestly I think it's probably in everyone's best interest for Chrome to do a few dumb things that make more power-users jump ship to Firefox. A lot of power users aren't willing to make the switch on ideological grounds; Chrome as a browser needs to get much, much worse to encourage them to use competitors.
Thankfully, it appears that (especially recently) the Chrome dev team has been thinking the same thing.
EDIT: 'danShumway and 'ajnin together essentially summarized my thinking here.
Web is built and maintained by technically proficient people so it needs them to be comfortable. There is no unified group of "power users"; everyone doing something regularly becomes a "power user" in that context to the extent they are able to. If you remove their ability to grow, you're condemning them to wasting their time and reducing utility of the web for them.
A real strange thing...
Not to worry though, I'm sure Google is just doing it for everyone's best interests, like the charitable organization for humanity that they are.
FTP is an awful protocol and there are other perfectly fungible open standard replacements for it, like HTTP/HTTPS. FTP dates from the era before NAT and firewalls and makes a bunch of problematic design choices, like having the server establish a separate port connection to the client (or vice versa, for passive mode) to transfer the file. It's super chatty, requiring multiple waits for response, and therefore slow. There's no length check, so if your socket gets closed you silently save a half-finished file.
FTP should just die off.
Yet they are positioning it as the only browser
One wouldn't expect Google to say "We recommend you use our browser, Google Chrome, but there's also these others that work fine to."
It's probably the case that back when the number of internet users was smaller the place had a more community oriented vibe, whereas now there is huge sums of money and power at stake.
Well, I think there is enough people like us, where a proper 'power-user' browser is worth maintaining. Any takers?
I guess not. More likely there'll be plugin to add this functionality back.
[0]: https://chrome.google.com/webstore/detail/iodihamcpbpeioajje...
https://blog.chromium.org/2017/05/goodbye-pnacl-hello-webass...
The point of "organize the world's information and make it universally accessible and useful" is to do precisely that: to organize the world's information and make it universally accessible and useful -- long tails included. But I guess for them it's not...
(Also, I can't believe the Chrome team is so strapped it can't afford to support or harden the feature, as some in the bug tracker suggest [1]. This is Google we are talking about, not some tiny open source project!)
[1] https://bugs.chromium.org/p/chromium/issues/detail?id=333943
How do you display ads while someone is accessing an FTP server?
ftp://example.com/directory/file.extension can be a link in a website, where the website displays ads.
I'm just imagining some people having a conversation that goes something like this:
"The funding for this feature has been removed because we can't serve ads on a page like this https://imgur.com/20ooI9f "
Edit: grammar
I believe those will happen, in the long run.
The next HTTP spec includes mandatory SSL, and Google had a hand in designing QUIC, and Google has been deprecating traditional SMTP authorisation.
FTP in the browser typically looks something like this https://imgur.com/20ooI9f
Plenty of space for ads.
HTTP is basically FTP with ads.
Funny thought. Imagine if, to this day, the internet consisted of pretty much that.
You go to ftp://nytimes.com and it just has a directory structure that consists of yyyy/mm/dd and the file names where things like statement-from-chinese-ambassador-to-australia.txt
And maybe a directory named breaking-news
Imagine if Twitter was a list of text files named yyyy-mm-dd-hh-mm-ss-username.txt
Ha.
Imagine if you had to upload a text file like this
---
Please place an x between the brackets as desired
[ ] Whopper Meal
[ ] Super sized Whopper Meal
[ ] Coke
[ ] Sprite
[ ] Eat-in
[ ] Takeaway
etc
Name on card:
Card number:
Expiry:
Card Security Code:
Sponsored by Nike and the Ford Motor Company
----
Edit: changes 'threat' to 'thread' in first line, typo could have been confusing. Second edit: made list verbatim.That's pretty much Gopher. Another protocol that Chrome no longer supports.
On Usenet newsgroups and BBS conferences, sellers would post forms that looked exactly like that, except for the ads of course. Buyers would then send in their completed order form via either email/netmail or, preferably, via fax for added security.
I remember always choosing to fax in my orders; even way back then, sharing credit card details via email seemed like a very bad idea.
I would love this. This has better UX than the food ordering sites we have to deal with in the real world.
Nobody would actually bother to download it would they!
Sounds like a total improvement over websites I have suffered... not to mention allows all kinds of third parties to create their own fancier ordering systems on top!
But my gut reaction to reading this concern is actually: why do you think this is “bullying” and not “opening the door for a niche competitor”?
Also, this enables linear scale out, since not all ftp data nodes (not sure what the correct term was) need to store all of the data that’s being served, and you can store multiple copies of each file.
Come to think of it, I’m not sure why HDFS exists, given that you can just use a ftp server cluster for the same effect.
https://en.wikipedia.org/wiki/Heartbleed
(I mean, I'm not overjoyed at the deprecation of FTP support because I used it just yesterday, but let's at least be honest here. The protocol might be decades old but the implementations aren't necessarily, and if they're being actively maintained there's always the possibility of introducing new bugs.)
That's not the "stable protocol that's been around for decades" situation that FTP is in.
That is literally the point I was making when I said, "if they're being actively maintained there's always the possibility of introducing new bugs."
Moreover, just because a library had its last fix a decade (or whatever) ago is no guarantee that unfixed bugs do not lie undiscovered in it.
Many protocols evolve not by being replaced by incrementally better point releases, but rather by being supplanted entirely by a better designed alternative.
FTP effectively evolved into HTTP for this use case, and scp/sftp for the authenticated file transfer use case.
and there are other bugs in the implementation which further demotivates the FTP support.
To me that reads as there are bugs in Chrome's implementation of FTP.
Did you take that to mean the author intended to convey the message that the FTP protocol has bugs?
Bully them back. Don't use Google search and don't use Chrome.
But if you really think it would be right to switch away from Google, give yourself a month of pain and then decide if you can live this new life. ;-)
I personally hope they continue exhibiting monopolistic behaviour. Same with Cloudflare and other company's who choose business models that are hostile to an open and decentralized Internet.
It's real easy to do. It is not the case that you are dependent on Google search. You're imposing artificial limits on yourself. Break free of this limiting mindset.
These kind of comments are so strange... why do you want Google to own your FTP client instead of having an independent one?
Give it a few years and they will deprecate Android for security reasons.
For example one of the things I would do as an evil product manager at Google is introduce active detection of Firefox - even if the user agent string has been set to Chrome to get me to serve unbroken pages. I would have engineers actively fingerprint Firefox, and if I figure out the user is using Firefox, serve them broken pages. (Even if it works perfectly well in Firefox if they pass my detection, and even if they identify as Chrome.)
Would this attitude be a good fit for a product manager for Google? I'm really evil.
Also, I can't be the only one who's absolutely sick of hearing that bloody "security" argument again. Yes, everyone knows FTP is plaintext, and so is HTTP. But drivers, which I'd say are a significant part of FTP use, are almost always themselves signed anyway, and I don't think malware is widely distributed via FTP either (I'm curious why FTPS/SFTP doesn't see to be indexed, or why they didn't decide to add that to the browser instead --- or at least I've never come across a search result that links to one.)