Because that’s how most people implicitly frame headlines like this one: a generalization of the public

Oh i know

I’m more blaming the system than the user. The system is designed to be as addicting as possible. Literally a century of addiction research into drugs and gambling, all used to squeeze every drop of engagement from the user

Anything to get that dopamine drip from the Black Rectangle

It’s not about what the user wants. It’s about what will make the most profit for Microsoft

Federated git hosting platform when?

You know, you could just ask what that means

s/org/li means replace org with li

I like solving puzzles, and I have a knack for programming specifically

But it doesn’t have any built-in concept of users, write permissions, or authentication (except for commit signing)

Hosting an unauthenticated git repo would be the equivalent to an open ssh port with no password required

Not to mention collaborative things like issue tracking, PRs, forums, etc

I wonder if it’d be feasible to make a fediverse github

“Unlisted” means you can’t find any of them via search or on the creator’s page. But if you still have the URL, you can view them directly

Which includes public playlists other people have created

Lox

Once i have a solid implementation, I wanna morph it into a custom scripting language for generating diagrams (a la graphviz or mermaid js)

https://github.com/Lightfire228/lightweaver

I literally just wrote this a few hours ago (line 55)

Languages evolve. It’s a very common thing for descriptors of negative things to become slang for insults. Not to say we should be encouraging this behavior, but rather that policing it is ineffective at best.

Effective solutions address the underlying issues

(Destigmatization of ailments is a good thing, but doing so by stigmatizing the words themselves often has a Streisand effect)

That doesn’t mean anything. They can request your browsing history directly from your ISP

Me: I wonder how they know it was staged

But investigators later concluded Greene had staged the attack, alleging she paid a body modification artist earlier to make it look like she was injured. Officers also found zip ties in Greene’s vehicle similar to those used on her, and the co-conspirator’s phone had been used two days earlier to search “zip ties near me."

Lol

Waydroid doesn’t intend on supporting it. It’s a piece of code that checks for evidence of “tampering” (such as an unlocked bootloader, or root access), and sends those bits of data off to Google’s servers for verification

It’s antithetical to Waydroid and device freedom, and is used by banking apps for “security” reasons, as well as media apps for piracy reasons

And is a massive pain for anyone who root’s their devices

Never make things more “impressive”

Make them more comprehensible

Reduce the cognitive load required to understand and reason about a piece of code. Honestly, the more you can express complicated ideas simply, the more impressive you are

I did this once

I was generating a large fake dataset that had to make sense in certain ways. I created a neat thing in C# where you could index a hashmap by the type of model it stored, and it would give you the collection storing that data.

This made obtaining resources for generation trivial

However, it made figuring out the order i needed to generate things an effing nightmare

Of note, a lot of these resource “Pools” depended on other resource Pools, and often times, adding a new Pool dependency to a generator meant more time fiddling with the Pool standup code

• if something feels too “heavy”, like it’s doing xml formatting, file manips, a db insert, and making coffee, all in a single class or function

Separate out those “concerns”, into their own object/interface, and pass them into the class / function at invocation (Dependency Injection)

• use “if guards” and early returns to bail from a function, instead of wrapping the func body with an if

public Value? Func(String arg) {
  if (arg.IsEmpty()) {
    return null;
  }
  
  if (this.Bar == null) {
    return null;
  }

  // ...
  return new Value();


  /// instead of

  if (!arg.IsEmpty) {
    if (this.Bar != null) {
      // ...
      return new Value();
    }
  }
return null;
}