That’s not the issue. Spammers sell each other lists of numbers that answer calls. By answering and blocking, you block one spammer and gain 5.

So how do I get it?

Sounds more plausible. Either that or the system is reporting RAM + swap - VRAM reserved memory somehow.

I initially thought that meant GPU accelerated compilation. Sadly not.

How does 2 x 32 GB sticks give you 67 GB of RAM? Did you download more RAM?

A 2+ hour long shitpost, that’s commitment.

I’m sick of this too.

While countries like Brazil, Mexico, and India have privacy laws on paper, enforcement is weak, allowing both domestic and foreign vendors to deploy invasive technologies unchecked.

So they’re doing just as well as the US?

Oh that looks nice! I was using Dissent which is very light on resources but I kept running on a couple issues. I’ll try that.

I pissed off the Tankie Triad LMAO

LOL, good going.

Back in the days before git, I worked on a small software+hardware startup with ~ 10 people. We used Trac very successfully to do project management. I know it’s been updated to mesh with git. You could set up roadmaps, track issues (which can be linked to code or not), tracked hours (using a plugin), and keep our internal KB in the integrated Wiki. There was a Trac Hack for everything we wanted.

I don’t recall which Gantt plugin we used, but there’s a few options: https://trac-hacks.org/tags/gantt

We didn’t use kanban back then, again, options: https://trac-hacks.org/tags/kanban

One could say it’s their fiduciary duty.

I don’t why the downvotes, this looks quite relevant. From what I understood, the Facebook app runs a web server exposing an API, which is used by any website with the Meta Pixel tracking lib to connect to it and query a persistent user ID. So if I don’t use the Facebook app, their tracking is based only on my browser fingerprint, correct?

deleted by creator

deleted by creator

F-Droid seems to manage it just fine. It’s even got reproducible builds.

Because there isn’t one. OC is deranged.

Why didn’t they write this instead of the BS above?

Why build another CLI editor?
What motivated us to build Edit was the need for a default CLI text editor in 64-bit versions of Windows. 32-bit versions of Windows ship with the MS-DOS editor, but 64-bit versions do not have a CLI editor installed inbox. From there, we narrowed down our options…
Many of you are probably familiar with the “How do I exit vim?” meme. While it is relatively simple to learn the magic exit incantation, it’s certainly not a coincidence that this often turns up as a stumbling block for new and old programmers.
Because we wanted to avoid this for a built-in default editor, we decided that we wanted a modeless editor for Windows (versus a modal editor where new users would have to remember different modes of operation and how to switch between them). This unfortunately limited our choices to a list of editors that either had no first-party support for Windows or were too big to bundle them with every version of the OS. As a result, Edit was born.

TL;DR: We tried nothing and were all out of options.