Updates tagged with wire on Jonkman Microblog!
lnxw48a1: My mom and most of my siblings do videochats over #Zoom. One brother does not understand such technology, and I don't use Zoom except when work requires it. I use #Jitsi_Meet, or for just two endpoints, I use #Wire.
lnxw48a1's status on Saturday, 09-Sep-2023 13:04:15 EDT
My mom and most of my siblings do videochats over #Zoom. One brother does not understand such technology, and I don't use Zoom except when work requires it. I use #Jitsi_Meet, or for just two endpoints, I use #Wire.
lnxw48a1: #Session vying to be replacement for #Wickr https://getsession.org/blog/the-perfect-replacement-for-wickr I still use !xmpp and #Wire
lnxw48a1's status on Monday, 20-Feb-2023 00:54:40 EST
#Session vying to be replacement for #Wickr https://getsession.org/blog/the-perfect-replacement-for-wickr I still use !xmpp and #Wire
Why Session is the Perfect Replacement for Wickr - Session Private Messenger
lnxw48a1: Internet Messaging ( #IM ) over congested networks https://blog.lewman.com/internet-messaging-versus-congested-network.html !xmpp !xmpp #Matrix #Briar #Wire #Discord
lnxw48a1's status on Saturday, 19-Feb-2022 23:20:53 EST
Internet Messaging ( #IM ) over congested networks https://blog.lewman.com/internet-messaging-versus-congested-network.html !xmpp !xmpp #Matrix #Briar #Wire #Discord
Internet Messaging versus Congested Network
lnxw48a1: Got a message from #Daddy_A on #Wire: > Did #sonTwo tell you ... No, but even if he had, I'd probably rather hear it from you.
lnxw48a1's status on Tuesday, 24-Aug-2021 22:18:16 EDT
Got a message from #Daddy_A on #Wire: > Did #sonTwo tell you ... No, but even if he had, I'd probably rather hear it from you.
lnxw48a1: Every now and then, I'll send one of the kids a message on #Wire, then look at the clock and realize it is 01:00 where they live. Oops! (It also happens with SMS, but we don't send so many of those any more.)
lnxw48a1's status on Wednesday, 30-Jun-2021 02:28:26 EDT
Every now and then, I'll send one of the kids a message on #Wire, then look at the clock and realize it is 01:00 where they live. Oops! (It also happens with SMS, but we don't send so many of those any more.)
lnxw48a1: Also got a Fathers' Day message from #sonOne on #Wire ... including a continuation of our discussion about trying to get #GS1 and #GS2 some vocational training. They moved out, so he cannot just enroll them at the local job training center.
lnxw48a1's status on Sunday, 20-Jun-2021 16:46:44 EDT
Also got a Fathers' Day message from #sonOne on #Wire ... including a continuation of our discussion about trying to get #GS1 and #GS2 some vocational training. They moved out, so he cannot just enroll them at the local job training center.
lnxw48a1: Last night, over #Wire, #Daddy_A and I were discussing #cryptocurrency again. I compared DOGEcoin's rising and falling based on Elon Musk's tweets to the penny stock "pink sheets" ... except that Mr Musk is probably smart enough to only have minimal exposure to the rollercoaster price movements his tweets are causing. Of course, I also compared his tweeting to that of a well-known former politician. Both have tweeted things which should never be said publicly, if at all.
lnxw48a1's status on Friday, 14-May-2021 15:21:24 EDT
Last night, over #Wire, #Daddy_A and I were discussing #cryptocurrency again. I compared DOGEcoin's rising and falling based on Elon Musk's tweets to the penny stock "pink sheets" ... except that Mr Musk is probably smart enough to only have minimal exposure to the rollercoaster price movements his tweets are causing. Of course, I also compared his tweeting to that of a well-known former politician. Both have tweeted things which should never be said publicly, if at all.
lnxw48a1: Did you see “this series of articles”:{https://www.copetti.org/writings/consoles/} about the hardware inside of game consoles? I think @bthall sent me the link on #Wire.
lnxw48a1's status on Monday, 10-May-2021 12:01:22 EDT
Did you see “this series of articles”:{https://www.copetti.org/writings/consoles/} about the hardware inside of game consoles? I think @bthall sent me the link on #Wire.
Architecture of Consoles | A Practical Analysis
lnxw48a1: Had a conversation with #Daddy_A over #Wire ... basically a text chat ... about the areas he’d driving through. Some large-ish cities in Great Lakes states. The way that much of what is visible from the highway are just skeletons of industry that is long gone. The importance of getting to the #hotel early, before dark, and not leaving anything in the car. In all of this, I’m hearing a thoughtful, contemplative person who has finally found his voice. He’s using words longer than five letters long, spelled correctly, with proper punctuation and discussing concepts that I’m only aware of because of some of the courses I took in college. (I guess some of those discussions about what I was studying sunk in. I did not know he was paying attention.)
lnxw48a1's status on Sunday, 18-Apr-2021 23:45:53 EDT
Had a conversation with #Daddy_A over #Wire ... basically a text chat ... about the areas he’d driving through. Some large-ish cities in Great Lakes states. The way that much of what is visible from the highway are just skeletons of industry that is long gone. The importance of getting to the #hotel early, before dark, and not leaving anything in the car. In all of this, I’m hearing a thoughtful, contemplative person who has finally found his voice. He’s using words longer than five letters long, spelled correctly, with proper punctuation and discussing concepts that I’m only aware of because of some of the courses I took in college. (I guess some of those discussions about what I was studying sunk in. I did not know he was paying attention.)
lnxw48a1: Today's #videochat happened just before #GS3's #naptime, so I got to see him try to stick the broom into the heater. He talked to me and then showed me his new toy. (I didn't understand a bit of it, so I don't know if it was English or Martian.) Great day. We had a few connection issues at the beginning of the call, but #Wire is still the most reliable tool we've used.
lnxw48a1's status on Saturday, 19-Dec-2020 15:32:52 EST
Today's #videochat happened just before #GS3's #naptime, so I got to see him try to stick the broom into the heater. He talked to me and then showed me his new toy. (I didn't understand a bit of it, so I don't know if it was English or Martian.) Great day. We had a few connection issues at the beginning of the call, but #Wire is still the most reliable tool we've used.
lnxw48a1: @geniusmusing @guizzy Shared the link with the kids. It sparked a conversation ( on #Wire ) about which old games we remember. Surprisingly, the youngest ( #Daddy_A ) remembers more games than the older kids.
lnxw48a1's status on Sunday, 15-Nov-2020 14:01:35 EST
@geniusmusing @guizzy Shared the link with the kids. It sparked a conversation ( on #Wire ) about which old games we remember. Surprisingly, the youngest ( #Daddy_A ) remembers more games than the older kids.
lnxw48a1: Was able to #videochat with #sonOne, #GD1, #GD2 for about an hour and a half today on #Wire. He's been working 16 hours a day since June, but he got a week of vacation. It possibly means that he'll be unavailable again in a week, but I'll try to do #videochats with the kids. Was informed that #GD1 lost her phone. #GS1 likewise lost his phone, but found it and sent it to sonOne because it wasn't accepting a charge. Daughter-in-law will make the six hour round trip to deliver the now-working phone to her son. (Asked because both of them suddenly stopped responding to SMS.)
lnxw48a1's status on Sunday, 18-Oct-2020 19:11:44 EDT
Was able to #videochat with #sonOne, #GD1, #GD2 for about an hour and a half today on #Wire. He's been working 16 hours a day since June, but he got a week of vacation. It possibly means that he'll be unavailable again in a week, but I'll try to do #videochats with the kids. Was informed that #GD1 lost her phone. #GS1 likewise lost his phone, but found it and sent it to sonOne because it wasn't accepting a charge. Daughter-in-law will make the six hour round trip to deliver the now-working phone to her son. (Asked because both of them suddenly stopped responding to SMS.)
lnxw48a1: Okay look. *I* don't use #Signal ( and same for #Telegram ), because I don't want to give my telephone number to anyone except family and close friends. I have enough personal contacts that do use them so that they'd be personally useful if I didn't have that unbreakable obstacle. But I don't object to others choosing such end-to-end encrypted messengers over messaging apps such as (for example) #Facebook_Messenger. I personally use #Wire, #XMPP, #Matrix, and #WickrMe. (I tried #Jami, but it wasn't very usable yet; none of my contacts were willing to try #Tox or #Briar.) I've even considered getting a Google account again so I can use whatever their latest incarnation of messaging is (just because almost everyone I know has a Google account). It does bother me that Signal and Telegram and most other messaging services are centralized and non-federated. It seems we haven't learned from the 1990s & early 2000s when some friends had AOL Instant Messenger (AIM), some had MSN Messenger, some had Yahoo Messenger, some had ICQ, and a few had various other walled garden messengers (such as Excite's messenger). If I wanted to talk with all my friends, I needed to have accounts on every possible service. I should be able to communicate with my friends from whatever service I choose to use to whatever services they choose to use and not have to create accounts on every possible service. But that's a matter of educating our friends and family, not of dogmatically refusing to communicate with them on any service they might use.
lnxw48a1's status on Sunday, 04-Oct-2020 20:33:27 EDT
Okay look. *I* don't use #Signal ( and same for #Telegram ), because I don't want to give my telephone number to anyone except family and close friends. I have enough personal contacts that do use them so that they'd be personally useful if I didn't have that unbreakable obstacle. But I don't object to others choosing such end-to-end encrypted messengers over messaging apps such as (for example) #Facebook_Messenger. I personally use #Wire, #XMPP, #Matrix, and #WickrMe. (I tried #Jami, but it wasn't very usable yet; none of my contacts were willing to try #Tox or #Briar.) I've even considered getting a Google account again so I can use whatever their latest incarnation of messaging is (just because almost everyone I know has a Google account). It does bother me that Signal and Telegram and most other messaging services are centralized and non-federated. It seems we haven't learned from the 1990s & early 2000s when some friends had AOL Instant Messenger (AIM), some had MSN Messenger, some had Yahoo Messenger, some had ICQ, and a few had various other walled garden messengers (such as Excite's messenger). If I wanted to talk with all my friends, I needed to have accounts on every possible service. I should be able to communicate with my friends from whatever service I choose to use to whatever services they choose to use and not have to create accounts on every possible service. But that's a matter of educating our friends and family, not of dogmatically refusing to communicate with them on any service they might use.
lnxw48a1: @amic@nulled.red’s asked me to try #Telegram because their phone isn’t working with #Wire. Unfortunately, TG, like #Signal, requires my telephone number, so both of those are not acceptable. (Leaving aside any questions about Telegram’s ownership, integrity, financing, and encryption.)
lnxw48a1's status on Saturday, 26-Sep-2020 16:32:28 EDT
@amic@nulled.red’s asked me to try #Telegram because their phone isn’t working with #Wire. Unfortunately, TG, like #Signal, requires my telephone number, so both of those are not acceptable. (Leaving aside any questions about Telegram’s ownership, integrity, financing, and encryption.)
lnxw48a1: Tried to call #sonOne on #Wire, so we can resume the weekly #videochat, but he's been working around sixteen hours per day since June, so that was again unsuccessful.
lnxw48a1's status on Sunday, 20-Sep-2020 17:13:07 EDT
Tried to call #sonOne on #Wire, so we can resume the weekly #videochat, but he's been working around sixteen hours per day since June, so that was again unsuccessful.
lnxw48a1: Tried to call #sonOne on #Wire for our regular, weekly #videochat, but no answer.
lnxw48a1's status on Sunday, 05-Jul-2020 18:26:45 EDT
Tried to call #sonOne on #Wire for our regular, weekly #videochat, but no answer.
lnxw48a1: Got away with calling #Daddy_A by his childhood nickname in #Wire. Usually he sends a grimacing face icon in reply, but this time he did not.
lnxw48a1's status on Friday, 15-May-2020 21:43:58 EDT
Got away with calling #Daddy_A by his childhood nickname in #Wire. Usually he sends a grimacing face icon in reply, but this time he did not.
strypey: @jamesmullarkey > Signal only ever asks you for your phone number ... which in most cases would allows any compromised account to be traced back to a human user. Signal claim they need your cell number to prevent spam, which is garbage, since both Wire and Riot provide encrypted chat without asking for one, and don't have noticable spam problems.#Signal #Wire #Riot
strypey's status on Friday, 24-Apr-2020 07:11:58 EDT
@jamesmullarkey > Signal only ever asks you for your phone number ... which in most cases would allows any compromised account to be traced back to a human user. Signal claim they need your cell number to prevent spam, which is garbage, since both Wire and Riot provide encrypted chat without asking for one, and don't have noticable spam problems. #Signal #Wire #Riot
lnxw48a1: We had our first family #videochat last evening on #Jitsi_Meet. There were some occasional quality issues ... possibly because three of us were connecting from different rooms here. Added to whatever game #lazyNephew was playing, it may have saturated the connection. My oldest brother was unable to connect, but no one has followed up to try to figure out why. His granddaughter is his usual tech support, but she cannot go over right now. . Going to try this with my kids and grandkids, if we can ever schedule it, but we may continue our use of #Wire. I think the video and audio quality is better ... but we've only used 1:1 so far.
lnxw48a1's status on Sunday, 19-Apr-2020 11:24:17 EDT
We had our first family #videochat last evening on #Jitsi_Meet. There were some occasional quality issues ... possibly because three of us were connecting from different rooms here. Added to whatever game #lazyNephew was playing, it may have saturated the connection. My oldest brother was unable to connect, but no one has followed up to try to figure out why. His granddaughter is his usual tech support, but she cannot go over right now. . Going to try this with my kids and grandkids, if we can ever schedule it, but we may continue our use of #Wire. I think the video and audio quality is better ... but we've only used 1:1 so far.
lnxw48a1: Still trying to get #sonTwo and #Daddy_A together to test multipoint videochat and audiochat on #Wire, #Jitsi_Meet, #Nextcloud_Talk (whenever I get that one set up). So far, I have one-to-one chats with sonTwo plus his wife and #GS3 almost daily; one-to-one chats with #sonOne plus #GD1 and #GD2 (wife usually appears briefly) every week, and one-to-one chats with Daddy A plus wife, #Little_Boy_A, #Little_Boy_A2, #Little_Girl_A3 about 1-2 times per year.
lnxw48a1's status on Monday, 06-Apr-2020 19:46:15 EDT
Still trying to get #sonTwo and #Daddy_A together to test multipoint videochat and audiochat on #Wire, #Jitsi_Meet, #Nextcloud_Talk (whenever I get that one set up). So far, I have one-to-one chats with sonTwo plus his wife and #GS3 almost daily; one-to-one chats with #sonOne plus #GD1 and #GD2 (wife usually appears briefly) every week, and one-to-one chats with Daddy A plus wife, #Little_Boy_A, #Little_Boy_A2, #Little_Girl_A3 about 1-2 times per year.
lnxw48a1: Waiting to hear whether we're going to try another multipoint videochat tomorrow. I invited #sonTwo and #Daddy_A (tomorrow's plan is #Wire and #JitsiMeet ... I still have not set up #Nextcloud Talk, which is also on our list). #sonOne is currently working 6-10s, so I didn't invite him.
lnxw48a1's status on Friday, 03-Apr-2020 19:43:03 EDT
Waiting to hear whether we're going to try another multipoint videochat tomorrow. I invited #sonTwo and #Daddy_A (tomorrow's plan is #Wire and #JitsiMeet ... I still have not set up #Nextcloud Talk, which is also on our list). #sonOne is currently working 6-10s, so I didn't invite him.
lnxw48a1: Sent this to @bthall via #Wire ... he's younger than my kids, so he might not know about those days.
lnxw48a1's status on Monday, 02-Mar-2020 19:16:02 EST
Sent this to @bthall via #Wire ... he's younger than my kids, so he might not know about those days.
lnxw48a1: @strypey So there's a lot to unpack in that document. The #Session onion routing protocol involves using a #blockchain called #Loki to make it difficult for an adversary to control a significant fraction of the nodes and prevent exposing the IP addresses (and therefore identities) of a user and his/her contacts to the same person or group. (As you noticed, Session is not yet using onion requests.) There's also swarms and attachments and message storage (including attachments), online vs offline messages, multiple device support, spam resistance, a modified version of #Signal's encryption protocol, group chats (3-500 member "closed" groups are end-to-end encrypted like the rest of Session; "open" groups are not, and require an account on a special group server [self-hostable]) Note that all this stuff happens under the covers. It seems that Session will handle most of it without the user ever seeing it. I'm going to query some family members and see whether any would be willing to try this as a secondary channel (for now #Wire is our primary channel). Just adding offline messages is a clear advantage over #Jami, but the lack of audio & video chats is going to limit its usefulness.
lnxw48a1's status on Saturday, 15-Feb-2020 12:47:40 EST
@strypey So there's a lot to unpack in that document. The #Session onion routing protocol involves using a #blockchain called #Loki to make it difficult for an adversary to control a significant fraction of the nodes and prevent exposing the IP addresses (and therefore identities) of a user and his/her contacts to the same person or group. (As you noticed, Session is not yet using onion requests.) There's also swarms and attachments and message storage (including attachments), online vs offline messages, multiple device support, spam resistance, a modified version of #Signal's encryption protocol, group chats (3-500 member "closed" groups are end-to-end encrypted like the rest of Session; "open" groups are not, and require an account on a special group server [self-hostable]) Note that all this stuff happens under the covers. It seems that Session will handle most of it without the user ever seeing it. I'm going to query some family members and see whether any would be willing to try this as a secondary channel (for now #Wire is our primary channel). Just adding offline messages is a clear advantage over #Jami, but the lack of audio & video chats is going to limit its usefulness.
lnxw48a1: Despite being invited to ride along on store trips in the early evening, I almost always decline. I want to be available on #Wire for a videochat with #GS-3
lnxw48a1's status on Tuesday, 11-Feb-2020 21:03:00 EST
Despite being invited to ride along on store trips in the early evening, I almost always decline. I want to be available on #Wire for a videochat with #GS-3
strypey: Whatever AP devs do, determined BadActors can easily circumvent blocks by going to the web page of your feed. What people looking for private discussion spaces need is something like #jabber #MUCs, or #Matrix rooms, or #Wire group chats, or #Crabgrass groups, or private Discourse instances, or any one of dozens of other free code tools that exist for private group discussions. But no, they demand we turn the fediverse into those to suit their use case. #EntitledAsFuck
strypey's status on Sunday, 15-Dec-2019 05:13:49 EST
Whatever AP devs do, determined BadActors can easily circumvent blocks by going to the web page of your feed. What people looking for private discussion spaces need is something like #jabber #MUCs, or #Matrix rooms, or #Wire group chats, or #Crabgrass groups, or private Discourse instances, or any one of dozens of other free code tools that exist for private group discussions. But no, they demand we turn the fediverse into those to suit their use case. #EntitledAsFuck
lnxw37d2: @dwc @oldvetcodes @AvnSgt Your best option will be a tool that your contacts are willing to use. Most of the "worth mentioning" things at https://www.privacytools.io/software/real-time-communication/ have already been rejected by my contacts, so right now, it is pretty much #Wire or nothing (I'm not joining #Facebook).
lnxw37d2's status on Wednesday, 20-Nov-2019 18:13:59 EST
@dwc @oldvetcodes @AvnSgt Your best option will be a tool that your contacts are willing to use. Most of the "worth mentioning" things at https://www.privacytools.io/software/real-time-communication/ have already been rejected by my contacts, so right now, it is pretty much #Wire or nothing (I'm not joining #Facebook).
lnxw37d2: @AvnSgt @oldvetcodes Thanks. This is a tough one. #Wire is the first and only privacy-centric tool that is in widespread use among my friends and family. Several of them tried #Ring (now #Jami) before that, but it was a bad experience all around and cries of "it got better" won't get anyone to try it.
lnxw37d2's status on Wednesday, 20-Nov-2019 15:07:42 EST
@AvnSgt @oldvetcodes Thanks. This is a tough one. #Wire is the first and only privacy-centric tool that is in widespread use among my friends and family. Several of them tried #Ring (now #Jami) before that, but it was a bad experience all around and cries of "it got better" won't get anyone to try it.
lnxw48a1: #GD2 (age 8) must have had trouble getting up for school. She used to send me messages on #Wire as late as 21:00 US-Central. Now, she sends her good night message promptly at 19:00 +/- 5 minutes.
lnxw48a1's status on Sunday, 03-Nov-2019 20:13:09 EST
#GD2 (age 8) must have had trouble getting up for school. She used to send me messages on #Wire as late as 21:00 US-Central. Now, she sends her good night message promptly at 19:00 +/- 5 minutes.
strypey: Here's a report on our third #VOICE testing session on Satuday, where we intended to test group voice chat on #Tox, but ended up having more success with #Wire: https://write.as/yt03jv11742w2.mdOur next session is scheduled for Sunday 2 November, starting at 12:00 UTC. We currently coordinate testing at: #voicechat:matrix.org
strypey's status on Monday, 21-Oct-2019 09:23:55 EDT
Here's a report on our third #VOICE testing session on Satuday, where we intended to test group voice chat on #Tox, but ended up having more success with #Wire: https://write.as/yt03jv11742w2.md Our next session is scheduled for Sunday 2 November, starting at 12:00 UTC. We currently coordinate testing at: #voicechat:matrix.org
strypey: @nurinoas that last one I think is key, because adoption is strongly shaped by #NetworkEffect Imagine if users of every #Jabber app, every #Matrix app, every standalone chat app like #Wire or #Signal, could chat with Jami users! Even #fediverse apps for that matter! @teaneedz @AmarOk
strypey's status on Saturday, 13-Jul-2019 04:04:06 EDT
@nurinoas that last one I think is key, because adoption is strongly shaped by #NetworkEffect Imagine if users of every #Jabber app, every #Matrix app, every standalone chat app like #Wire or #Signal, could chat with Jami users! Even #fediverse apps for that matter! @teaneedz @AmarOk
strypey: Having said all that, I just remembered proposing pretty much the same thing some time back, including a reference to #Forget. I was inspired by the self-destructing messages in #Wire, and thinking it could be a good way to reduce the storage needs of the fediverse, as well as increase the signal-to-noise ratio of its archives. https://mastodon.nzoss.nz/@strypey/101212607635047102 @rtwx @wion @jessmahler
strypey's status on Wednesday, 10-Jul-2019 08:07:19 EDT
Having said all that, I just remembered proposing pretty much the same thing some time back, including a reference to #Forget. I was inspired by the self-destructing messages in #Wire, and thinking it could be a good way to reduce the storage needs of the fediverse, as well as increase the signal-to-noise ratio of its archives. https://mastodon.nzoss.nz/@strypey/101212607635047102 @rtwx @wion @jessmahler
lnxw48a1: @amic Just got in and opened #Wire.
lnxw48a1's status on Friday, 07-Jun-2019 22:19:05 EDT
@amic Just got in and opened #Wire.
lnxw48a1: I talked to my “no answer” kid ( #Daddy_A ) for a few minutes recently because of birthdays. It was good, but uncomfortable. I ended it pretty quickly. Our last actual phone call before now was Christmas of 2017. (But we do communicate over #Wire regularly and sometimes via #SMS.)
lnxw48a1's status on Wednesday, 15-May-2019 21:57:21 EDT
I talked to my “no answer” kid ( #Daddy_A ) for a few minutes recently because of birthdays. It was good, but uncomfortable. I ended it pretty quickly. Our last actual phone call before now was Christmas of 2017. (But we do communicate over #Wire regularly and sometimes via #SMS.)
forteller: Hey, you know how #Wire has been promising for a long time to allow federation? Looks like they're working on it!In the latest changelog you can read: "The Android Wire client can now be run against a private server."Cool beans!
forteller's status on Monday, 06-May-2019 11:30:47 EDT
Hey, you know how #Wire has been promising for a long time to allow federation? Looks like they're working on it! In the latest changelog you can read: "The Android Wire client can now be run against a private server." Cool beans!
strypey: @rysiek hasn't #Signal demanded people not connect third-party clients to their servers? In fact, any binaries not distributed by them (they refuse to let #FDroid distribute their app). These are only two of many reasons not to support Signal with your unpaid time: https://github.com/privacytoolsIO/privacytools.io/issues/779I'd recommend working on a native #SailFish client for #Wire instead. They are a) already close to feature parity with Signal b) actively working towards server>server federation: https://github.com/wireapp/wire-server/issues/631
strypey's status on Monday, 22-Apr-2019 14:43:37 EDT
@rysiek hasn't #Signal demanded people not connect third-party clients to their servers? In fact, any binaries not distributed by them (they refuse to let #FDroid distribute their app). These are only two of many reasons not to support Signal with your unpaid time: https://github.com/privacytoolsIO/privacytools.io/issues/779 I'd recommend working on a native #SailFish client for #Wire instead. They are a) already close to feature parity with Signal b) actively working towards server>server federation: https://github.com/wireapp/wire-server/issues/631
Implement XMPP federation · Issue #631 · wireapp/wire-server
404city: Added #DNSSEC record for https://404.city #xmpp #jabber decetralized alternative #wire #signal #telegram #threema #whatsapp
404city's status on Friday, 19-Apr-2019 13:00:45 EDT
Added #DNSSEC record for https://404.city #xmpp #jabber decetralized alternative #wire #signal #telegram #threema #whatsapp
lnxw48a1: @rw A few family members complain that I can’t see their calendar events, but the biggest annoyance I have with not being a #Facebook user is all the people that say “did you see what cousin so and so just said?” and then stick their phones in my face. If I wanted to see all that random garbage, I would still have an account. Yes, but how can we get in touch with you? Let me count the ways: * call * text * !XMPP * #Wire * #Ring / #Jami * e-mail * in person * contact any of my sons, nephews, siblings, my youngest niece, the cousin that lives in TX, or my mom and ask them to forward
lnxw48a1's status on Thursday, 11-Apr-2019 14:45:55 EDT
@rw A few family members complain that I can’t see their calendar events, but the biggest annoyance I have with not being a #Facebook user is all the people that say “did you see what cousin so and so just said?” and then stick their phones in my face. If I wanted to see all that random garbage, I would still have an account. Yes, but how can we get in touch with you? Let me count the ways: * call * text * !XMPP * #Wire * #Ring / #Jami * e-mail * in person * contact any of my sons, nephews, siblings, my youngest niece, the cousin that lives in TX, or my mom and ask them to forward
lnxw48a1: Because we were both doing maintenance around the house, #sonTwo and I split our call into three. I messsed up and put the part in backwards, so I'll have to redo my task. Family day at Home Depot, I guess. #sonOne was at work, so we had no phone call this week. #Daddy_A and I chatted on #Wire at the same time as Mark and I were conversing via SMS. Finally, co-worker S called and we were on the phone about two hours and forty minutes (talking about $EMPLOYER and life after $EMPLOYER). Full day. I'm going to go to bed now. #TZAF
lnxw48a1's status on Monday, 08-Apr-2019 02:22:41 EDT
Because we were both doing maintenance around the house, #sonTwo and I split our call into three. I messsed up and put the part in backwards, so I'll have to redo my task. Family day at Home Depot, I guess. #sonOne was at work, so we had no phone call this week. #Daddy_A and I chatted on #Wire at the same time as Mark and I were conversing via SMS. Finally, co-worker S called and we were on the phone about two hours and forty minutes (talking about $EMPLOYER and life after $EMPLOYER). Full day. I'm going to go to bed now. #TZAF
bobjonkman: That conversation would have been at least a year ago, and probably on #Wire -- my main laptop with all the comm clients on it has been relegated to to the basement to be a server (dead screen), and my currently laptop lacks the oomph to do things like #Ring / #Jami / #Wire
bobjonkman's status on Tuesday, 02-Apr-2019 17:02:57 EDT
That conversation would have been at least a year ago, and probably on #Wire -- my main laptop with all the comm clients on it has been relegated to to the basement to be a server (dead screen), and my currently laptop lacks the oomph to do things like #Ring / #Jami / #Wire
lnxw48a1: Good morning. I’ve already had my daily #YoCo ( #yogurt / #yoghurt and #coffee ), navigated around a online forum conflict, had a couple of personal conversations over #Wire and #XMPP, been greeted by an excited three year old (sister’s granddaughter), and tuned in to @sir’s coding stream. #TZAG
lnxw48a1's status on Friday, 29-Mar-2019 12:58:31 EDT
Good morning. I’ve already had my daily #YoCo ( #yogurt / #yoghurt and #coffee ), navigated around a online forum conflict, had a couple of personal conversations over #Wire and #XMPP, been greeted by an excited three year old (sister’s granddaughter), and tuned in to @sir’s coding stream. #TZAG
strypey: The #Wire team are open to the idea of using #XMPP for federation between instances of the Wire server: "Please feel free to use this issue to post links / papers / reading material of any kind that might help us make a more informed decision" https://github.com/wireapp/wire-server/issues/631
strypey's status on Wednesday, 27-Mar-2019 02:27:56 EDT
The #Wire team are open to the idea of using #XMPP for federation between instances of the Wire server: "Please feel free to use this issue to post links / papers / reading material of any kind that might help us make a more informed decision" https://github.com/wireapp/wire-server/issues/631
strypey: @kfwyre I've been using #Wire on and off for a while. I had to stop using the Wire desktop client when #Electron (which it depends on) stopped supporting 32-bit. When I log on using the web app, on the same device, logged in as the same user, I get all my chat history just fine.
strypey's status on Wednesday, 27-Mar-2019 02:18:30 EDT
@kfwyre I've been using #Wire on and off for a while. I had to stop using the Wire desktop client when #Electron (which it depends on) stopped supporting 32-bit. When I log on using the web app, on the same device, logged in as the same user, I get all my chat history just fine.
strypey: @wire perhaps I'm getting confused between #Signal, #Telegram, and #Wire. From what I remember, Moxie liberated the Signal client source before setting up #OWS, but resisted releasing the server source for some time, claiming there was no point. Just as he still claims there's no point replacing Google Play Services in mainstream Signal, or distributing the Android client in #FDroid, or supporting #federation between servers. Some people discussing this in 2016: https://whispersystems.riseup.narkive.com/LvP523Tg/signal-server-source-code @alexl
strypey's status on Tuesday, 19-Mar-2019 09:34:15 EDT
@wire perhaps I'm getting confused between #Signal, #Telegram, and #Wire. From what I remember, Moxie liberated the Signal client source before setting up #OWS, but resisted releasing the server source for some time, claiming there was no point. Just as he still claims there's no point replacing Google Play Services in mainstream Signal, or distributing the Android client in #FDroid, or supporting #federation between servers. Some people discussing this in 2016: https://whispersystems.riseup.narkive.com/LvP523Tg/signal-server-source-code @alexl
strypey: #Wire also confirmed that while the company is focused on supporting their existing web client and the desktop clients using the #Electron wrapper, they welcome the #SoftwareFreedom community to help develop alternative clients to be used with their service, like #Coax (currently in alpha): https://github.com/wireapp/wire/issues/266#issuecomment-473873942
strypey's status on Tuesday, 19-Mar-2019 08:44:06 EDT
#Wire also confirmed that while the company is focused on supporting their existing web client and the desktop clients using the #Electron wrapper, they welcome the #SoftwareFreedom community to help develop alternative clients to be used with their service, like #Coax (currently in alpha): https://github.com/wireapp/wire/issues/266#issuecomment-473873942
Wire servers can't federate with each other · Issue #266 · wireapp/wire
strypey: ... and in #GoodNews, #Wire not only confirms they're working on secure, federated chat, but #federation will be part of the #MLS protocol being standardized at the #IETF : "During this interim the proposal was made to include federation more strongly in the design considerations and the proposal was adopted as a future goal for MLS. Wire's goal has always been to achieve federation between different compatible backends and this brings us one step closer to that goal!" https://wire.com/en/blog/mls-meeting-summary/
strypey's status on Tuesday, 19-Mar-2019 08:40:22 EDT
... and in #GoodNews, #Wire not only confirms they're working on secure, federated chat, but #federation will be part of the #MLS protocol being standardized at the #IETF : "During this interim the proposal was made to include federation more strongly in the design considerations and the proposal was adopted as a future goal for MLS. Wire's goal has always been to achieve federation between different compatible backends and this brings us one step closer to that goal!" https://wire.com/en/blog/mls-meeting-summary/
Summary of the second Messaging Layer Security (MLS) interim meeting · Wire
strypey: I've reported #Wire's lack of server>server federation as an issue, and explained how it could benefit them as a company. I mentioned that there might be hackers out there willing to help them make it happen. Let's see what they say: https://github.com/wireapp/wire/issues/266
strypey's status on Monday, 18-Mar-2019 02:14:51 EDT
I've reported #Wire's lack of server>server federation as an issue, and explained how it could benefit them as a company. I mentioned that there might be hackers out there willing to help them make it happen. Let's see what they say: https://github.com/wireapp/wire/issues/266
strypey: @alexl BTW all chats and calls on #Wire are #E2E by default, and they do not use roll-your-own crypto@tao
strypey's status on Friday, 08-Mar-2019 07:47:52 EST
@alexl BTW all chats and calls on #Wire are #E2E by default, and they do not use roll-your-own crypto @tao
strypey: Because of #Electron abandoning support for 32-bit PCs, this bug in #Wire is unlikely to be fixed, and I may have to give up on trying to use the Wire desktop client on my 32-bit laptop: https://github.com/wireapp/wire-desktop/issues/2038
strypey's status on Wednesday, 06-Mar-2019 10:37:56 EST
Because of #Electron abandoning support for 32-bit PCs, this bug in #Wire is unlikely to be fixed, and I may have to give up on trying to use the Wire desktop client on my 32-bit laptop: https://github.com/wireapp/wire-desktop/issues/2038
i386 build for Debian depends on wrong version GLIBC_2.27 instead of GLIBC_2.24 · Issue #2038 · wireapp/wire-desktop