HNHacker News
TopNewBestAskShowJobs

frenchman99

1,405 karma · joined December 1, 2012

submissionscomments
frenchman99··on Librem One – A growing bundle of ethical services
I actually think it's great if there is commercial use of open source. That means they can reinvest development time into the projects, because their customers will depend on those projects.

The alternative seems to be walled gardens.

Other companies do similar things, such as Fastmail which develops the open source IMAP server Cyrus [1]. I've been a happy Fastmail customer for years. Cyrus is still free for anyone to use even though Fastmail makes money from it.

[1] https://www.cyrusimap.org/

frenchman99··on Google OAuth Login Issues
I don't know about Google, but we've had some issues with our Git hosting service last year. At times, it paralyzed us so much that we had to move to another one, which was not quite as good but more stable at the time.
frenchman99··on HTTP Error Code 418 I'm a Teapot is about to be removed from Node
Making everything dull won't benefit the field.

Sure we can remove every joke, every code comment that contains "FUCK", we can forbid commits that contain swear words, we can ask engineers to wear suits, we can remove animated GIFs from Slack and we can remove "418 I'm a teapot".

This kind of joke is what makes the job fun. You look at an implementation of an HTTP request and see "418 I'm a teapot", you smile for a second and keep working. That kind of fun contributes to happynness, increases psychological well-being and ends up contributing to long-term productivity.

In addition, removing the 418 code would break backwards compatibility. It will create way more problems than its availability does right now. This is the kind of thing you have to think about before-hand: add it and keep it, or don't add it. Now that we have a fun status code, we shouldn't add new ones. But removing the existing one is useless and damaging.

frenchman99··on Kite Responds to the Minimap and Autocomplete Issues
The 2nd sentence is an apology: "Over the last few days, Kite has been knocked around in social media (and the actual media) over several moves we made to expand our user base. It was a humbling experience, and I’d like to apologize to the entire open source community for our handling of these projects."
frenchman99··on A Message to Our Customers
What you're saying sound like a win-win situation for Apple and its customers. So whatever the reason is for them to speak out, it's a good thing that they do speak out. Isn't it?
frenchman99··on Streams: Mail 3.0 concept
I dislike how half of this blog post is just ranting about email. For example, I don't get this: "electronic messages are not real-time, they’re hard to manage in huge amounts, they work best for person-to-person dialogs"

These are "limitations" according to the author. But IMO they're the reason I like email:

- I like to be able to reply when I want, without the sender having the expectation of everything happening in real time, I have other things to do than answering real time to everything.

- Anything is hard to manage in huge amounts, which is why we hide less important stuff. Email has folders where you can put stuff in. You can archive emails. Or maybe this management issue is technical, as in "storing petabytes of emails is a difficult task" ? In that case, I have no real answer.

- I actually like the concept of mailing lists: they work where I already am (ie my mailbox) and I can stay up to date just like in a forum. And person-to-person dialogs do indeed work very well with email. I don't see that as a limitation.

---

Also, about this: "Stream is a group of threads. Simple as that."

That does not sound simple. In fact, just from that sentence, I didn't understand at all what it meant. I had to read on to get the idea. But I do see the point of "streams", and I agree that filters are usually complex to setup and maintain.

---

The part that I don't understand is this one: "With proper user/access management Streams could replace not just email, chats and group chats but also forums, blogs, mail lists, RSS and most of web 2.0 communities."

It sounds like what you need is RSS everywhere. RSS has a pull model too. You can setup ACLs on an RSS feed if you have some kind of authentication in place. It can replace mail lists, except that you'd still need to be able to push messages to it, which I don't see anything about in the blog post.

---

Finally, regarding this: "This fixes ambiguity around do-not-reply@ addresses"

I get the point of ambiguity and I have replied to no-reply addresses before myself, with an error message coming back. But I think ambiguity could be fixed with a header here, instead of throwing away the whole email infrastructure.

Imagine a "X-No-Reply: true" header. That way, email clients could disallow replying to such an email address. This has the advantage of being backwards compatible with everything that exists.

---

Overall, I do think that you can try something new, trying to "replace" email. But realistically, Google has tried several times and is struggling. Email has solid tooling and knowledge built around it, and I think trying to push for its self-improvement is worth a look.

Slack is sometimes said to be an "email-killer", but the fact is it replaces only one use of email. At my last company, we used Slack for real time stuff, notifications, quick questions, but not for everything. And that's great. Because email sucks for real time stuff right now (although initiatives like JMAP may make things better).

Email seems to carry the notion of importance, which is not true of chat messages I think. The reasoning behind this is, I think, an incoming email stands alone, whereas a chat message is quickly surrounded by other messages.

Also, emails have a clear receiver, the receiving email address. This means that if you get a message to "devs@project.org" and you are a dev, you are de-facto concerned by this email, which is a reason to read it thouroughly. This is not true of chat messages which do not have a "receiver" but are instead posted to the more liberal notion of "channel".

frenchman99··on Email Encryption Software Relies on One Guy, Who Is Going Broke
I'd guess that whoever downvoted you thought this was a troll meant to start a flamewar with C++ vs. PHP and whether one or the other is more difficult (read "better" or "a real language").

It's interesting to note though, that Facebook does uses PHP and C++ extensively. And Facebook maintains a large a number of open source PHP and C++ projects. So I suppose that some Facebook engineers are more involved with PHP and some more involved with C++.

But more importantly, I don't think Facebook engineers are bound to a technology. They think about how to solve problems. If PHP is the best tool to solve a problem, they'll use that. If it's C++, they'll use that instead.

← PreviousPage 7 of 7