261 karma · joined January 26, 2020
It can provide psychological safety for your own subconscious. Write down every idea, regardless of how ridiculous it is. Every "What if I...". I sometimes do a question and answer format in a simple text/markdown document. Write out a question that's one facet of the issue you're working on, and answer it with a bunch of different options. Then discard or select or flesh out the responses. Ask questions about what might and might not work with each option.
It's amazing what having a few different new paths to try can do for your energy levels and motivation.
Like Glasswire though I'm guessing this doesn't alert on common traffic like DNS lookups via the host, which would still allow malicious software to get traffic in and out unseen.
What's the one-true, best-practise, everyone-accepts-it, supported-almost-everywhere way to provide dual ISP connectivity to an SMB with IPv6?
Once they solve the class of problems like that it'll take off a little faster.
So I wrote t2md, which after backing up the .json files constructs a folder tree of markdown files and attachments to represent your boards, lists and cards. From each card the description, comments and checklists are formatted into separate markdown files. Any attachment URLs you've embedded as links or images are then updated to their new relative paths so they continue to display. (The readme shows an example).
This was also my project to learn modern C# .NET Core async, which means it runs fast, is cross-platform and is a single-file binary. Let me know what you think!
Another related issue is the ULA design - they're meant to be randomly generated but it's not enforced, so you just know there'll be a bunch of internal networks with custom duplicate ULAs that will only show up when some businesses merge, so we'll be back to re-ipaddressing subnets.
IPv6 has changed a bit since the first RFCs (privacy extensions etc) so I imagine at some point someone will look at this and make some changes to suit. I wonder if it'll be relaxing ULA recommendations or adding something else entirely.
I'm insanely excited for never having to worry about subnet size again but it just doesn't seem like there's a clear best-practice one-true-way everyone-agrees way forward right now for a whole bunch of popular use-cases.
# load assembly System.Windows.Forms which will be used
Add-Type -AssemblyName System.Windows.Forms
# set powerstate to suspend (sleep mode)
$PowerState = [System.Windows.Forms.PowerState]::Suspend;
# do not force putting Windows to sleep
$Force = $false;
# don't allow the computer to be woken by devices or tasks (e.g. windows updates)
$DisableWake = $true;
# do it! Set computer to sleep
[System.Windows.Forms.Application]::SetSuspendState($PowerState, $Force, $DisableWake) | Out-Null;