Notices by codesections (codesections@fosstodon.org), page 20

@goo

I don't really know #python and I know even less about making a web browser in python. However, I know exactly who *is* an expert on just that: @the_compiler the guy behind #qutebrowser—a full browser written which is not only written in python but is also excellent. It's the browser I use every day, including right now.

@SuperFloppies

Yeah, I think most static site generators let you do something similar. In the static site generator I use (#gutenberg) you can use standard HTML comments (`<!-- -->`) which will show up in the generated file. Or you can use comments in the template (`{# #}`), which will get stripped out. I appreciate having both options.

@goo

Also, just curious, what are your goals for the browser you want to write? Is it just about being able to write your own (nothing wrong with that!) or do you want to build something that others will want to use? If so, what features would set your browser apart from the others out there? All very interesting—good luck!

@emsenn Yeah, those might be better solutions.

My quick approach for now is to change from
```
{%- if context.content is containing("<article") -%}
```
to
```
{%- if context.content is containing("<article") or context.pages -%}
```

This adds in all the CSS to sections with sub-pages, which isn't *quite* as efficient, but it's close

@emsenn

Thanks. I just realized that my implementation has a bug, though—I'm just checking the text of the page/template, so I'm *not* checking the text of pages/templates that are included in other Tera syntax. This has slightly borked the formatting on my blog homepage, so maybe I was a bit too clever for my own good!

(But I bet I'll figure out a fix)

@kev I ran into the same issue. It turns out that you can de-link your the account as soon as your Medium account is created and go to just a email login. So, it's bad, but not *quite* as bad as it look. (Still crazy, though)

@mkb

I haven't used KeyBase chat (much, anyway) though I have it installed. With all these things, though, it comes down to what teams are already using—I'm not going to be able to show up somewhere new and get people to change their tools on day 1! And I'm not part of any teams that use KeyBase chat, at least at the moment.

@thor

Warranties tend to be pretty awful in general. Retailers push them because they're often very profitable, but they're generally not a good deal for you at all—unless you *really* can't afford to pay for the repair. In the long run, it's far better to save the money on the warranty, put it aside, and use that to fund repairs.

@h4ck3r9

#notlegaladvice #AmALawyerButNotLicensedInYourState

I would *strongly* recommend against relying on any of this, for anything. There's a long tradition of people trying arguments like this, and they *never* work, and people who try them get fined/imprisoned

Just revised my #gutenberg templates to conditionally inline CSS *only* when the specific styles are needed. This cuts the number of lines in my homepage by 30%!

(Thanks to the power of compression, this only cuts the *download* size by ~10%, but it makes the `view-source` a lot more readable. Plus, not everyone gets the compressed page)

@emsenn

@hund @cameron @ignitionigel @pinguino
Working now. Thanks!

@hund @cameron @ignitionigel @pinguino
Test toot using Vim with the set.editor command—it seems to work, but not to include my config settings or spellcheck. I'll have to look into this more!

@pinguino @hund @ignitionigel @cameron My problem with using quitebrowser for Mastodon is that I *really* can't spell, and quitebrowser doesn't have a spell check (understandable—they're hard to implement well).

I'm not familiar with Bitlbee. Does it check spelling?

@mooshoe @kelbot Well, *I'm* not—but I never was :D

(Er, well, I'd say that they're no more "purely driven by profit" than the average public company, maybe less. But that's still pretty purely driven by profit for their shareholders!)

Others may well disagree, and argue that Google is especially bad, and I'd see where they're coming from. I wouldn't put it that way, but I'd agree that Google's scale makes them especially troubling—and some of their (alleged) antitrust actions use that scale

@mooshoe @kelbot I'd agree with most of that. I tend not to use words like "evil" for an org like Google, personally—even if accurate for some orgs, it's rarely helpful/precise. And I wouldn't say that they're "conspiring", exactly.

What I would say is that they have economic incentives that would cause them to push the Internet in less free/less private directions; they seem to be acting on those incentives; and I'm troubled—troubled enough to play my (small) part in reducing dependence

@mooshoe @kelbot One thing we *can* tell from the outside, though, is that Google has direct, economic interests in gathering data—in fact, it's their whole business model. Thus, *if* you care deeply about your privacy, Google's interests aren't aligned with yours, but opposed. And it would take inhuman saintliness to ignore those interests.

If you *don't* care about your privacy, the questions seem much harder; Google offers many cool toys in return for the data they make billions off of