nathants

41 ms·

571.
by nathants 4y ago
if that doesn’t suck for you, that is also fine.
572.
by nathants 4y ago
if a setup that is a: - terminal - browser - window manager sounds awful, avoid desktop linux. you will find it to suck, even on a fancy distro like pop. otherwise, dual boot windows and linux. work on linux, play on windows. this works gre
573.
by nathants 4y ago
nah, its fine[1]. on the frontend you have a single thread and all state is in memory. on the backend anything goes. in both domains you have to use sane, simple designs, and that can be challenging. 1. http://github.com/nat
574.
by nathants 4y ago
more rss, less thumbnails, no chum buckets.
575.
by nathants 4y ago
- inability to install recent versions of software with distro package manager - pstree has too much stuff in default install - lack of recent kernel - lack of good wiki
576.
by nathants 4y ago
arch or alpine edge. the rest are too annoying.
577.
by nathants 4y ago
this is the way.
578.
by nathants 4y ago
rebase is a multi stage command that often requires force push. as good as it can be, discouraging it’s use, especially in contexts where git is considered challenging, is probably the play.
579.
by nathants 4y ago
lately i’ve been using stash, reset hard, stash pop. work on a single patch over main. use a backup branch prior to stash, just in case.
580.
by nathants 4y ago
accurate.
581.
by nathants 4y ago
git is like cpp, you have to use a subset: - push - pull - checkout - checkout -b - merge —ff-only - stash - stash pop - reset —hard origin/master - reset —soft $hash - commit -m
582.
Show HN: Immutable backups so simple that unborkable(github.com)
5 points by nathants 4y ago|0 comments
583.
by nathants 4y ago
this is a good idea, but difficult to nail in scope and multi-lang support. i’ve made similar attempts[1,2]. tbh if this had go support i’d probably try it today. json, yaml et al are ways to declare literal data. this is good. they are fin
584.
by nathants 4y ago
rest and vest. it’s a good retirement. for the op, probably something interesting first.
585.
by nathants 4y ago
there are two kinda of people who discuss self driving cars: - members of comma.ai discord - everyone else conversation amongst one of these groups is more interesting than the other, and there isn’t much crosstalk.
586.
by nathants 4y ago
work for startups. exclusively. yes, you’ll leave some money on the table. you’ll run into some toxic environments. you’ll quit or get fired regularly. you’ll see some shit, the good, bad, the ugly. more importantly, you will never be bored
587.
by nathants 4y ago
reagent[1], the most used interface to react from clojurescript, hasn’t had major api changes in a decade. it’s just as productive today as it was a decade ago. find a good workflow[2], and build stuff. churn is fine, it’s either motivated
588.
by nathants 4y ago
this is the way.
589.
by nathants 4y ago
i’ve been trying really hard to write good docs lately[1]. it’s kind of terrifying to describe something as easy and fun knowing that it could be hard and rage inducing, but we have to try! yes, build a better terraform. build a better pupp
590.
by nathants 4y ago
git-remote-gcrypt + rclone + s3.
591.
by nathants 4y ago
excellence in software engineering isn’t something you can buy. a university can’t bestow it. a title or certification can’t assert it. it’s something one grows over time because they are passionately curious. it grows because they love to
592.
by nathants 4y ago
there is a critical mass of devs who want clojure[script] but not emacs: https://github.com/BetterThanTomorrow/calva
593.
by nathants 4y ago
this is correct. it's the datarace between these components, and the possibility of ebpf dropping data because of a slow userspace callback, that makes this flaky.
594.
by nathants 4y ago
by the time a user prompt is displayed, all metadata has been joined to the packet, and libnetfilterqueue is waiting for a decision. my understanding of what is happening is as follows: - 1: libnetfilterqueue gets a packet. - 2: lookup pack
595.
by nathants 4y ago
i don’t think so. i think exactly what you’ve documented is the case. if the callback can’t keep up with the data before the ringbuffer overflows, data is lost. in that case, the solution is to increase the size of the ringbuffer, giving th
596.
by nathants 4y ago
bandwidth monitor use case seems like a perfect fit, and the occasional missed packet wouldn’t be an issue. picosnitch looks really cool! i’ve rss subscribed to its github commits.
597.
by nathants 4y ago
i use a kind of tui. it is actually a gui, pops up fullscreen. you can’t click it though, just keypress interaction. i agree with you. especially if i’m filtering all traffic, i need to be able to y/n quickly and easily. https:/&
598.
by nathants 4y ago
1. get linux router on lan or linux vpn on wan. 2. install opensnitch or similar on 1. 3. route all traffic through 1. 4. figure out how to deal with rule management and new connection requests from 1 to wherever is most convenient for you.
599.
by nathants 4y ago
ebpf used in this way is typically nonblocking. it drops data instead of blocking. for a firewall, that’s potentially bad. can ebpf operate in a blocking manner while making drop/allow decisions on packets WITH reliable access to the c
600.
by nathants 4y ago
the issue is that libnetfilterqueue doesn’t have pid information, and so that must be looked up or joined to another data stream at runtime. this can fail. flakes at this point can be dangerous, and can reduce confidence in the system. they

More ›