On June 20, 2026 6:05:21 PM GMT+01:00, [email protected] wrote:
>June 20, 2026 at 12:14 PM, "Bradley Morgan" <[email protected]
>mailto:[email protected]?to=%22Bradley%20Morgan%22%20%3Cinclude%40grrlz.net%3E
>> wrote:
>
>
>
>> 
>> On 20 June 2026 17:05:02 BST, [email protected] wrote:
>> 
>> > 
>> > June 20, 2026 at 4:58 AM, "Bradley Morgan" <[email protected]
>> >
>mailto:[email protected]?to=%22Bradley%20Morgan%22%20%3Cinclude%40grrlz.net%3E
>> > 
>> > > 
>> > > wrote:
>> > > 
>> > >  
>> > >  On June 20, 2026 1:11:13 AM GMT+01:00, [email protected] wrote:
>> > >  
>> > >  > 
>> > >  > June 19, 2026 at 6:05 PM, "Bradley Morgan" <[email protected]
>> > >  >
>> > > 
>> >
>mailto:[email protected]?to=%22Bradley%20Morgan%22%20%3Cinclude%40grrlz.net%3E
>> > 
>> > > 
>> > > > 
>> > >  > > 
>> > >  > > wrote:
>> > >  > > 
>> > >  > > 
>> > >  > > On June 19, 2026 11:02:03 PM GMT+01:00, Paulo Duarte
>> > >  > > <[email protected]> wrote:
>> > >  > > 
>> > >  > > > 
>> > >  > > > > 
>> > >  > > > > On 19 Jun 2026, at 22:50, Bradley Morgan
><[email protected]>
>> > > 
>> > wrote:
>> > 
>> > > 
>> > > > > > > 
>> > >  > > > > Good that sergey did it (atleast some) :)
>> > >  > > > > 
>> > >  > > > He did 95% of the work.
>> > >  > > > 
>> > >  > > Oh. Well, could we make some sort of telegram group? Or are you
>> > > 
>> > folks
>> > 
>> > > 
>> > > > > 
>> > >  > not
>> > >  > 
>> > >  > > 
>> > >  > > into telegram.. :(
>> > >  > > 
>> > >  > I would imagine that most people are not into that in the Hurd
>group,
>> > > 
>> > but
>> > 
>> > > 
>> > > > some
>> > >  > might be ok with it. I personally don't like that it is routed on
>a
>> > >  > central
>> > >  > server...
>> > >  > 
>> > >  > There is always #hurd irc channel.
>> > >  > 
>> > >  > XMPP (jabber) supports public rooms (maybe private ones).
>JMP.chat
>> > >  > 
>> > >  > Mumble voice chat would be an option.
>> > >  > 
>> > >  > I am a member of the FSF, and they support jitsi chatrooms (audio
>/
>> > >  > video).
>> > >  > 
>> > >  Sorry to be so nitpicky here, but I don't like the UI on irc (on
>mobile)
>> > >  I prefer to do my informal chats and stuff on mobile.
>> > >  
>> > >  Telegram has a Amazing UI tbh, and it's more privacy focused then
>e.g:
>> > >  discord 
>> > >  
>> > >  I'm suggesting it because then I can chat where I pretty much
>always
>> > > 
>> > talk
>> > 
>> > > 
>> > > to people, I mean, I have mastodon too.
>> > > 
>> > No need to apologize. You are not nickpicking. You are just describing
>> > what
>> > you want. :)
>> > 
>> > I believe that matrix is a more libre option for the Hurd, and they do
>> > have mobile
>> > clients. Riot is one. Maybe next week I'll re-set up my matrix
>client...
>> > 
>> > Unless, I can set up dino-im to bridge to matrix...should be possible.
>> > 
>> > Are you sure that you don't want to try XMPP? We can create private /
>> > public chat
>> > rooms. And jmp.chat has a android client. cheogram: 
>> > https://f-droid.org/en/packages/com.cheogram.android/
>> > which is based on the "conversations" XMPP client. Both work
>splendidly
>> > in mobile. 
>> > 
>> > P.S. hmmmm, well I actually am trying a fun experiment. For at least a
>> > week the only
>> > computer that I will use is the Hurd running on real hardware...does
>the
>> > Hurd support
>> > a telagram client?
>> > 
>> Port it! It's a debian application 
>> 
>> They also have a web client
>
>I am not a big fan of telegram, so I probably won't try to port the debian
>application.  But I could try to run the web client.  The Hurd's best
>modern
>web browser is luabit ( in my opinion ), which might be powerful enough to
>run
>the telegram client.
>


web.telegram.org

Give it a try! :)
>> 
>> > 
>> > > 
>> > > > 
>> > >  > > 
>> > >  > > > 
>> > >  > > > > 
>> > >  > > > > Are you a ARM folk too?
>> > >  > > > > 
>> > >  > > > An enthusiast, not an ARM system developer though. Did it for
>> > > 
>> > quite
>> > 
>> > > 
>> > > > > > some time for i686 and x86_64, but got so many years working
>with
>> > >  > > > business applications with high level languages that started
>> > > 
>> > really
>> > 
>> > > 
>> > > > > > missing the low-level C stuff.
>> > >  > > > 
>> > >  > > > I daily drive in a M4 MacBook, have a few Raspberry Pis and a
>few
>> > >  > > 
>> > >  > other
>> > >  > 
>> > >  > > 
>> > >  > > > ARM SoCs. But my ultimate goal is to have it booting on an
>old M1
>> > > 
>> > Mac
>> > 
>> > > 
>> > > > > > Mini, even if just via serial TTY.
>> > >  > > > 
>> > >  > > Could we get it booting starting off on u-boot? If we modify
>the
>> > > 
>> > code to
>> > 
>> > > 
>> > > > > allow hurd to work, because currently it only supports Linux
>> > > 
>> > loading
>> > 
>> > > 
>> > > > > 
>> > >  > > > 
>> > >  > > > > 
>> > >  > > > > Perhaps if we are lucky ;) we could get arm.com folks to
>work
>> > > 
>> > on
>> > 
>> > > 
>> > > > > 
>> > >  > hurd.
>> > >  > 
>> > >  > > 
>> > >  > > > > but we may not be lucky :(
>> > >  > > > > 
>> > >  > > > That would be great.
>> > >  > > > 
>> > >  > > If anyone that knows arm.com people sees this thread, get their
>> > >  > > attention, please.
>> > >  > > 
>> > >  > > If you told me how id get their attention, id surely push it a
>try.
>> > >  > > 
>> > >  > I sometimes give puri.sm a suggestion (business idea). You could
>try
>> > > 
>> > to
>> > 
>> > > 
>> > > > convince them
>> > >  > to port their Librem 5 to the Hurd. I own such a device. The
>librem 5
>> > >  > supports
>> > >  > a virtual serial console via USB...
>> > >  > 
>> > >  > [email protected] mailto:[email protected]
>> > >  > 
>> > >  Intriguing, I'm into arm.com people
>> > >  more, but I'm sure we can do that, for them to think about it, what
>> > >  we need to do is make them realize
>> > >  the benefits of porting their machine/chipset to the hurd.
>> > >  
>> > >  They won't just do it for no reason..
>> > > 
>> > I already sent them an email saying that they should support the Hurd.
>> > 
>> > Also the librem 5 supports a hardware serial too!
>> > 
>> > > 
>> > > (Same with the arm.com folks tbf)
>> > >  
>> > >  > 
>> > >  > 
>> > >  > 
>> > >  Thanks!
>> > >
>> > 
>> Thanks!
>>
>

Thanks!

Reply via email to