jerdfelt

Joined 16 years ago

Karma

145

Submissions

Member since

May 29

[ my public key: https://keybase.io/jerdfelt; my proof: https://keybase.io/jerdfelt/sigs/Y2JqsCyETlsAKZOwKxY1OWl3-P8uzq1eAQsny2RgRMg ]

View on Hacker News

Recent submissions

Comment · 1 year ago

You don't have to wait until expiry. Transfers generally add 1 year of service (for most TLDs), so unless you're already at the limit, you can transfer everything now.

Comment · 2 years ago

Intel has proposed dropping 32-bit and 16-bit support in the future.

https://www.intel.com/content/www/us/en/developer/articles/t...

Comment · 2 years ago

It is mentioned in the first paragraph of the README:

shpool is a service that enables session persistence by allowing the creation of named shell sessions owned by shpool so that the session is not lost if the connection drops. shpool can be thought of as a lighter weight alternative to tmux or GNU screen.

Comment · 4 years ago

Python 2 was even more terse with it's print statement

    print >>sys.stderr, "foo"

Comment · 4 years ago

Does the ZNS (Zoned Namespaces) spec come close enough?

https://nvmexpress.org/new-nvmetm-specification-defines-zone...

Comment · 4 years ago

Is there anything that explains the why and how a bit deeper?

As an example, in the video "Packaging a Gem as a Nix derivation", he basically just and copies and pastes another default.nix, changes some strings and mentions he doesn't understand what 'passthrough.updateScript' does, but just changes a string there too.

This doesn't really help me understand Nix.

Comment · 9 years ago

I'm not sure if you're trying to imply that Lightning Network is vaporware, but there are currently three implementations that pass the integration tests:

https://github.com/lightningnetwork/lnd https://github.com/ElementsProject/lightning https://github.com/ACINQ/eclair https://cdecker.github.io/lightning-integration/

Comment · 9 years ago

You can get indirect exposure to SpaceX through some Fidelity mutual funds.

http://blog.sfgate.com/pender/2015/03/25/see-which-fidelity-...

Comment · 9 years ago

The Azores

Comment · 9 years ago

Location: Redmond, WA

Remote: Yes (have spent the last 6 years working remote)

Willing to relocate: No

Technologies: Python, C, Go, x86 Assembly, Linux, Hypervisors (Xen), Distributed Systems (check my resume for more)

Résumé: http://johannes.erdfelt.com/resume-hn.txt

Email: [email protected]

I've done work from low-level BIOS extensions, to Hypervisor development, to Linux kernel development, to Network Services (DNS, SMTP, DHCP, HTTP, TLS, etc) to high level distributed systems.

I've worked as the first engineer at a startup to large multi-national companies.

I'm generally looking for something in the cloud and/or backend internet services, but I'm open to something new as well.

Comment · 9 years ago

Unfortunately, Amazon does not appear to keep different sellers products separate in the warehouse. All it takes is one seller sending counterfeit products to the warehouse for their inventory to be contaminated by counterfeits. This makes "fulfilled by Amazon" more risky in some respects.

Comment · 9 years ago

In my experience, do a web search with a unique phrase out of the company or job description. It will often lead to the same job posting directly from the company.

Comment · 10 years ago

There is NTP the protocol[1], and there is NTP the implementation[2].

While the implementation is popular, there are alternatives. There is also OpenNTPd, chrony and ntimed for instance.

There are also alternatives to the NTP protocol too, such as PTP and SNTP.

[1]https://www.ietf.org/rfc/rfc5905.txt [2]http://www.ntp.org/

Comment · 10 years ago

These are farms of cheap Linux boxes.

They go out of their way to design and manufacture their own motherboards and equipment[1] to reduce their capital and operational expenses.

While the motherboard and enclosures are probably custom made, the components inside (CPU, memory, etc) are all "commodity".

[1] http://www.opencompute.org/

Comment · 10 years ago

The 63 character limit on domain name labels in RFC 1034/1035 isn't arbitrary, it's a limitation in the way DNS packets are encoded. The upper two bits of the label length are used for compression of labels in DNS packets.

Without protocol changes, DNS cannot support labels longer than 63 bytes.

However, I agree that validating it is unnecessary.