Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
networkimprov
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
6 ms
·
1.
▲
by
networkimprov
4y ago
What's your opinion of Etherpad? Does their roadmap overlap with your vision?
2.
▲
by
networkimprov
4y ago
Wow, have to ask whether you're interested enough to contribute? :) > You can't use a volatile cache ... > all this work to juggle JSON in flat files I really don't think I've misused the cache! I didn
3.
▲
by
networkimprov
4y ago
A TMTP client can subscribe to any number of TMTP services at different sites.
4.
▲
by
networkimprov
4y ago
FWIW, most of the roadmap for this project is not described on the website nor defined in the protocol. This is a deep topic, and "messaging" is not the only goal, nor even the principal one :)
5.
▲
by
networkimprov
4y ago
(Author here.) I imagine that existing web-based bulletin boards would simply copy messages to TMTP users if requested. Conversely, TMTP groups/lists could be copied to a read-only website.
6.
▲
by
networkimprov
4y ago
(Author here.) The message format definition is included in the protocol doc only as a convenience. Ultimately it would be two standards. Trying to "upgrade" the email ecosystem is an impossible goal, and the requirements I'm
7.
▲
by
networkimprov
4y ago
(Author here.) Thanks for your interest & support! Yes, the default concept for an Internet messaging service is "everyone can reach anyone". This isn't helpful for online services and businesses who need to reach their m
8.
▲
by
networkimprov
4y ago
(Author here.) Development has been paused for ~1y as I've been at work creating a vehicle to take this forward. The protocol specifics (e.g. identifiers & types) aren't polished, because I focused on features in working code.
9.
▲
by
networkimprov
4y ago
(Author here.) TMTP clients maintain concurrent (possibly intermittent) connections to any number of TMTP services, and each service gets its own inbox. So you don't need a separate app instance per service. Inboxes for a set of relate
10.
▲
by
networkimprov
4y ago
(Author here.) The client UI is designed for desktop. A mobile frontend is in the works. Tentatively planning to use Ionic Framework with Vue.
11.
▲
by
networkimprov
4y ago
Hi, author here, AMA!
12.
▲
by
networkimprov
5y ago
Here are a few fundamentally different async protocols in development which could challenge SMTP: DIME - https://en.wikipedia.org/wiki/Dark_Mail_Alliance Math Mesh - https://mathmesh.com TMTP - https:/
13.
▲
by
networkimprov
5y ago
Oddly, the Web Monetization spec, probably essential to ILP adoption, doesn't indicate how browsers would contact an Interledger network site. https://webmonetization.org/specification.html https://github.co
14.
▲
by
networkimprov
5y ago
It's the underpinning of the Web Monetization effort backed by Mozilla. https://webmonetization.org https://grantfortheweb.org
15.
▲
by
networkimprov
5y ago
"mnm" enables a safer, better, decentralized email network. It's open source (and not blockchain). https://mnmnotmail.org & https://twitter.com/mnmnotmail Because SMTP will not be fixed, here&
16.
▲
by
networkimprov
5y ago
I have sketched a plan for a venture, for which I'd need co-founders (e.g. mobile app code & UX expertise) -- feel free to reach out via Twitter @mnmnotmail (link above). Those big corporate advocates necessary for the success of a
17.
▲
by
networkimprov
5y ago
At this early stage, I'd say the biggest obstacle is reaching a wide enough audience; I have no prior fame, and no PR budget yet.
18.
▲
by
networkimprov
5y ago
And yet none of those corporations has displaced email, despite the fact that it has become a universal cyberattack channel, with a stagnant UX that doesn't address most real-world use cases for email! I saw a need for a safer, better,
19.
▲
by
networkimprov
5y ago
The success of a wide variety of messaging and discussion apps demonstrates that the network effects of email are not necessarily a high barrier. What these products have lacked, which email has, is an open protocol. (XMPP had early success
20.
▲
by
networkimprov
5y ago
You might like TMTP from the mnm open source project (my work).
21.
▲
by
networkimprov
5y ago
Didn't XMPP originate with a single vendor? And JMAP? Didn't SMTP also originate in the field? Are you saying that the Matrix authors won't submit an RFC?
22.
▲
by
networkimprov
5y ago
Could you define "real open protocol" vs "public API"? If the former entails an adopted RFC, isn't it common practice to prove need via a product before proposing a standard? Asking because I'm at work on a saf
23.
▲
by
networkimprov
5y ago
Have a look at TMTP from the mnm project.
24.
▲
by
networkimprov
5y ago
The primary problem for email at this point is that it's a highly effective cyberattack channel, because it allows anyone, claiming any identity, to send you any content, without limits. This cannot be "fixed" as it's th
25.
▲
by
networkimprov
5y ago
Great story of "market-based" engineering management & collaboration, where different teams could trade resources (in multiple categories) with other teams to optimize each component while staying in-bounds with the mission re
26.
▲
by
networkimprov
5y ago
Before ditching SMTP/etc, we'd need something to replace them. TMTP (my work) is a candidate. More at https://mnmnotmail.org/
27.
▲
by
networkimprov
5y ago
During 2010-2017, I worked on creating a "pocket server", the size of a keyfob, which would be the basis of a pads/tabs/boards personal computing environment. It would connect to any number of local screen devices via Bl
28.
▲
by
networkimprov
5y ago
Not yet! See TMTP from the "mnm" project (my work).
29.
▲
by
networkimprov
5y ago
I know of two: DIME - Dark Internet Mail Environment mnm - mnm is not mail (my work)
30.
▲
by
networkimprov
5y ago
Sorry folks, I thought it was OK to resubmit links that didn't make the front page. I never got a "Show HN" link on the prestigious Show page because someone else posted it and made the front page. So I tried some other URLs.
More ›