When Snap was introduced Canonical promised it would never replace APT. This promise was broken. Some APT packages in the Ubuntu repositories not only install snap as a dependency but also run snap commands as root without your knowledge or consent and connect your computer to the remote proprietary store operated by Canonical.

This is a store we can’t audit, which contains software nobody can patch. If we can’t fix or modify software, open-source or not, it provides the same limitations as proprietary software.

Although it is open-source, Snap on the other hand, only works with the Ubuntu Store. Nobody knows how to make a Snap Store and nobody can. The Snap client is designed to work with only one source, following a protocol which isn’t open, and using only one authentication system. Snapd is nothing on its own, it can only work with the Ubuntu Store.

Science’s culture of critique discourages groupthink, countermands the effects of human biases, and protects knowledge, not only by rewarding a dispassionate stance toward the subject and institutionalizing organized skepticism but also by fostering competition among scientists able to replicate and hence challenge each other’s work.

We took a stance on an issue. We informed and documented. We made it easy for you to understand the problem and also to take action if you disagreed.

We took a stance on an issue.

We informed and documented. We made it easy for you to understand the problem and also to take action if you disagreed. I hope you didn’t read https://linuxmint-user-guide.readthedocs.io/en/latest/snap.html#how-to-install-the-snap-store-in-linux-mint-20. I can’t understand how it could be simpler.

Is it harder to enable it in Mint than it is to disable it in Ubuntu? Not at all. Is how to enable it better documented in Mint than how to disable it in Ubuntu? Absolutely: https://linuxmint-user-guide.readthedocs.io/en/latest/snap.html.

Yahoo is _much_ worse than Google when it comes to collecting data and using it.

http://letmegooglethat.com/?q=How+to+change+the+default+search+engine+in+chromium&l=1

We can certainly explain the issues snap cause without using political or religious arguments. We did so in the documentation I linked to above.

We don’t do politics, and we certainly don’t do religion. You’re bringing these here by using terms such as “politicians” or “evil”.

game (fun and enjoyable)

strategy (decisions affect the outcome, not chance)

I can provide full 24h logs and a copy of /var/lib/docker/network/files/local-kv.db if you give me a private channel.

Some users download the DEB package and install it manually and manage upgrades completely manually. This is useful in situations such as installing Docker on air-gapped systems with no access to the internet.

The scripts require root or sudo privileges to run. Therefore, you should carefully examine and audit the scripts before running them.

that's by design:

For the future, you should: Install LTS (Long-term support) versions as they have an 8-year life span (with Extended Security Maintenance) or 5 years without. The current LTS version is Ubuntu 18.04.1 LTS Bionic Beaver released on July 26, 2018 with an EOL in April 2023. OR Carefully watch the EOL of the interim / development releases and upgrade frequently.

Please don't thank me! ;-) If this answer did help, just click the little grey ☑ at the left of this text right now turning it into beautiful green. If you do not like the answer, click on the little grey down-arrow below the number, and if you really like the answer, click on the little grey ☑ and the little up-arrow... If you have any further questions, just ask another one! ;-)

As you installed a development release (17.04) that had only a 9-month life span and had an End of Life (EOL) in Jan 2018, there is no way to upgrade it to 17.10 as that went EOL back in July 2018. So as you're stuck with a release without an upgrade path (as you cannot skip versions)

Ubuntu 17.10 reached End Of LIFE 19th July 2018 .. you should have upgraded to 18.04 long ago.

OTOH, I'm old enough to have made the exact same error myself, i.e. trying to optimize something which really didn't need it and making the code more complicated as a result, so I am not blaming whoever had the idea for the rewrite.

Why was the change even made, if statistical performance is not improved and the code is just harder to understand? Conspiracy theorists could get the idea of a backdoor (:

The code is far simpler and easier to understand/verify

Snaps each pick a ‘base’, for example, Ubuntu18 (corresponding to the set of minimal debs in Ubuntu 18.04 LTS). Nevertheless, the choice of base does not impact on your ability to use a snap on any of the supported Linux distributions or versions — it’s a choice of the publisher and should be invisible to you as a user or developer.

The heart of Ubuntu is a collection of ‘deb’ packages which are tested and integrated so that they work well as a set. Debs are optimised for highly structured dependency management, enabling you to combine debs very richly while ensuring that the necessary software dependencies for each deb (themselves delivered as debs) are installed on your machine.

Ubuntu also supports ‘snap’ packages which are more suited for third-party applications and tools which evolve at their own speed, independently of Ubuntu. If you want to install a high-profile app like Skype or a toolchain like the latest version of Golang, you probably want the snap because it will give you fresher versions and more control of the specific major versions you want to track.

The plot is so thin that, if it is ever discovered, will revolutionalize the world of particle physics.

This gem is now entering passive maintenance mode; I will not be actively maintaining it anymore.

I cannot guarantee that happening at all, so no timeline sadly.

I could find the time to maintain it despite being "boring"

At work, I cannot maintain this project. At home, I'd rather spend time with my children and on projects that I'm currently passionate about.

Maintaining open source software requires energy and a "want"/"passion". I've not been using this project myself for years, and I mainly work in other things than Rails at this point. That means I'm far removed from this project and see no personal gain in maintaining the energy to keep this going.

I'm still pretty proud of the project and I don't want to see it gone, so I want to keep updating it when needed. But on the other hand, the feature set is pretty stable and well working now (AFAIK) so I also don't see the need to pretend to be actively maintaining it.

Please: Prompt me when things break and I will probably fix it. I won't guarantee how fast I'll move, but I'll try to make the effort sometimes. The bigger the issue, the more likely it is that I'll do something about it.

Contributions are welcome, like always. I love contributions and seeing other people getting value from this project. Keep doing it!

It's not impossible, but it's not likely I would accept someone I haven't worked with IRL or know on a personal level. That's because I want some form of creative control over the direction and I want to maintain the existing code style. If I know you I'm more likely to know that this will keep working the way I want it to.

a triager would be very welcome; someone that can ask follow-up questions on issues, create test cases for the problems, and so on.

Show me good PRs, bug triaging, documentation fixes, whatever and you're a candidate if you ask for it.

reviewing code takes energy!

This is open-source. You can always fork and maintain that fork yourself if you feel that's warranted. That's how this project started in the first place, so I know the feeling.

premailer-rails processes all outgoing emails by default. If you wish to skip premailer for a certain email, simply set the :skip_premailer header:

premailer-rails and premailer require a gem that is used to parse the email's HTML. For a list of supported gems and how to select which one to use, please refer to the Adapter section of premailer. Note that there is no hard dependency from either gem so you should add one yourself.

config.action_mailer.register_preview_interceptor :css_inline_styler

This allows you to execute multiple scripts in parallel.

GIL free JavaScript execution The Ruby Global interpreter lock is released when scripts are executing

Apple, however, insisted reaching said agreement in the US was not an admission of wrongdoing.

Use inline styles for everything.

Email marketing made better

Slogans can therefore be longer than taglines

Taglines are more often next to the company's logo on official advertisements, and are dedicated more specifically to brand awareness than slogans. Slogans carry a brand's values and promises as the company grows and evolves, and can be promoted under an overarching company tagline.

Although both "slogan" and "tagline" tend to be used interchangeably, they actually serve two different purposes. 

Companies have slogans for the same reason they have logos: advertising. While logos are visual representations of a brand, slogans are audible representations of a brand. Both formats grab consumers' attention more readily than the name a company or product might. Plus, they're simpler to understand and remember.

In many ways, they're like mini-mission statements.

a slogan is "a catchphrase or small group of words that are combined in a special way to identify a product or company,"

See screenshots of your emails across 90+ apps

Previewing You can create a controller that gets the email and then renders the body from it.

Nerd Fonts is a project that patches developer targeted fonts with a high number of glyphs (icons). Specifically to add a high number of extra glyphs from popular 'iconic fonts' such as Font Awesome ➶, Devicons ➶, Octicons ➶, and others.

popular 'iconic fonts'

The following Sankey flow diagram shows the current glyph sets included:

SankeyMATIC unlocks the capabilities of the D3 Sankey tool for anyone to use.

SankeyMATIC builds on the open source tool D3.js and its Sankey library, which are very powerful but require a fair amount of work & expertise to use.

Pango is one of the most common font rendering libraries on Linux. It's used by GTK/GNOME and a lot of standalone apps, like Rofi, Polybar, and a lot of terminals.

cp src/glyphs/Symbols-2048-em\ Nerd\ Font\ Complete.ttf ~/.local/share/fonts fc-cache -fv pango-view -t "Playing some  for you right now"

How should this be manually tested?

Trust me, I'm not trying to stress you right now, but I just wanted to do a friendly bump in case you forgot about this. (I know how it is sometimes) If you get this notification and feel "Ugh, I really don't have time" you don't have to comment here and I'm sorry. I'm just sending you a notification in case you forgot. If not, feel free to archive the email and not click/tap on anything.

Premailer is written in Ruby

What’s the difference between an ad and your recommendation?

Bordering an element with a single repeating image is something that seems like it should be easy with a property called border-image, but the process for actually doing that is somewhat counter-intuitive. Let’s say, for example, that you want to border an element with a repeating heart icon. You can’t do that with a image of a single heart. Instead, you have to make an image of a “frame” of hearts arranged as you’d like them to appear in the border, then slice that image. <img sizes="(min-width: 735px) 864px, 96vw" src='https://i2.wp.com/css-tricks.com/wp-content/uploads/2013/01/enlarged-border-image-slice.png' alt='' data-recalc-dims="1" />Eight hearts in a “frame” image, enlarged to show detail. The red lines indicate slices. If you think that sounds preposterous, you’re in good company. There was a lengthy discussion of the subject on Eric Myer’s blog a few years ago where many frontend development greats weighed in.

Try out the different border-image-repeat values in this demo

This question is locked and replying has been disabled.

Just as the user above said, Gmail is removing all css styles throughout the body, and removing all css styles in the head tag. Their own documentation says this should work but it's not working at all. I've wasted 6 hours trying to make this work.

The Gmail Android app that comes pre-installed with most new Android phones contains a feature to access non-Google accounts using POP and IMAP. Unfortunately, emails accessed through this setup lack the embedded style (<style>) support as well as the support for background images.

Email’s actually not guaranteed to be quick. Even though it usually is pretty darned speedy, the entire email system is built to tolerate delays of several days. There are various reasons that this might happen, including a few very legitimate spam-fighting techniques. The solution? Wait a while. If in a few hours or the next day you still haven’t received the confirmation email, the problem may be elsewhere.

Now that we triage by severity, setting this bug's priority to P2 to represent near-term backlog status.

The background-origin CSS property sets the background's origin: from the border start, inside the border, or inside the padding.

border-image-slice

This is responsive, but you can use media queries to specify different sizes and margins for mobile if necessary.

You could use an asymmetrical border to make curves with CSS. border-radius: 50%/100px 100px 0 0;

Because .subtitle has a width of 100%, the min-width: auto calculation that flexbox makes says that its container should be larger than we want.

Situation: you have a single line of text in a flex child element. You don’t want that text to wrap, you want it truncated with ellipsis (or fall back to just hiding the overflow). But the worst happens. The unthinkable! The layout breaks and forces the entire flex parent element too wide. Flexbox is supposed to be helping make layout easier!

The solution is min-width: 0; on the flex child Or min-width some actual value. Without this, the flex child containing the other text elements won’t narrow past the “implied width” of those text elements.

We are not allowed to show you historical data for Amazon

Augmented Steam is an open source project. You can verify the code for yourself, help us improve it or create your very own version.

I used it to create a full-bleed utility class: .full-bleed { width: 100vw; margin-left: calc(50% - 50vw); }

Use-case party I asked some CSS developers when they last used calc() so we could have a nice taste here for for how others use it in their day-to-day work.

Great, I can use vw to scale text so it doesn't look puny on a desktop! Perfect... Oh. Huh, now the text is too small to read when viewed on a phone. Okay, well I can just use "max(x,y)" to make sure it doesn't get shrunk beyond a minimum size. Perfect... Oh. Hmm. Looks like "max" isn't supported properly by Chrome. Okay, well guess I'll just use "px" again.

Content is like water

Change any of the <option> by double clicking on the number.

I want to create a filter for all email sent by me only to me. To accomplish this I send all these "notes" to a permutation that I know no one else uses. E.g. john__doe@gmail.com

auto As a maximum, identical to max-content. As a minimum it represents the largest minimum size (as specified by min-width/min-height) of the grid items occupying the grid track.

CSS Grid Layout excels at dividing a page into major regions or defining the relationship in terms of size, position, and layer, between parts of a control built from HTML primitives.

This is really cool! Having the content decide on the space it needs is so powerful!

overflow-wrap: break-word; makes sure the long string will wrap and not bust out of the container. You might as well use word-wrap as well because as the spec says, they are literally just alternate names for each other. Some browsers support one and not the other.

How to wrap long word (text without spaces) in html table’s cell? This is very, very easy! We must add only a CSS proprty to table cell “td” tag – “word-break: break-all;” then all column’s widths become as intended. 

fixed: With this value, the table’s layout ignores the content and instead uses the table’s width, any specified width of columns, and border and cell spacing values. The column values used are based on widths defined on columns or cells for the first row of the table

It is also very likely that the contents of the table might change the structure or dimensions of the table. For example, long words residing in the table cells can cause the cell width to increases. If you fix that problem, it might happen that the long words cross the cell boundaries.

Tables in HTML are absurd elements.

I think it’s a bit more robust to do this at the grid definition level.

min-width: 0;

The explanation here is that the minimum size of an fr unit is auto. Grid then looks at the min-content size of the item. If the item has a size (you’ve given it a width) or has something in it with a size such as an image, the min-content size might be much bigger than the share of available space you think 1fr will give you. It’s easy to think of 1fr as being “one part of the space in the grid container” when it is really one part of the space left over. If there is space to grow then the tracks grow from that min-content size assigning space. Using minmax, as you have pointed out, is the best thing to do if you want to forcibly have equal width tracks, as that says “I want this track to have a min-content size of 0”, you could potentially in that situation end up with overflows as you lose the squishiness.

It’s easy to think of 1fr as being “one part of the space in the grid container” when it is really one part of the space left over.

And since auto is entirely based on content, we can say it is “indefinitely” sized, its dimensions flex. If we were to put an explicit width on the column, like 50% or 400px, then we would say it is “definitely” sized.

I can’t promise I’m explaining this 100% accurately, but the way I understand it, the minimum width of a grid column is auto.

It’s true that the auto value would do the same, but auto isn’t quite as robust since it’s size is based on the content inside.

The only difference is that in this case “auto” will not work, but instead “height: 100%” is required.

use of the border-box property. If you add the following at the top of your CSS file, you should be able to avoid many of the problems inherent in using 100% width on your elements:

Blocks Don’t Need 100% Width When we understand the difference between block-level elements and inline elements, we’ll know that a block element (such as a <div>, <p>, or <ul>, to name a few) will, by default expand to fit the width of its containing, or parent, element (minus any margins it has or padding its parent has).

But in most cases, I strongly recommend you use padding inside a box, rather than margins, to ensure you don’t have this problem.

It seems like this should be one of the easiest things to understand in CSS. If you want a block-level element to fill any remaining space inside of its parent, then it’s simple — just add width: 100% in your CSS declaration for that element, and your problem is solved. Not so fast. It’s not quite that easy. I’m sure CSS developers of all skill levels have attempted something similar to what I’ve just described, with bizarre results ultimately leading to head scratching and shruggingly resorting to experimenting with absolute widths until we find just the right fit. This is just one of those things in CSS that seems easy to understand (and really, it should be), but it’s sometimes not — because of the way that percentages work in CSS.

Making literal grids. Like X columns with Y gap between them homegrown framework stuff. grid-gap is wonderful, as gutters are the main pain point of grid systems.

Join Our Community

sudo apt purge chromium-browser chromium-chromedriver Bye bye, fake Chromium packages.

Create an /etc/apt/preferences.d/debian-chromium

Debian still maintains Chromium as a regular package in their APT repository. We can configure Ubuntu to get it from there, and continue to receive timely security updates along with all of our other OS updates. This makes sense from a security perspective, since Debian is where Ubuntu already gets most of its packages, and is a very well known high-profile project. There is no need to risk installing software from some random source or telling your system to trust a PPA.

I'm very (VERY!) tempted to use that ppa, but without offense to it's maintainers... it's just some random ppa. If it had more "traction" I'd use it. Right now it has only 3 maintainers.

You can use Chromium from the Debian buster repository.

the bloody mount points. I couldn't believe that when I realised what was going on. I got the wire brush and dettol out and scraped it off my drive. Never, ever again.

It won't work if $HOME is not under /home. Really. Not even if you softlink. You need a bind mount

There's a lot of advice online showing how to get rid of snap. (e.g.: https://cialu.net/how-to-disable-and-remove-completely-snaps-in-ubuntu-linux/ worked for me) so the only result (so far, a few months later) is that Chromium has lost a user, and having upgraded Ubuntu since the original Warty, if snap becomes obligatory I'll have to take a look at Mint, or Devuan.

I did the same thing. Another big advantage with Pop! is that it comes ready to deal with modern graphics cards. I coulg get my card working on Ubuntu sometimes, but it had to be done just so, and the phase of the moon needed to be right, or else you had to start the whole process over again. Canonical is free to do whatever they want I guess, but their recent shifts in priorities are a little weird to me.

It is pretty much what Ubuntu 20.04 could have been, but isn't.

I managed to remove it myself this morning...apparently it used to get it's hooks in so deep it was very difficult to remove the daemon as it interconnected with ubuntu-desktop for....reasons.

Good. Hate snap. It's insidious and a pain to deal with.

Plus, have you seen how many loopback mounting points it creates? "df" becomes very hard to use as it buries your actual drives with it's own. One for the daemon, one for GTK, one for Gnome, one for each of the snaps you have installed....

it's an absolute resource hog

Besides running contrary to the principles that lead a lot of people to Linux systems (a closed store that you can't alter...automatic updates you have no control over....run by just the one company)

The strangest "quirk" I had was that I couldn't get the web browser to save a file directly to an attached, encrypted drive. Permissions problem. So I had to save to an interim folder then move it across by hand. Utter pain.

So they want to "reduce fragmentation" OK.

I found that snap can cause lots of issues. I installed keepass using snap, and it installed as a sandboxed app. Very nice for security you would think. Well, a short while later, after 3 upgrades to keepass, it deleted the oldest snap container, which just happened to contain my password file. So secure that even you can't use your passwords now!

Call me cynical, but is Snap possibly a resource hog as well?

Flatpak as a truly cross-distro application solution that works equally well and non-problematic for all

It appears that Canonical is continuing it's vice grip of unliateral, maybe dictatorial control on the development of Snap to the benefit of Ubuntu, but to the detriment of groups like Linuxmint, and all other non-Ubuntu based Linux distributions - like CentOS/Redhat, Suse/openSuSe, Solus, Arch/Manjaro, PCLinuxOS, etc, that are pushing Flatpak as a truly cross-distro application solution that works equally well and non-problematic for all. .

Canonical would do well to make sure they dont complicate things for whatever the next big Linux shift is.

I suspect zerocopy is going to be big, it can significantly improve performance provided you stay in one kernel. If someone can find a way to zerocopy data across containers, in theory you could have data pass through a firewall, nginx, your app tier, into the database and onto the filesystem, without copying it once instead of copying it 8 times.

What's wrong here is Canonical trying to position itself as a powerhouse and ascertain control over Linux users.

If upstream code presumes things will work that dont in snap (e.g. accesses /tmp or /etc) the snap maintainer has to rewrite that code and maintain a fork. Pointless work. Packaging for .deb is a no-brainer.

Why did I put the kdb in the snap file system? Because the app is sandboxed, so I had no choice.

+1 For Devuan here, running it on my home and work machines, and on my son's laptop, despite his IT teacher telling him to install a proper operating system like Windows 10....

>Linux needs an app delivery format Yeah, it's incredible that it has managed to survive for so long without one.

It's Snap that drove me to Arch, so it did me a huge favour. Seeing things like GNOME as a snap and other 'core' products wasn't something I was comfortable with. Personally, I prefer flatpaks as a packaging format when compared to snap and appimage. I agree that Linux needs an app delivery format, but snap's current implementation isn't it.

I run a fairly ancient RedHat Enterprise 6 on my 32-bit test machine and if I need something requiring Gtk3 (such as a latest Firefox or Chrome), I just make a chroot and use debootstrap (from EPEL) to get me a Debian 9 userland for that program. Easy. No bizarre "app stores", no conflicting packages. Do people use Snap app-stores because they don't know how to use the chroot command? Or are they just lazy? If it is because they want the added security of a container, substitute chroot with lxc... Shouldn't be necessary though; if you avoid non-ethical software (i.e App-stores), you are very unlikely to need the added security.

I've already said this, but if you think the average desktop computer user thinks a sentence beginning "I just make a chroot..." makes any kind of sense, you haven't been paying attention to the level of intelligence of the general public.

Well, that user can safely stay with Windows. Hiding these things from me makes wish that.