One colleague at my last employer demanded to use the XMPP gateway and everyone hated it, because he constantly missed information, didn't get personal messages and didn't receive emoji reactions.
I'm glad the finally removed this.
Tell HN: Slack decides to close down IRC and XMPP gateways
411–420 of 624 posts
Re: Tell HN: Slack decides to close down IRC and XMPP gateways
#412Earlier quoted context omitted.
you seem to miss the point. 1) get US phone 2) register google voice to US phone 3) stop paying for US phone 4) you can't de-register you US phone, unless you register a new one 5a) if you never sign up for a US phone, anybody can get assigned that number and click "forgot password" on your google voice. 5b) you get a new US phone: go to 2. that is true for every single service that ties you up to a phone number or t…
Pay $20 and you get the number permanently. I've set up my kids' soccer club and my son's Cub Scout Pack with voicemail-only numbers. Callers leave a message and a recording and a transcription is forwarded to the appropriate person via email. I've also read using Google Voice is highly recommended for things that require a voice or text number since it's very difficult to get hold of someone at Google that can be so…
Where can I get a permanent (US) number anywhere?
The cheapest I've seen slightly below $2/month, but all the super cheap carriers are very volatile businesses and you can't expect to keep them more than a few years.
Seeing as you don't really own phone numbers in the sense you own domain names, any permanence is limited by the life span of your service provider.
Re: Tell HN: Slack decides to close down IRC and XMPP gateways
#413Earlier quoted context omitted.
> Here's a thought: how about you write a native app for each platform? I can guarantee that the hundreds, if not thousands, of engineers working on AppKit and Windows APIs are a lot better at getting this to work than your team. You're joking, right? Have you not noticed any of the pain that anybody trying to make cross-platform app goes through, and hence the huge popularity of cross-platform frameworks?
Just use Qt. It's harder, but not dramatically harder, than a web-based implementation.
[deleted]
Re: Tell HN: Slack decides to close down IRC and XMPP gateways
#414Earlier quoted context omitted.
One of my ex-colleague build one a while ago in less that a few days so I guess not that hard. But he is in the habit of making IRC gateway for everything he use
I'm interested. Do you have a link to his homepage/github profile/... ?
unfortunately he didn't publish the code
Re: Tell HN: Slack decides to close down IRC and XMPP gateways
#415Earlier quoted context omitted.
Email does many things, but "works great" isn't one of them. PGP even less.
I'm not sure why this is getting downvoted. I love email and I'm sure I'll be using it in the retirement home. But it is not very popular among the youth: https://techcrunch.com/2016/03/24/email-is-dying-among-mobil... And there's good reason for that. Email is basically the electronic equivalent of postal mail, a first pass at digital communication that aped the old medium. But the first email RFC was 35 years ago.…
I'm currently in a country where access to social network sites like facebook, instagramm & twitter is being blocked for two days due to political issues (Sri Lanka). One fellow travel (21yo) does not know how to reach out to any of his friends and family besides using facebook & whatsapp. Sadly, he didn't even think of using email to reach out, even though everyone has one. Can't blame him for not knowing about VPN and TOR. So, reality is that we're (still) living in times when a simple, reliable and independent service like email does have it's advantages and can be very useful from time to time, esp when travelling or when politics change.
Re: Tell HN: Slack decides to close down IRC and XMPP gateways
#416Earlier quoted context omitted.
They're not basically electron apps. they _are_ electron apps. And it's completely absurd that mine is currently using 1514MB of memory. If I weren't required to use Slack on a day-to-day basis, I absolutely wouldn't solely on principle.
Animated images and emoji can be disabled in the Accessibility settings. Spritesheets can be disabled under Advanced. Maybe it helps, sorry I have no before/after but my Slack is sitting at 300MB right now and I deal with an high number of very active channels.
Animated emojis can eat 100% CPU on my MacBook Pro if someone spams enough of them. It's insane how demanding and bloated the app is for what it does.
Re: Tell HN: Slack decides to close down IRC and XMPP gateways
#417Earlier quoted context omitted.
They're not basically electron apps. they _are_ electron apps. And it's completely absurd that mine is currently using 1514MB of memory. If I weren't required to use Slack on a day-to-day basis, I absolutely wouldn't solely on principle.
I just use emacs-slack[0]; my entire emacs usage is currently a fraction of yours. On X, this means emacs-slack displays images, emoji &c. just like the web or pseudo-native clients do. [0] https://github.com/yuya373/emacs-slack
Oh great, now every lazy developer is going to write their app on top of emacs and distribute a crappy Emactron version that uses almost eight megs of RAM.
But seriously, how hard would it be for a sneaky dev to make emacs with emacs-slack into a normal person application with clicky buttons and no ugly gnu? Could be worth a lot of money, or at least github stars.
Re: Tell HN: Slack decides to close down IRC and XMPP gateways
#418Earlier quoted context omitted.
> XMPP [...] is fragmented (not every client implements desired extensions), etc. How much I hate this "X is fragmented" argument. When two pieces of software that speak a common set of core protocols and thus can achieve at least some level of interoperability, but there is no perfect feature parity, then OH HORROR, IT IS FRAGMENTED!!1111 The obvious solution? Use a product that does not interoperate with absolutely…
"The obvious solution? Use a product that does not interoperate with absolutely anything at all ..." You mean use a product with a baseline feature set where you can count on all the clients seeing things the same way and supporting the same thing.
Yes, let's stop using Linux entirely. Everyone uses different versions, it's too fragmented and can not possibly be useful to anyone.
A proprietary platform where everyone the same product with identical feature set would easy out-compete it. It is apparent that the cloud is obviously betting on the wrong horse.
Re: Tell HN: Slack decides to close down IRC and XMPP gateways
#419Earlier quoted context omitted.
With the punctuation level set to all, the NVDA screen reader for Windows reads your code snippet like this: n s dictionary star my compounded word equals at left brace at left quote key colon [pause] left bracket n s number number with int colon [pause] 7 right brace right bracket semi It's a lot to absorb, but people do program productively this way. For example, the NVDA screen reader is itself developed primarily…
Interesting, how do blind developers feel about minimalist languages like lisp? On one hand it seems like it would read very well in some circumstances (+ 1 2), but the scoping could be a real pain. Cobol seems like another language that might be well suited to them.
Emacspeak[0] is one of the more popular voice oriented IDEs. I have yet to get it working, but I think you can do things like get it to read visual regions and sections between matching parens, etc. Ideally this is what I want to use, but it has resisted my efforts so far. Maybe I'll give it another try this weekend.
Re: Tell HN: Slack decides to close down IRC and XMPP gateways
#420Earlier quoted context omitted.
Moxie Marlinspike has a blog post about why protocols like XMPP aren't good enough to support modern messaging apps. https://signal.org/blog/the-ecosystem-is-moving/ XMPP is an example of a federated protocol that advertises itself as a “living standard.” Despite its capacity for protocol “extensions,” however, it’s undeniable that XMPP still largely resembles a synchronous protocol with limited support for rich medi…
Tangentially related, I have to take issue with this: > addressing with user-owned identifiers like phone numbers Phone numbers are owned by telecoms, not users. Sometimes they're transferable between telecoms, but not always. I, in particular travel internationally often and do not maintain phone service in the same country continuously. I've had to change phone numbers with Signal and Whatsapp a couple times now an…
> addressing with user-owned identifiers like phone numbers
Don't take things like that too seriously. That's just the result of the reality distortion field that comes with sitting on top a huge database of phone numbers.