nevalem

joined 1 year ago
[–] nevalem@programming.dev 2 points 9 months ago

I might have a few hours a month to help out if there's something I feel I can help with.

[–] nevalem@programming.dev 1 points 10 months ago

An organization that opposes the Galactic Empire. The Alliance is a coalition of rebel cells and resistance groups that formed in response to the Empire's authoritarian rule.

[–] nevalem@programming.dev 1 points 1 year ago

We have a custom nix package each for the org, teams, down to the project level that a dev can use to bootstrap what they need from day one with a no-knowledge-about-nix installer.

[–] nevalem@programming.dev 4 points 1 year ago

There is a storied history in computing to use tongue in cheek self referential acronyms to denote some humor and finality in distinguishing things that purposely fill a niche in the world of competing, often pricey, commercial software and other hackable reasons.

So I bet you're rubbing wrong those of us who remember that gnu is not unix, and more specifically wine is not an emulator. Because they really aren't.

[–] nevalem@programming.dev 8 points 1 year ago

I don't believe this is possible and actively protected against in the dht protocol implementation.

The return value for a query for peers includes an opaque value known as the "token." For a node to announce that its controlling peer is downloading a torrent, it must present the token received from the same queried node in a recent query for peers. When a node attempts to "announce" a torrent, the queried node checks the token against the querying node's IP address. This is to prevent malicious hosts from signing up other hosts for torrents. Since the token is merely returned by the querying node to the same node it received the token from, the implementation is not defined. Tokens must be accepted for a reasonable amount of time after they have been distributed. The BitTorrent implementation uses the SHA1 hash of the IP address concatenated onto a secret that changes every five minutes and tokens up to ten minutes old are accepted.

I believe you would have to know the torrent first, then you could discover other nodes. This is probably why that tool can't tell you anything outside of it's known list of torrents.

Source: http://bittorrent.org/beps/bep_0005.html

[–] nevalem@programming.dev 3 points 1 year ago

I have that exact combo loaded up on my desk right now. Great pen and I love that ink.

[–] nevalem@programming.dev 1 points 1 year ago

Don't forget about fq!

[–] nevalem@programming.dev 1 points 1 year ago

Find a better instance to use. Some are overloaded and from my very limited understanding so far of the tech, where you have an account or where you tell your client to "enter", you're limited by that instance's resources to serve you up what you're viewing.

When I moved, it's now like night and day in terms of performance and responsiveness. Still get the occasional problem but totally usable.

[–] nevalem@programming.dev 3 points 1 year ago (2 children)

Yeah, and sometimes my comments get duplicated. Growing pains of the fediverse.

[–] nevalem@programming.dev 5 points 1 year ago

I'm going on 25+ years and at principal eng/architect level. My take would be to find something, try it, and find if it excites you. There isn't a wrong answer. At worst you'll become a generalist, fluent with more and more until you find a niche in an array of things you're conversant in. At best you'll dive deep into a specific area and become more and more of an expert on a topic.

Right now I'm really into rust, rewriting tons I've done in the past with more experience under my belt, and learning more about web assembly. Running rust in web assembly on any platform including the user's browser without really having to think about distribution targets is something that excites me. I think I can gleam a future that might compete with how revolutionary kubernetes has been, but even if I'm wrong the things I've learned will still hold up.

If the huge array of things overwhelms you, find a problem and try to solve it. Just the act of doing that and heading into that rabbit hole can open up new worlds you never even knew existed, and helps strengthen one of what I would consider the best qualities in good devs: competent independent troubleshooting. The fun I've had trying my hand at bypassing att router restrictions, extracting certificates from roms, architecting my home network with self hosted kubernetes and all the home automation stuff, low level c embedded systems programming for homemade iot sensors... The things you can do with tech is usually always in reach of anyone with some time and an Internet connection.

Also, don't neglect the open source community. Start a project, contribute to someone else's... Probably the biggest leap I took as a dev consisted of a simple change to a large oss project. The mentality, guardrails, rule self imposed on the project we're incredibly impressive to me and I learned so much about the benefits of code quality, good review, automated, well everything, really opened my eyes to what a small team can do given a common goal they are passionate about, something that at times can be missing from enterprises that might have profit as king.

Let us know what you end up at. You never know if you might inspire another dozen people with something that interests you. Good luck!