Slashdot Mirror

According to https://github.com/mozilla/add..., it does:

* sends header "X-1057" to sites
* if the page contains certain strings, it flips those strings upside down for 2-6 seconds and then reverts to normal (ex. "privacy" and "control"). It'll also put an on hover box on them with a link.

Dunno if that's really the right plugin, test plan, or full list of what it does, but it was linked from the parents link, which was waaaay more to read than the above two bullet points. If someone sees the above and knows them to be wrong, please reply and correct me.

Systemd has three fundamental issues:
-Piss poor community engagement. Their reaction to any request or security report is to first say the requester or reporter is an idiot. For example: https://github.com/systemd/sys... where he claims that it's perfectly valid for a confused systemd to just run user as root instead of error out.

If I read *just* that bug report, the part of the community engagement that is not working well is from the community of incensed (seemingly Debian) users who insult people in bug reports.

Pottering explained the general approach they took which was:

In systemd we generally follow the rule that when we encounter a unit setting that does not validate syntax-wise we'll log about it and ignore it, for compat reasons. We do the same for User= here as for all other options.

However, he was open to taking a different approach for most security-related settings, and as such the issue is fixed

Systemd has three fundamental issues:
-Piss poor community engagement. Their reaction to any request or security report is to first say the requester or reporter is an idiot. For example: https://github.com/systemd/sys... where he claims that it's perfectly valid for a confused systemd to just run user as root instead of error out.

If I read *just* that bug report, the part of the community engagement that is not working well is from the community of incensed (seemingly Debian) users who insult people in bug reports.

Pottering explained the general approach they took which was:

In systemd we generally follow the rule that when we encounter a unit setting that does not validate syntax-wise we'll log about it and ignore it, for compat reasons. We do the same for User= here as for all other options.

However, he was open to taking a different approach for most security-related settings, and as such the issue is fixed

> Ironically enough, LinkedIn scrapes its users browser for known extensions. See https://github.com/prophittcor... for details.

Server interrogates clients for their functionality.

That doesn't sound nearly as nefarious as you think it does.

I think there's just too many things unnecessarily built into systemd rather than it utilizing external, usually, already existing utilities. Does systemd really need, for example, NFS, DNS, NTP services built-in? Why can't it run as PID 2 and leave PID1 for init to simply reap orphaned processes? Would make it easier to restart or handle a failed systemd w/o rebooting the entire system (or so I've read).

I think you are confused.

Here is the service unit file for systemd-timesyncd From this it should be quite apparent that:
1)No, systemd (the pid 1) isn't an NTP service. The systemd project includes a different time synchronisation service that is built using the systemd libraries to work better during sytemd boot under certain conditions than other clients (such as ntpd, chronyd etc.) that work perfectly adequately with systemd under normal conditions.
2)The service doesn't run as root, but as a dedicated user.
3)There is a separate, dedicated service, that can be stopped and started without touching the pid 1.

The same goes for the DNS resolution service/daemon.

I am not aware of any NFS-related service that is built into systemd.

I think you've been reading too much anti-systemd FUD, and believing it.

I think there's just too many things unnecessarily built into systemd rather than it utilizing external, usually, already existing utilities. Does systemd really need, for example, NFS, DNS, NTP services built-in? Why can't it run as PID 2 and leave PID1 for init to simply reap orphaned processes? Would make it easier to restart or handle a failed systemd w/o rebooting the entire system (or so I've read).

I think you are confused.

Here is the service unit file for systemd-timesyncd From this it should be quite apparent that:
1)No, systemd (the pid 1) isn't an NTP service. The systemd project includes a different time synchronisation service that is built using the systemd libraries to work better during sytemd boot under certain conditions than other clients (such as ntpd, chronyd etc.) that work perfectly adequately with systemd under normal conditions.
2)The service doesn't run as root, but as a dedicated user.
3)There is a separate, dedicated service, that can be stopped and started without touching the pid 1.

The same goes for the DNS resolution service/daemon.

I am not aware of any NFS-related service that is built into systemd.

I think you've been reading too much anti-systemd FUD, and believing it.

Systemd has three fundamental issues:
-It's not systemd versus sysv, it's systemd vs. sysv/syslog/cron/at/user session management. That's a whole lot of potential controversy to take on for a project that you either adopt as a distro or you don't, and giving the users choice in a matter like this is an impractical thing for most distributions. It also creates challenges for security, because something you do to provide user-level access to some capabilities becomes a potential path for a vulnerability (of which systemd has had a fair share).
-Piss poor community engagement. Their reaction to any request or security report is to first say the requester or reporter is an idiot. For example: https://github.com/systemd/sys... where he claims that it's perfectly valid for a confused systemd to just run user as root instead of error out. It's one thing to not catch such a scenario, but for your *gut* reaction to be "oh yeah, you are doing it wrong, nothing should have let you do that", implication there that he's just *trying* to make life hard for systemd. Most people immediately recognize a security problem is something that *must* contend with unclean input. This is also why journald continues to have no native text logging. Instead of engaging with the community to create a best of both worlds solution with both human readable text and high performance indexing and *some* mild defense against tampering (only real solution to that is one-way append-only logging to an external part). Instead, the reaction is "you guys are idiots" and those use cases are ignored. It's one thing to have a rough start, but if there continues to be this much vitriol around a project this many years on, the project has screwed up their relationship to the community.
-It also becomes the poster child for a lot of other design changes that are common to the distros, but may not even be systemd related. Sometimes exacerbated by systemd (dbus), but largely not particularly the projects fault. However it has the curse of being very visible and loud and can attract other problems with systemd complaints.

Things that have come from that include:
-Unreasonable disdain for text format logging. Rather than pursue a compromise where text data is a first class citizen, they say 'just schedule dumps to a text file ever so often' or '*add* syslog *and* journald'. There is clear disdain for the whole idea of a format that doesn't require a specific tool to read, despite reasonable proposals to do things like externalized binary metadata to preserve the best of both worlds.
-Unreasonably drawn out vulnerabilities while they spend sometimes months complaining about it being intentional instead of fixing it.
-Inability to allow a user to select a deterministic boot mode. Yes, properly done dependencies are the 'right' way to solve, but some folks would rather have a deterministic boot than contend with unknown race conditions. It would be a simple matter to have a serialized boot behavior with a very deterministic approach to serializing services consistently that do not seem to rely upon each other.

It also becomes a matter of controversy because it does bring value, and attract people to white knight for it:
-Faster boot, not everyone cares, so this being optional would be an easy thing to do to make folks happy
-Fast and structured log analysis, which could have been done with external metadata to keep text analysis feasible.
-Intelligent use of cgroups to keep reasonable tabs on a process
-Standard facilities to 'daemonize' software without the software having to do the right double fork and exit dance. It would have been one thing if libc had provided a function, but it hasn't so every daemon has had to do that weird dance itself, and many of them get it wrong, particularly home-grown software
-Encapsulating the overwhelmingly common startup scenarios as a config file instead of rewriting the same basic scipt over and over. So long as

Best example is when systemd decided to hijack kernel's command line

How could it do that? Has systemd taken over grub/lilo too?

I never used systemd, but I know that the linux *kernel* is passing the command line params to the init program, whatever that is. Go read about it here.

systemd doesn't have to hijack anything in order to complain about params it doesn't understand. Maybe it's just giving itself airs about legit kernel params it considers "illegal"? (the way the stupid bash programmable completion won't let me complete file names to some programs it thinks it knows everything about).

You're quite correct. The Minix license is visible at https://github.com/minix3/mini... .

I'm not convinced BSD is the most infringed license, but you seem correct that infringing it is common place. One reason difficulty is that the BSD license does not have the clear consequences that GPL violation does, that violation loses access to all other GPL licenses from the same copyright owner. The Free Software Foundation has been using this successfully to enforce GPL compliance.

... For now.

1.) AST published an open letter, and the fact that the disclaimers are not posted does not seem to bother him much.
See here: http://www.cs.vu.nl/~ast/intel...

2.) Minix3 License, states that, when distributed in Binary form, the DOCUMENTATION has to reproduce the copyright notice and, well, there is no documentation whatsoever abut the ME.
See here: https://github.com/Stichting-M...

Having said that, security through obscurity is not a sensible policy, and AST's courtesy is not enough. If intel is using minix, they should say so and print the license.

Anyone who has trouble with systemd is too stupid to run linux. Stick to Apple and let the real people go about their business.

As of this writing, there are 705 open issues for systemd on GitHub.

You're calling all of them, every one of the people who use systemd in Arch, Debian, Red-Hat, etc. and opened an issue, too stupid to run Linux?

Use KaldiSTT locally https://github.com/MycroftAI/m...

Use Mycroft with a local speech-to-text server.

https://mycroft.ai/

Local STT with KaldiSTT https://github.com/MycroftAI/m...

When all these companies talk about AI, what they really mean is a way to provide back-end servers, neural net chips, GPUS and such so that they can charge for the deep learning systems that everyone wants to use to process the data to find those little nuggets. They are not working on building general AI systems or even working on how to architecture one. They want to make money and the money is in the service. Just like Amazon, Google and IBM. Facebook uses AI and provide some services. But the future where you need fast real-time detection of things that your automated cars and planes will be doing, where it sends all that to a massive computer to do the processing and sends the results back is what they are talking about (at least in these last few and next 5 years). The AI systems, based on neural nets as still so simple compared to what humans can do, it will be a little while before real general AI gets around. And the Robotic technology and hardware to house it is so far behind the software at this point. It will all come, bio-robotics, Bio-AI, might be here first. You can't stop technology and you won't stop developing AI systems, we learn more and more each month, but there are still a lot of unsolved hard AI problems and formalizing all that is even harder.

Then why does Baidu have Apollo?

The cutting edge of R&D on all AI is often supported by tech giants like Google, Facebook, Microsoft, Baidu.

In Chrome using https://github.com/Eloston/dis... . this before moving to Firefox.

I use that as well, but it doesn't always work. I think auto-play video is about the rudest thing a web developer can do, and if they've gone to the trouble to even work around a plugin that blocks it, I just close the page.

In Chrome using https://github.com/Eloston/dis... . this before moving to Firefox.

Change the way AI is done.

It doesn't have to be so esoteric: make it "visible" as layered voting machines where each factor "votes". Use data layouts similar to spreadsheets and relational database reports so that "regular" office workers can study, arrange, relate to, and adjust factor weightings, mask weightings, and routing paths (similar to "hidden layers") as needed.

Color coding, similar to Excel's conditional formatting can make high-match and low-match factors stand out for test cases or trouble-shooting.

Staff can be divided similar to the processing tree. For example, in vision recognition, one group can focus on people identification, another on furniture and building identification, another on outdoor patterns, etc. The idea of one giant do-it-all monolithic neural-network is not practical if we want rank-and-file AI and dissect-able AI. Bring in modularity and divide-and-conquer techniques.

You may need an experienced AI domain specialist to help divide up tasks and provide factor (test) guidelines or drafts, but once staff have their basic assignments they can focus and tune without being caught up in the big picture and way-out theory.

As far as content control, all I have to do is tunnel thru to my VPS in the Netherlands. I am watching some shows in the states right now that are banned here. This setup is extremely simple and explained here: https://github.com/inwtx/SSH-W...

https://github.com/corna/me_cl...

I had to google this NodeJS debacle. This is amazing.

The fact that Noordhuis attempted to revert the pronoun changes after another admin approved them is especially boorish.

> Decompiling is merely an optimization problem [...] you lose comments and (without debug info) function and variable names.

There are folks working on this: https://github.com/eth-srl/Nic.... The idea: use machine learning to look at t lot of code to come up with plausible variable names (the first demonstrator was AFAIR for a Javascript deminifier from ETHZ).

Who knows... perhaps the thing could come up with some useful comments too... I'd bet it'd be better than the Doxygen comments churned out by many a Java sweatshop.

It's kind of a hack, but it gets the job done. Basically you have types like float32x, int32x4 etc. There are methods to add and subtract them using non vector code but if the hardware supports them using vector instructions, those vector instructions get substituted for the non vector code.

https://github.com/tc39/ecmasc...

I have seen this being waved around back in July. Seems to work in theory, but I do need Intel ME in my workplace, so I never did try it on an actual system.

You're the one who should have read the goddamn bug report's discussion.

When you say nonsense like

don't adhere to standards

you're full of bullshit.

What fucking standards would those be? Wait, there is no standard in this case! That's a huge part of the fucking problem!

This comment makes a good argument in favor of it being a valid username when considering certain possibly-applicable standards.

Even Poettering himself states that "some distributions are less restrictive".

Later on, Poettering himself points out that there is no standard: "please work with the POSIX, shadow-utils, libuser communities, as well with the other Linux distributions to come up with a single unified set of rules".

So don't give us this bullshit about "standards". There are no fucking standards, meaning that a username like "0day" should be accepted by systemd, and if it doesn't support such a username then systemd is in the wrong.

Your pathetic attitude is why so much software today is so flawed and insecure. You cry and moan about "conforming to standards" instead of doing the responsible thing and making your software properly handle unusual cases that are perfectly valid and reasonable.

You're the one who should have read the goddamn bug report's discussion.

When you say nonsense like

don't adhere to standards

you're full of bullshit.

What fucking standards would those be? Wait, there is no standard in this case! That's a huge part of the fucking problem!

This comment makes a good argument in favor of it being a valid username when considering certain possibly-applicable standards.

Even Poettering himself states that "some distributions are less restrictive".

Later on, Poettering himself points out that there is no standard: "please work with the POSIX, shadow-utils, libuser communities, as well with the other Linux distributions to come up with a single unified set of rules".

So don't give us this bullshit about "standards". There are no fucking standards, meaning that a username like "0day" should be accepted by systemd, and if it doesn't support such a username then systemd is in the wrong.

Your pathetic attitude is why so much software today is so flawed and insecure. You cry and moan about "conforming to standards" instead of doing the responsible thing and making your software properly handle unusual cases that are perfectly valid and reasonable.

You're the one who should have read the goddamn bug report's discussion.

When you say nonsense like

don't adhere to standards

you're full of bullshit.

What fucking standards would those be? Wait, there is no standard in this case! That's a huge part of the fucking problem!

This comment makes a good argument in favor of it being a valid username when considering certain possibly-applicable standards.

Even Poettering himself states that "some distributions are less restrictive".

Later on, Poettering himself points out that there is no standard: "please work with the POSIX, shadow-utils, libuser communities, as well with the other Linux distributions to come up with a single unified set of rules".

So don't give us this bullshit about "standards". There are no fucking standards, meaning that a username like "0day" should be accepted by systemd, and if it doesn't support such a username then systemd is in the wrong.

Your pathetic attitude is why so much software today is so flawed and insecure. You cry and moan about "conforming to standards" instead of doing the responsible thing and making your software properly handle unusual cases that are perfectly valid and reasonable.

If you want to see an even stranger and worrying discussion around a similar enough problem affecting Linux, look at this bug report involving systemd and concerning unusual Linux usernames.

Almost right away Lennart himself declared it "not-a-bug" and closed the issue, claiming it involved "not a valid username" and claiming "I don't think there's anything to fix in systemd here."

Thankfully, others looked into this matter in more detail. They pointed out that the unusual username involved should very well be considered valid, regardless of what the systemd developers believed. They pointed out that it was in fact a serious problem. They pointed out that it should be fixed.

At some point Michael Biebl came in, babbled nonsensically about "trolls" and locked the discussion, basically giving a big "fuck you" to everyone who wanted to work toward getting these problems fixed properly.

Lennart then deleted some user-submitted comments in a show of censorship, and again denied that there was a problem.

The most absurd part is near the bottom, when Lennart states, "don't forget we don't break people's stuff". This is particularly unusual because systemd is well-known for causing all sorts of breakage and problems for many Linux users.

Was the problem affecting macOS a big mistake on Apple's part? I think so. But at least they got a fix out very quickly once they became aware of the issue.

Their approach is much saner than what we're seeing happen with Linux and systemd, as shown by the systemd bug report and absurd handling of the bug as described earlier.

I'll take Apple's approach any day.

You can use an autohotkey script to control all those HP buttons.
https://github.com/jleb/AHKHID

if you needed a transaction to verify a private key with the network how would you ever make a new address to receive? it becomes chicken and egg.

the means of private signing key to public address is well known and does not need to create a transaction to verify. take directory.io ( site seems down, article about it https://www.coindesk.com/bitco... )

any block explorer can check if a address resulting from to a private key has unspent outputs or skip the network traffic by running a local node modified to index unspent output from all addresses ( https://github.com/bitpay/bitc... ) instead just ones which private keys are held in a wallet file, ie default node.

lastly in order to show how difficult it is to brute force private keys look at the large bitcoin collider project ( https://lbc.cryptoguru.org/ ) which is a distributed effort working on a puzzle transaction where coins were sent to numerous address with amounts increasing with number of none zero bytes bits.

Classic Theme restorer

Just go ahead and use userChrome.css to apply a different theme.

I've found uBlock Origin in dynamic mode to be highly superior to NoScript (either XUL or WebExt).

Enable "I am an advanced user" in the settings, then open the uBO toolbar button and mark 3rd party scripts and 3rd party frames as red in the global column. After this, add exceptions (noop = grey) or allow/deny in the global or local columns to unbreak any broken sites you encounter. The UI also handily shows which sites have inherited settings.

https://github.com/gorhill/uBl...

It only takes a couple of minutes to get the hang of, but it's an extremely powerful tool (and adds nicely on top of the good old static filters in uBO). Unlike NoScript, you can noop sites only on specific domains, instead of globally.

People use bare pointers all the time: "this". They also use references, which are semantically equivalent.

"Modern C++" with smart pointers etc doesn't come close to protecting you from use-after-free bugs. See for example https://github.com/isocpp/CppC...

Here you go, I just uploaded a copy of the source and my 1.77 xpi to github.

https://github.com/xtraeme-xt/BetterPrivacy/releases

Already use Privacy Badger, but thanks, appreciate the recommendation! There are still scenarios where websites use local storage to enforce super cookies. Publishers tend to be the worst offenders. The Volatile Storage addon in combination with BetterPrivacy were a sort of hackish way to purge the system.

Just in case the uninitiated might confuse this for a serious statement; to be clear he's completely trolling.

It is a species of trolling, designed to attract flaming responses and try to paint Rust proponents as arrogant, insufferable know-it-alls whose opinion can be safely dismissed. There's nothing factually wrong in that statement, it's all in the approach.

Non-trolling assessment would be that Rust's safety guarantees help, and help enormously, with the development of robust code, but are not a panacea. E.g., see the results of fuzzing some Rust programs and libraries: those are all bugs detected at runtime, not by the compiler. Note also that all except two, one segfault and one stack overflow, result in a controlled crash with a backtrace, which makes identifying the bug much easier.

It is also clear to everyone who's not a blind zealot that it's impracticable to re-implement every piece of code in Rust. Which doesn't mean that its use in places where it's felt that its safety could make a difference shouldn't be explored.

They aren't "available to install if someone feels like being edgy", at least not without some manual effort of fetch'ing (that's the FreeBSD pseudo-equiv of wget), using strfile(8) (bet you've never heard of it until now, have you?), and dropping non-pkg-managed files into /usr/local/share/games/fortune manually. So, if by "being edgy" you mean "making a port/pkg for it", guess what: I've done exactly that:

* https://github.com/koitsu/fortune-mod-freebsd-classic (also contains history of what was done by FreeBSD Project members)
* https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=223798

I refused to sit by and watch Ken Arnold's work (the import of classic 4.4BSD-Lite fortune into FreeBSD was done 23 years ago) and part of BSD/UNIX history get thrown in the trash. My hope is that this makes several people happy (probably us old UNIX beardos who still have a sense of humour and don't get triggered by seeing words they disagree with).

The committers responsible for the modifications and removals (especially the latter) should have done the above.

then you don't care about user's privacy.

https://github.com/mozilla-mob...

Funny enough, you often see the same people (or at a minimum the same behaviors) behind the destruction. It's not just Adria Richards and Anita Sarkeesian and Zoe Quinn shitting up the things computer nerds love, it's gone fucking mainstream and can be seen everywhere, from the Eich excommunication debacle to the fuckheads Sarah Sharp and Matthew Garrett (mjg59) technicolor poop-spraying on Linux. The staunchly anti-political technology field has become not only politicized but strongly polarized. We need to cut out the social justice cancer without apologies.

CoralineAda (Coralina Ada Ehmke) or at least connections to "her" via "her" hot dumpster file "Contributor Covenant" seem to pop up often in places that subsequently find themselves embroiled in identity politics/feminist/SJW "live and let live as long as you live like we tell you to" controversies. Codes of conduct like hers are often used to marginalize white and male individuals under a patently false veil of equality.

krainboltgreene (Kurtis Rainbolt-Greene) is an aggressive "male feminist" that also makes an occasional appearance when something shitty and smeared with identity politics goes down.

Here, have some links for more reading. I'm getting depressed looking this trash can up and I don't want to dredge up more memories. Read for yourself.

https://github.com/opal/opal/i...
https://github.com/opal/opal/i...
https://www.reddit.com/r/Mozil...
https://news.ycombinator.com/i...
http://esr.ibiblio.org/?p=6918
http://paul-m-jones.com/archiv...

Also, before they get around to replying, fuck AmiMoJo and PopeRatzo in particular. They are prime examples of the burnt crust that needs to be scraped off the Pyrex dish of computing.

Funny enough, you often see the same people (or at a minimum the same behaviors) behind the destruction. It's not just Adria Richards and Anita Sarkeesian and Zoe Quinn shitting up the things computer nerds love, it's gone fucking mainstream and can be seen everywhere, from the Eich excommunication debacle to the fuckheads Sarah Sharp and Matthew Garrett (mjg59) technicolor poop-spraying on Linux. The staunchly anti-political technology field has become not only politicized but strongly polarized. We need to cut out the social justice cancer without apologies.

CoralineAda (Coralina Ada Ehmke) or at least connections to "her" via "her" hot dumpster file "Contributor Covenant" seem to pop up often in places that subsequently find themselves embroiled in identity politics/feminist/SJW "live and let live as long as you live like we tell you to" controversies. Codes of conduct like hers are often used to marginalize white and male individuals under a patently false veil of equality.

krainboltgreene (Kurtis Rainbolt-Greene) is an aggressive "male feminist" that also makes an occasional appearance when something shitty and smeared with identity politics goes down.

Here, have some links for more reading. I'm getting depressed looking this trash can up and I don't want to dredge up more memories. Read for yourself.

https://github.com/opal/opal/i...
https://github.com/opal/opal/i...
https://www.reddit.com/r/Mozil...
https://news.ycombinator.com/i...
http://esr.ibiblio.org/?p=6918
http://paul-m-jones.com/archiv...

Also, before they get around to replying, fuck AmiMoJo and PopeRatzo in particular. They are prime examples of the burnt crust that needs to be scraped off the Pyrex dish of computing.

It's strange to see the FreeBSD project being attacked like this. My interactions with the FreeBSD and the OpenBSD communities have always been excellent. As long as you do your homework and don't waste their time, the members of those communities are always extremely friendly and willing to lend a helping hand. They are some of the most tolerant, open and non-bigoted individuals I've ever dealt with.

Those communities are a huge contrast to the Rust programming language project's community. Despite all of their claims about being "inclusive", Rust has one of the most tyrannical and totalitarian communities that I've ever experienced in my many years of open source software use. I mean, they even have a Rust Moderation Team dedicated to eradicating/banning anybody they dislike! The justify this eradication squad through the existence of their tyrannical and contradictory Rust Code of Conduct.

The hypocrisy and contradiction of the Rust Code of Conduct is unreal. The very same paragraph that says "we don’t tolerate behavior that excludes people" starts off with "We will exclude you from interaction ...". They openly promise to engage in the same sort of behavior that they claim is intolerable!

It gets even weirder when you look at the list of Rust contributors, and it becomes clear that most of them are young, white males. Of course, there's nothing wrong with being young, white, or male. It's just strange to see such a lack of diversity in a community that claims to go out of its way to promote and encourage diversity. I've seen much more natural diversity in pretty much every other open source community I've ever dealt with, especially the ones that don't go out of their way to focus on diversity in any way. It's like diversity happens best when you aren't fixated on artificially creating it.

I think that the FreeBSD community is being wrongly smeared here. It's one of the most open and friendly communities I've ever dealt with. Yet while this excellent FreeBSD community is being attacked without merit, absolutely nothing is done about open source communities, like the Rust community, that in my opinion promote censorship and intolerance while claiming to support the opposite.

https://github.com/microg/andr...

Some malware authors even post their projects in public: https://github.com/microsoft

Apparently anybody can submit issues, pull requests, and so on to ensure the world gets the benefit of high quality malware with all the goodness of open source.

A gun makes a bullet go fast, and weighs about ten pounds.

Nonsense. A and doesn't weigh even one pound in the case of a pistol.

Handguns are only effective out to about 20 feet,

That's a lot of bullshit.

and even then two or three shots probably won't kill the bad guy.

That depends very much on how good your aim is.

The important bit of the system is the part which aims the gun at a vital part of the target's body and fires at the proper instant. That part is called the marksman. It weighs about 180 pounds.

What does yolo 9000 running on a raspberry pi zero weigh?

Everything you said was wrong.

ImageZoom hasn't been updated, but there is ZoomImage which seems similar.

The developer behind Classic Theme Restorer has a set of custom CSS files that can tweak a lot of the interface.

The obvious agenda here is to make repository hosting first more centralized, then more "hosted at MicroSoft", then, once people depend on the hosted service, demand monthly fees for it.

Nobody tell him GitHub already exists and charges money. Microsoft's interested in GVFS is because 1) Git sucks at handling large repos, and 2) Microsoft has a 270GB repo.
The original /. article back in Friday had better comments, including one linking an article describing why they chose Git for source control, and what GVFS actually does.

I've heard of people using git for strange purposes (blogging?!) but for a second reading this headline I had the horrific thought that someone was attempting to create a filesystem backed by git.

Fortunately that's not the case, GVFS (not that other GVFS) provides a git-compatible filesystem abstraction on Windows 10.

Although I'm not a big git fan, I do have to say I'm impressed with Microsoft's recent moves toward open-source and interoperability. If the Linux Subsystem is ever a first-class citizen in the MS ecosystem, I could even see myself using Windows again.

I've heard of people using git for strange purposes (blogging?!) but for a second reading this headline I had the horrific thought that someone was attempting to create a filesystem backed by git.

Fortunately that's not the case, GVFS (not that other GVFS) provides a git-compatible filesystem abstraction on Windows 10.

Although I'm not a big git fan, I do have to say I'm impressed with Microsoft's recent moves toward open-source and interoperability. If the Linux Subsystem is ever a first-class citizen in the MS ecosystem, I could even see myself using Windows again.

the best option is to completely abandon the manufacturer, unlock the bootloader and install a different operating system in the hopes it will remain better supported.

Example of a different operating system with commercial support : Sailfish X (for Sony Xperia X) by Jolla, the former Nokia engineer who were working on Maemo/Meego for the N700/N800/N900/N9 series before Elop and Microsoft happened to them.

That's another alternative possibility to the usual suspects (like LineageOS, etc.)

(Note: NOT Android based at all - except for the platform drivers, it's still GNU/Linux under the hood like back when at Nokia).

Regarding phones fromOnePlus, Jolla doesn't currently have an official line of products, but there's a vibrant community so a community port might show up in talk.maemo.org

Okay, but you've already moved the goalposts.

I didn't move any goal posts, the developer of NoScript did. First he said day and date with Firefox 57, then he said "later this week". Read his blog post.

Compare and contrast NoScript with uBlock Origin. uBlock Origin shipped ahead of Firefox 57's release, NoScript didn't. uMatrix shipped before Firefox 57's release, NoScript didn't. In the end, it's up to NoScript to deliver. If uBlock Origin and uMatrix can, NoScript can too.

Okay, but you've already moved the goalposts.

I didn't move any goal posts, the developer of NoScript did. First he said day and date with Firefox 57, then he said "later this week". Read his blog post.

Compare and contrast NoScript with uBlock Origin. uBlock Origin shipped ahead of Firefox 57's release, NoScript didn't. uMatrix shipped before Firefox 57's release, NoScript didn't. In the end, it's up to NoScript to deliver. If uBlock Origin and uMatrix can, NoScript can too.