_ikke_

7 ms·

1.
by _ikke_ 2mo ago
The branch reflog (git reflog <branchname> or git log -g <branchname>) is a lot easier to follow in the case of rebase than the HEAD reflog (which gets an entry for each commit that gets checked out / applied).
2.
Fragnesia(github.com)
9 points by _ikke_ 4mo ago|0 comments
3.
Spec: Generic Methods for Go(github.com)
1 points by _ikke_ 5mo ago|0 comments
4.
by _ikke_ 7mo ago
My favorite from this release. > The built-in new function, which creates a new variable, now allows its operand to be an expression, specifying the initial value of the variable. So no need for separate helpers anymore to instantiate a
5.
by _ikke_ 9mo ago
As long as what it says is reliable and not made up.
6.
by _ikke_ 9mo ago
That's why I mentioned multiple addresses. The public addresses (assigned using SLAAC or DHCPv6) are for global reachability, while you use the local prefix for stable addresses within your network. If you want stable global addresses,
7.
by _ikke_ 9mo ago
The ipv4 routing table contains many individual /24 subnets that cannot be summarized, causing bloat in the routing tables. With ipv6, that can be simplified with just a couple of /32 or /48 prefixes per AS.
8.
by _ikke_ 9mo ago
With IPv6, it's common to have multiple addresses on an interface. So on options is to assign yourself an [RFC 4193]( https://datatracker.ietf.org/doc/html/rfc4193 ) fc00::/7 random prefix that you use for
9.
by _ikke_ 10mo ago
Instead, you get to hunt the nouns.
10.
by _ikke_ 1y ago
It affects many open source projects as well, they just scrape everything repeatedly without abandon. First from known networks, then from residential IPs. First with dumb http clients, now with full blown headless chrome browsers.
11.
by _ikke_ 1y ago
Only if that AI does not hallucinate, otherwise it would be useless.
12.
by _ikke_ 2y ago
Systems that use shamirs secret sharing, like openbao, require multiple operators to unlock the secret engine. Gitlab premium can also require multiple approvals before a merge request can be merged.
13.
Alpine Linux: Seeking Support After Equinix Metal Sunsets(alpinelinux.org)
10 points by _ikke_ 2y ago|1 comments
14.
Digital signatures and how to avoid them(neilmadden.blog)
4 points by _ikke_ 2y ago|0 comments
15.
Digital signatures and how to avoid them(neilmadden.blog)
278 points by _ikke_ 2y ago|82 comments
16.
by _ikke_ 2y ago
If a TUI is an option, then `tig blame` is a good interface. https://github.com/jonas/tig
17.
by _ikke_ 2y ago
> OpenSSH sshd on musl-based systems is not vulnerable to RCE via CVE-2024-6387 (regreSSHion). https://fosstodon.org/@musl/112711796005712271
18.
by _ikke_ 2y ago
They have a blogpost about it: https://tailscale.com/blog/free-plan > TL;DR: Tailscale’s free plan is free because we keep our scaling costs low relative to typical SaaS companies. We care about privacy, so unlike s
19.
by _ikke_ 2y ago
Until you want to introduce a change that affects both machines. You need to start rewriting history or cherry-pick the changes on both branches. The further the history diverges, the harder this becomes. Using branches for this does not sc
20.
by _ikke_ 2y ago
It's surprising how often projects retag releases. Diffoscope makes it easy to see the difference between the original tarball and the retagged versions. Changes vary from from forgetting to update an in-source version to tagging the w
21.
Running MSBASIC on my breadboard 6502 computer [video](youtube.com)
4 points by _ikke_ 3y ago|0 comments
22.
by _ikke_ 3y ago
For someone who understands git, it certainly is not. But if you are not aware of how git works, committing things when HEAD is detached could to confusion in the best case, and lost commits in the worst.
23.
by _ikke_ 3y ago
git diff by default outputs valid patch files that you can feed to patch out git apply. --word-diff does not Kernel development involves working with patches a lot, so it made sense to default to that, and --word-diff was added later anyway
24.
by _ikke_ 3y ago
Lift-off
25.
by _ikke_ 3y ago
Which is the equivalent of a fast-forward merge. Same result, different mechanism.
26.
by _ikke_ 3y ago
Lots of criss-cross merges make it really difficult to follow history, making it less useful. Note that merge vs rebase a false dichotomy. After rebasing you still have to merge your branch anyway, either fast-forward or with an explicit me
27.
by _ikke_ 3y ago
> Tools have been written to identify these mistakes, but it is hard to analyze whether references to a variable outlive its iteration or not. These tools must choose between false negatives and false positives. The loopclosure analyzer
28.
by _ikke_ 3y ago
The smallest prefix that can be routed is a /24, so that's the minimum amount you can get.
29.
by _ikke_ 3y ago
No, that's just copyright infringement. You use the license as a contract in order to use the code without infringing on copyright. If you don't adhere to the conditions in the license, the license is revoked, and you're back
30.
by _ikke_ 3y ago
It stops and asks you to resolve it and then you'd use the regular git commands to continue that operation (like git rebase --continue)

More ›