$5/month and an afternoon to set up unlimited email accounts on unlimited domains on one server. There are a few scripts/services out there that limit the pain.
This makes sense. Possibly the value of increased corporate sales of G Suite is worth more than the loss of the information gained from reading diminishing numbers of personal emails, as people turn more and more to social media and phone apps for personal communication.
HEADLINE: Consolidation of Documentation; Removal of Outdated Documentation
DESCRIPTION: Any time you do a web search for anything regarding Debian, the search results include a huge amount of official but outdated information. Normally for Linux-related questions I refer to the amazing Arch wiki, but there are topics that are Debian-specific, and then sifting through all the detritus is a huge waste of time. There's a wiki, a kernel handbook, a manual, random xyz.debian.org pages, mailing lists, user forums, the Debian Administrator's Handbook...
Granted, it's a huge effort to clean all of that up, but perhaps there's a way to incorporate user feedback, so that pages can be marked as "outdated" by users, or updated by users (wait, there's a log-in page- does this mean I can edit wiki pages? Did not know that...:( ), or otherwise made more systematic.
In particular, it would be great to have more complete information on the installation process: which images to use (RC, ..., or weekly image?), how to put them on a USB stick (why does my 32GB stick now say it has 128GB?; you mean I can just copy the files to a FAT32-formatted drive?), what the options are (for hostname, is any name, a FQDN necessary?), etc. For every single clarification, there will be a hundred, thousand, ten thousand people who are helped; that seems like a worthwhile investment. Everyone is a beginner at the beginning, regardless of knowledge outside this specific domain, so why not make it easier.
All that said, have been using Stretch/testing for a few years, love it, love the Free/Libre Software ethos, love what you guys do, keep it up, thank you!
One often has to rely on stackoverflow (and the likes) to get info because the doc/wiki is outdated.
That being said, the info provided on theses websites aren't necessarily correct.
There is for instance no clear, up-to-date, doc on how to install some packages from testing and keep them updated (pinning ? no pinning ? what values ? what sources ?)
Hear, hear. The site is generally an excellent resource but I've also come across reams of outdated guides which steered me wrong, and worse, have sometimes left my system in an indefinite state because I only realized halfway through that this guide is no longer relevant. Cleaning this stuff up should be a priority.
This! As I see it a major problem not only with Debian but Linux over all is the amount of outdated documentation. At least some people will when they don't find what they're looking for on the Debian wiki google for it and might end up with at best solutions that are old and outdated, or at worst solutions that are all wrong these days and might leave their system wide open.
I like the idea of genius as derived from genus, and meaning something like a particular kind of excellence, an exemplar of its kind, something's characteristic disposition. One can think of there being not one class of geniuses, but think of it as excellence of a particular kind, in a particular activity, that is related to the intrinsic and highly developed talents or disposition of the genius. So, Rafael Nadal is a clay court genius, because he is a great tennis player, and in addition he puts maximum effort into the kind of tennis that requires it, and his physical, top-spin heavy tennis is ideally suited to the surface.
Please, web developers, as a minimum, set up your websites so that they do not depend on Google, Facebook, Microsoft, Amazon or Apple for their functionality. That means, for example, use DoubleClick or AdSense or GoogleAnalytics if you like, but please do not use jquery from Google's CDNs. If you do that, and the site is dependent on that functionality to work (i.e. for text to be displayed), those of us who don't allow Google CDNs will not be able to use the site.
The same for WebAssembly: use it if you like, but please don't make your actual content unnecessarily dependent on the use of services from these multinationals. It makes the Web less free.
Thing is, if you're a news site, your news isn't going to show up on Google's news platforms if it doesn't support AMP.
As a customer, I don't like this behavior at all. I do not like AMP, mostly for the small issue that it's very difficult to link to the base page. Minor consistent inconvenience, major feature rage.
But I can't imagine what it's like for a web developer. You need to support a whole other platform just to maintain your audience, which is also your lifeblood. Also, that audience won't actually see your page; just the text with some Googly UI. Avoiding it would be fantastic, but it also wouldn't be a realistic option.
One of the comments in Alex Kras's linked page asks "Can’t you make a direct link to your site’s page auto generated on your article templates?" [0] which seems a very reasonable, though perhaps not ideal, solution that doesn't require Google to make AMP optional, something I think Google is very unlikely to do.
It's really strange to me that Google just decided to remove the option to not use AMP. I personally hate that part of it the most. It's like someone made the decision to not even fight the take-rate battle. "AB test it? Hah! They'll use it if they want to get to the result!". It seems to be getting them tons of ill will which they could easily fix by just putting a non-amp link on results. Then again, "tons" on HN equates to basically nothing across their whole user base, so I doubt they really care too much, but damn, what an awful idea/decision to take away the choice.
It depends on what you do with that blob; if you use it to request some required encrypted content, for example, users won't be able to do much about that.
My point is that anyone can use an adblocker or Squid proxy filtering to block GoogleAnalytics, but if the site uses jquery from a Google CDN to render content, that cannot be blocked without making the site unusable. It's even worse if the Google CDN request is made with https, because then a redirection needs to be made inside the browser.
Can't you whitelist the specific jQuery library on Google's CDN though?
Serving widely used libraries out of a CDN is a best practice for a reason. Most visitors will already have it in cache. What alternative are you supposing? Local hosting? That has drawbacks, including more cache misses and increased bandwidth costs for the website provider.
It's not always the user doing the blocking. A lot of sites broke for me when I was in China because they were trying to fetch resources from Google's CDN, which is/was blocked there.
Surely the primary blame there lies in China's censorship of the Internet, no? Isn't it just assumed that if you're traveling to China you need to be using a VPN in order to have the web as you're used to it work normally?
No doubt Google considers it a best practice, because they are in the business of knowing what people do on the internet. How often will a browser get the jquery for a particular website or check with the CDN? There are a lot of jquery versions in use, the cache gets deleted (often on browser close) or expires, cache-age=0, etc. Almost always?
Besides providing jquery themselves, websites can use a CDN from another provider. OK, that might cost an extra 20 ms.
Right, but then Google can leverage their CDN to track you, whether or not you also let them show you ads through normal channels. Ideally people would use a CDN not built to track people around.
Presumably once Google traps you into an unblockable ad channel (on mobile or whatever) they will unleash the tracking they've been doing on you.
It's really not as beneficial as it sounds in theory. Sites uses different versions of these libraries.
You would be better serving a single minified asset that is cached for your users.
Is not it better to serve scripts from your server? It gives you more control and you don't have to share your visitors data with Google. With external hosting you get more downtime, and in some countries Google servers are blocked so you get less visitors.
>The same for WebAssembly: use it if you like, but please don't make your actual content unnecessarily dependent on the use of services from these multinationals.
With this being said, it may actually be easier to figure out wasm than frameworkified JS since you can apply IDA-style reversing to it.
Open question: what existing tools and research are good at inferring the high-level behavior of stack machines? Eg, research papers, or (preferably open source) tools for reversing eg Java code. I want links I can throw at Ph.Ds.
In addition, the blog post uses Google Fonts and jquery from a Google CDN. Could people please consider using a non-Google CDN for things that affect webpage functionality? Those of us that block HTTP requests to Google servers will then also be able to use the website. (In this case the webpage content appears entirely usable even with jquery etc. blocked.)
I read the Share Lab metadata report, based on an examination of the metadata in the headers of the emails exchanged between Hacking Team members. The level of detail this provides on the network and on the individual members of the team is extraordinary. Now in the case of Facebook, imagine that times 100, then add AI to slice and dice the data better than a team of the world's top 1000 data scientists working on the analysis of some tiny portion of the data for some particular purpose, for a year... Just one consequence: think of what Facebook and Google have on every politician in the United States, in the world.
