Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
ddevault
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
85 ms
·
901.
▲
by
ddevault
6y ago
It's not hugged to death, my Gemini server is just kind of unstable and crashes a lot. I'm keeping an eye on it.
902.
▲
by
ddevault
6y ago
Gimp is a volunteer-run open source project. You ready to get cracking on that patch?
903.
▲
by
ddevault
6y ago
Microsoft is a member of RIAA.
904.
▲
by
ddevault
6y ago
Yes. > So, SourceHut is not hosted in anyone's cloud. I own all of the hardware outright and colocate most of it in a local datacenter. > I just built a new server for git.sr.ht, and boy is she a beaut. It cost me about $5.5K as
905.
▲
by
ddevault
6y ago
Perhaps. But I'm appealing to HN readers here, not to China.
906.
▲
by
ddevault
6y ago
Code like this doesn't happen unless a programmer sits down and writes it. You have a responsibility to refuse to write code which is morally wrong. This is the cost if you don't: real human lives.
907.
▲
by
ddevault
6y ago
Yeah, that's not how it works. That's how you want to believe it works so you can sleep at night. In reality that person probably turned to the gig economy, with no job security, benefits, or upwards mobility, and works twice as m
908.
▲
by
ddevault
6y ago
It's not that great. Remember that a real person used to do this work, and they've been replaced by a buggy robot in the name of cost savings. That's one fewer job on the market. That real person would also have been able to
909.
▲
by
ddevault
6y ago
Google does not ignore your website, what nonsense. I have always posted on my own domain and I have a strong readership. RSS exists, link aggregators exist (how did you find this article? On HN!), it's not all glum and woe.
910.
▲
by
ddevault
6y ago
More than just considering the reader's interests, it's also against the author's interests to use Medium. They've become more and more draconian, bloated, and, well, the same as any other venture capitalist ultra-growth
911.
▲
by
ddevault
6y ago
>if you don't delete the whole repo. Right, but the repo and the other features are fundamentally not the same thing on SourceHut. It's entirely unnecessary to take down the mailing list (perhaps to take down the archives, but
912.
▲
by
ddevault
6y ago
But on GitHub, the PRs and issues cannot exist independently of the git repository. They'd have to make substantial software changes to support this approach. Sure, they could do that, but - have they? No. SourceHut has.
913.
▲
by
ddevault
6y ago
Then removing the offending material can be done without shutting off the mailing list entirely. I mentioned this in the article. On GitHub, everything - bugs, pull requests, wikis, code - is baked into one thing, your repository, which i
914.
▲
by
ddevault
6y ago
Erp, it was a typo. Sending HTML emails to anyone is rude.
915.
▲
by
ddevault
6y ago
Yeah, but I disrecommend doing this. Starting a new thread is usually better.
916.
▲
by
ddevault
6y ago
Because it does not contain offending material.
917.
▲
by
ddevault
6y ago
All lists on lists.sr.ht, for one. Using the In-Reply-To header requires foreknowledge of email headers, the purpose of Message-ID, and how to find it. It's not very approachable. Most mailing lists who have thought about it don't
918.
▲
by
ddevault
6y ago
A good practice when firing off an email to a list like this is to do a git blame on nearby code, identify the maintainers, and come up with a list of people to Cc directly on the email. If you can get the git repo, you don't need the
919.
▲
by
ddevault
6y ago
Hah! 8G of RAM is plenty for a workstation. My main laptop away from home is only on 4G and I seem to manage just fine. My home workstation is 32G but the only time I get even close to that is when I use /tmp to compile a large proje
920.
▲
by
ddevault
6y ago
You really shouldn't send plaintext emails to anyone at all. It's rude.
921.
▲
by
ddevault
6y ago
- It gets, uh, sent. If you send it to a mailing list, the mailing list will forward it to the subscribers. - Yes, there are online archives available for each mailing list. - Yes. - Both. It shows up with you as the author and them as the
922.
▲
by
ddevault
6y ago
I disrecommend using In-Reply-To when sending a revised patchset. Just start a new thread. Mailing lists which prefer In-Reply-To are in the minority.
923.
▲
by
ddevault
6y ago
>When I want to reply to someone, do I email the list or the person? How do I make sure the emails are threaded properly? Most people will (and you should, too) use reply-all when participating on a mailing list, which should land the re
924.
▲
by
ddevault
6y ago
It's also the first usable workstation for a novel open-source architecture. It's not as fast but that's a feature which, in my opinion, makes the price parity reasonable. Progress is gradual.
925.
▲
by
ddevault
6y ago
I have written a guide for emailing patches: https://git-send-email.io And also for configuring your client for plaintext, which is strongly preferred by most mailing lists: https://useplaintext.email If you or anyon
926.
▲
by
ddevault
6y ago
The price really isn't that outrageous. Consider the use-case: this is a mini-ITX form-factor with a standard power supply, M.2 slots, a PCIe adapter, etc. This is designed for desktop workstations. It comes with the CPU, motherboard,
927.
▲
by
ddevault
6y ago
There's a BIG difference between "data driven self-help" emails from a self-proclaimed "marketing pro" and on-topic development discussion and patchsets.
928.
▲
by
ddevault
6y ago
This article is about the developer workflow, not about what the end-user software should do.
929.
▲
by
ddevault
6y ago
Let them come. Asshole companies shouldn't discourage people from building cool things. Until the C&D arrives, the author ought to express themselves in defiance of Nintendo.
930.
▲
Mailing lists are resistant to censorship
(sourcehut.org)
205 points
by
ddevault
6y ago
|
98 comments
More ›