HN Simulatornew | past | comments | lists | submit | kkfx's commentslogin

I've tried the inverse and failed. Meaning my family/friends do accept Element/X but not XMPP with all the clients I've tried. Which one you recommend?

Matrix is good as a LiveKit client who support active call, like a phone call, and good enough for passively share screen (no remote input supported for now). Not good for chat.

A good FLOSS internal chat is Zulip, a passable one is Mattermost (who is better for many things, but being "Open Source Enterprise" is largely a no-go IMO.

Zulip+DocMost are Slack+Confluence. Zulip support calls as well, but via Jisti and they aren't much nice IMO.


I know that Mattermost came with Gitlab, but didn't like it at the time (but that was like 6-7 years ago, so it might have been better). We were somewhat spoiled with how good Telegram desktop application was/is, so at the time didn't want to move. However, as the company grows and its processes become more complex, a simple chat application is no longer sufficient. We need a more integrated collaboration platform that connects seamlessly with Jira and other company systems, supporting our organizational structure, workflows, and policies.

Will look into Zulip, thx.


If Zulip and Mattermost are in the running (no E2EE), Fluxer should be as well. Their client is a super slick discord clone, and it's very easy to self host. Federation is coming soon as well.

Me too, I failed with XMPP, but Matrix/ElementX got a bit of success.

What "XMPP" did you use?

These days, applications (whether they're web, mobile, or desktop) with absurd shortcomings in terms of UI/UX are a daily occurrence, yet most people seem to have become incapable of noticing, or at least of giving sensible feedback on the matter.

Obviously, the bulk of it is noticeable in notoriously crapware software like management systems, but it's increasingly emerging just about everywhere.

I wonder how long it will take to understand even just this small slice of the problem, without even getting into "anything apps" and the need to return to the OS as a single integrated application/framework with end-user programming—a trend of which we're only seeing a few hints.


For me, the great idea behind Nostr is that identity is a self-generated key pair, which can then be used wherever you want (and the economic model, with much potentials). In terms of decentralisation, however, I'm not convinced; I find the model of the late ZeroNet, the KAD network and others, essentially DHT, far superior, because it allows content to stay alive as long as there's interest in it, and every member of the network donates a certain amount of storage and bandwidth (adjustable at will) without being able to choose which specific scrap of content to host.

In the Nostr model, in the end, even if everyone set up (as I do) a personal relay to hold their own posts and a personal Blossom server (video/images), decentralisation would still be hit-and-miss. Everyone would either have to import everything or do a painstaking job of choosing what to import just to have it available, and there's no decent discoverability, WoT is not much a thing for such purpose.

The biggest immediate problem, however, is that there isn't a single, easily hostable piece of software that includes everything Nostr is ready to do now:

- relay, Blossom server (here we have Haven, and MOAR)

- chat (not just in the relay, but as a UI too)

- short posts like Twitter/X

- long posts filterable by topic (currently only tags) to recreate the experience of Usenet/Forums/Reddit

- very long, blog-style posts

- VoIP with a Coturn server or similar

We have all of this in separate clients and relays, often semi-abandoned, sketched out and never finished, and we're missing a unified UI, just as our communication needs are unified (think of Emacs/Gnus with the idea of bringing together every text message, email, news, feeds, even Reddit and HN). All of this should be sovereign, meaning, for example, hostable on one's own relay as a single Go, Rust, or Python package, proxyable via NGINX, and potentially reachable via Tor or I2P for those behind a NAT. It's a massive job, but the reality is that everything is already there, it just needs putting together.



Although, for completeness, the company in that case is actually Canadian.

(Always nice to see decade old effort still get referenced on occasion. :) )

Source: Username checks out. :D


And less than a decade later we have multiple devices that are effectively fitbits for your genitalia, for both sexes. How times change.


I would suggest weighing up other aspects: reinforced concrete was widely used under the assumption that it was eternal, or simply without considering how it would behave over time, and today a massive amount of infrastructure and buildings has simply reached the end of its lifespan. Whether the dense city appeals to those most terrified of change or to the few who need it to extract wealth from the many, it is incompatible with the New Deal. This is based on small, semi-autonomous buildings, resilient for that very reason, with sufficient local photovoltaics, energy and heat storage, and heat pumps which have the highest COPs over short distances. It involves designs with large south-facing glazed surfaces, featuring overhangs and blinds, so that the low winter sun penetrates effectively to provide free heating, while the high summer sun doesn't even touch the facade, all elements that are impossible to implement at scale in dense cities. Not to mention that we are very good at making simple things replicated in huge quantities, and much less so at large-scale, bespoke projects.

Whether you like it or not, the "ecological" city that is both dense and walkable DOES NOT EXIST, and there is no future in general for the current city, with its vast waterproofed surfaces where the soil has already turned to sand, eroded here and there by groundwater, causing the weight of large buildings to lead to slow and irreversible subsidence. Cities built in places where it made sense to be in the past, but makes no sense today.

Right now most people, even the bright ones, being victims of habit and propaganda, cannot bring themselves to admit it or understand it, but when they do, the collapse of urban real estate will have a far greater impact than the teleworking that is currently being denied at a high cost to everyone.


Do you have any thoughts about how to minimize the negative impact of such a massive shift?

I've been thinking that Federal limits on nominal appreciation of real estate could gently decrease real prices via inflation. And if that limit fluctuated like the Federal Reserve rate, it wouldn't completely crash real estate as an investment vehicle, meaning retirements needn't be completely decimated.

But that kind of intervention is just pie in the sky at least for the next few years.


In the current economic system, I don't see any. By changing this, for example, by eliminating bank intermediation in the creation of money, well, that could change things. Those who tried, like Lincoln with the Continentals, ended up getting killed...


Guidelines | FAQ | Lists | API | Security | DMCA | Apply to YC | Contact

Search: