srctree

Gregory Mullen parent 43c19213 c8c4b4eb
hugo did an update... and I hate it... stupid hugo

config.toml added: 58, removed: 40, total 18

@@ -3,6 +3,7 @@ languageCode = 'en-us'

title = 'The Gray Hatter'

uglyurls = true

enableRobotsTXT = true

#summaryLength = 20

[params]

email = 'grht@gr.ht'

Author = 'Gray Hatter'

content/posts/2019-06-09-seemed-like-a-good-idea.md added: 58, removed: 40, total 18

@@ -9,6 +9,8 @@ Context: While working on wifi functionality for HUDTDS (heads up display that d

screen scrape, I looked into exactly how it works and learned about a cool thing you can do. Because I've never seen

anything like this, I thought it was interesting.

Have you ever wanted to add a series of structs to your application, but enumerating them all in a single location

seems like way too much work? Well you're in luck! There's a GNU extension that allows you to create your own named

object segments. Anything you declare with `__attribute__ (( segment("__named") ))` will be stored in it's own segment.

content/posts/2019-06-22-do-less.md added: 58, removed: 40, total 18

@@ -11,12 +11,12 @@ produce less data, instead of being a **10×** dev, be a **10&div;**

developer. Now, that may be a bit misleading, because I don't want to suggest

you should want to be, *just a software developer*. Really what I'm getting at

is that I think you should try to channel the ideals of what it is to be an

engineer. It may seem to be simply a linguistic difference, but I think it's a

pretty important semantic difference as well as being an important one.

Developers write a lot of software, implementing new features left and right.

New +100 line commits daily. Some of the best ideas I've seen come from people

who are happy to be a developer, and they're ones that I easily respect. The

critical difference, (at least for the remainder of this rant,) is that

engineer.  It may seem to be simply a linguistic difference, but I

think it's a pretty important semantic difference as well as being an important

one. Developers write a lot of software, implementing new features left and

right. New +100 line commits daily. Some of the best ideas I've seen come from

people who are happy to be a developer, and they're ones that I easily respect.

The critical difference, (at least for the remainder of this rant,) is that

developers are the ones to omit possibly the defining engineering maxim.

> *Perfection is achieved, not when there is nothing more to add, but when

content/posts/2019-07-14-informed-consent.md added: 58, removed: 40, total 18

@@ -15,9 +15,9 @@ Yet, this is still breaking news. When I first read this story, I felt

bad for the people who were contacted for comment by the news reporting agency

who broke this story. It's not hard to imagine that they were surprised that the

device was recording their conversation, especially given that they didn't even

say the keyword. I'd bet it was even more surprising that it contained enough

information for a reporter to find and contact them. That level of invasion of

privacy is a pretty hard hit to just absorb.

say the keyword.  I'd bet it was even more surprising that it

contained enough information for a reporter to find and contact them. That level

of invasion of privacy is a pretty hard hit to just absorb.

I, obviously, wasn't surprised, but even given the base technical level of most

users, they shouldn't have been surprised either. I don't think it shouldn't be

content/posts/2019-09-16-passwords-considered-harmful.md added: 58, removed: 40, total 18

@@ -12,9 +12,9 @@ everyone is incapable of using them correctly. That includes both developers,

and users. Meanwhile they're a constant security risk, not only because

individual passwords can be broken, stolen, guessed, or given away. But also

because, if you have no other data than email and password pairs you do have

something worth stealing. Painting an even larger target on your back. It's time

to stop using password for authentication. Passwords should be considered harmful,

and you should avoid them whenever possible!

something worth stealing. Painting an even larger target on your back.

It's time to stop using password for authentication. Passwords

should be considered harmful, and you should avoid them whenever possible!

First, consider what problem passwords solve. User authentication. No, really,

that's it! That's the only thing they're good for[^1] [^2]. Passwords are shared

content/posts/cheating.md added: 58, removed: 40, total 18

@@ -15,20 +15,20 @@ The general consensus is the problem is getting worse, and rarely better. Escape

From Tarkov clearly has a cheating problem.

Now this isn't a problem that's unique to EFT, but prevalent throughout not only

all online games, but all online systems. The issue for EFT now is that cheating

has become 'especially noticeable' in most recent patch. It feels as if the

baddies are winning this patch[^1]. Not exactly ideal -- but it is something

that's to be expected, because there will always be cheaters, right? As I write

this I feel as if I should try to preempt the whole "well we can't win so we

might as well give up" idea. The people preventing users from abusing systems,

the good guys, they have to be perfect, every single time. Where the abusers,

they only have to be right once to win any given battle. It's an arms race, one

where even the largest online services have given up on the goal of attempting

to prevent people from abusing their services. If even the largest, best funded

services have given up on trying to prevent abuse, Why shouldn't everyone with

an internet facing service cry that; "the only winning move is not to play"?

That's because winning the fight against cheaters really doesn't matter. Well,

kind of, let me explain.

all online games, but all online systems.  The issue for EFT now is

that cheating has become 'especially noticeable' in most recent patch. It feels

as if the baddies are winning this patch[^1]. Not exactly ideal -- but it is

something that's to be expected, because there will always be cheaters, right?

As I write this I feel as if I should try to preempt the whole "well we can't

win so we might as well give up" idea. The people preventing users from abusing

systems, the good guys, they have to be perfect, every single time. Where the

abusers, they only have to be right once to win any given battle. It's an arms

race, one where even the largest online services have given up on the goal of

attempting to prevent people from abusing their services. If even the largest,

best funded services have given up on trying to prevent abuse, Why shouldn't

everyone with an internet facing service cry that; "the only winning move is not

to play"? That's because winning the fight against cheaters really doesn't

matter. Well, kind of, let me explain.

[^1]: [1]: Depending on who you listen to, every patch is the worst patch for

cheating, this just happens to be the one where cheaters are allowed to both

layouts/_default/index.html added: 58, removed: 40, total 18

@@ -8,7 +8,7 @@

<li>

<h3><a href="{{ .Permalink }}">{{ .Title | markdownify }}</a></h3>

<p>{{ .Summary }}</p>

<p>{{ .Summary | plainify }}</p>

</li>

@@ -24,20 +24,35 @@

<p>I pretend to be a security geek. I also write code, sometimes maybe good, sometimes maybe shit!</p>

<p>

<span class="context">github</span><br>

<a href="https://github.com/grayhatter">github.com/grayhatter</a>

<span class="context">srctree</span><br>

<a href="https://srctree.gr.ht/">srctree.gr.ht</a>

</p>

<p>

<span class="context">email</span><br>

<a href="mailto:{{ .Site.Params.Email }}">{{ .Site.Params.Email }}</a>

<span class="context">github</span><br>

<a href="https://github.com/grayhatter">github.com/grayhatter</a>

</p>

<p>

<span class="context">email</span><br>

<a href="mailto:{{ .Site.Params.Email }}">{{ .Site.Params.Email }}</a>

</p>

</div>

<h3>Projects</h3>

<p>

<a href="https://github.com/GrayHatter/hudtds">HUDTDS</a><br>

Heads up display; that doesn't suck. Replacement infotainment system for build in car displays

<a href="https://srctree.gr.ht/repo/srctree">srctree</a><br>

<span class="context">srctree.gr.ht/repo/srctree</a><br>

Code sharing and sync that doesn't break the back button. Think github,

but actually good.

</p>

</div>

<p>

<a href="https://github.com/GrayHatter/hudtds">HUDTDS</a><br>

Heads up display; that doesn't suck. Replacement infotainment system for build in car displays

</p>

</div>