I work on the Mellium project and sometimes on XEPs. Bike mechanic during the day, but also sometimes freelance software development.

Hire me: https://willowbark.org/

  • 48 Posts
  • 36 Comments
Joined 7M ago
cake
Cake day: Apr 13, 2022

help-circle
rss
Wall Hitch Mount for Bike Storage
Someone at work was throwing away an old hitch mount bike rack a while back. I hated to see it go to waste, so I built a "hitch" for the wall of my garage: ![a hitch mount bike rack mounted to the wall](https://community.xmpp.net/pictrs/image/b3e7fc67-9bde-4edf-9af7-c8e095bdee90.jpeg) ![the same bike rack with two bikes on it](https://community.xmpp.net/pictrs/image/a279ae05-065c-4ac9-8bf0-64ad404d63af.jpeg)
fedilink


I will say that it’s worth being careful: there’s no option for a backup XMPP account (so your account better have perfect uptime) and I very rarely have incoming phone calls actually work (calling out works, calling in is pretty random, most of the time it doesn’t even ring). Also the UI on the client is still pretty bad (especially for group texts, which are almost unusably bad).

All that being said, it’s a great service, just know what you’re getting into before you make it your primary phone number, it’s not nearly as polished as they make it sound.


It only gets full of memes if that’s the culture you create (I hope we won’t do that, so far it seems like we haven’t). And I definitely wouldn’t follow everything on a high-volume chat, when you’re on and a topic of discussion you’re into starts or you just feel chatty, then you follow along, otherwise it’s not necessary. But that’s just how I do chat rooms, YMMV.


Bicycles chat room
Do you like #bicycles or #cycling? Do you also use an #xmpp compatible chat service? Join our new group chat at [bicycles@conference.samwhited.com](xmpp:bicycles@conference.samwhited.com?join). Hopefully this can become a fun community space to share pictures, post routes, and generally chat about bicycles. [Join us!](xmpp:bicycles@conference.samwhited.com?join)
fedilink

Bicycles chat room
Do you like #bicycles or #cycling? Do you also use an #xmpp compatible chat service? Join our new group chat at [bicycles@conference.samwhited.com](xmpp:bicycles@conference.samwhited.com?join). Hopefully this can become a fun community space to share pictures, post routes, and generally chat about bicycles. [Join us!](xmpp:bicycles@conference.samwhited.com?join)
fedilink

Bicycles group chat!
cross-posted from: https://community.xmpp.net/post/49428 > Do you like #bicycles or #cycling? Do you also use an #xmpp compatible chat service? Join our new group chat at [bicycles@conference.samwhited.com](xmpp:bicycles@conference.samwhited.com?join). Hopefully this can become a fun community space to share pictures, post routes, and generally chat about bicycles. > > [Join us!](xmpp:bicycles@conference.samwhited.com?join)
fedilink

Bicycles group chat!
Do you like #bicycles or #cycling? Do you also use an #xmpp compatible chat service? Join our new group chat at [bicycles@conference.samwhited.com](xmpp:bicycles@conference.samwhited.com?join). Hopefully this can become a fun community space to share pictures, post routes, and generally chat about bicycles. [Join us!](xmpp:bicycles@conference.samwhited.com?join)
fedilink

Oh nice, some of the GSoC projects are really interesting this year!




cross-posted from: https://community.xmpp.net/post/34677 > For the last few years we've accepted patches on both GitHub and Sourcehut and used Sourcehut for our CI system. We have tried to move entirely to Sourcehut in the past but it ended up [not meeting our needs](https://codeberg.org/mellium/xmpp/issues/51), and we've tried starting our own co-op code hosting, but were not able to find many cooperators who wanted to help (if you'd like to join us and cooperatively host a Gitea instance, [reach out](https://blog.samwhited.com/about/)!). We have been experimenting with mirroring a few of the main repos on Codeberg and using their experimental CI feature, and this has been going much smoother and has been much simpler than the current SourceHut integration. > > With all this in mind, we've decided that the time is right to move to [Codeberg](https://codeberg.org/). > > For the time being we will continue to accept pull requests for the main project and a few of the support libraries over on GitHub, and we will keep the main projects CI running on Sourcehut as well as on the new Codeberg CI so that both Codeberg and GitHub based PRs can show the status. However, smaller support libraries that do not receive contributions often will be moved entirely to Codeberg and PRs on GitHub will be automatically closed. > > Eventually, once we are certain everything is working smoothly, the old GitHub repos will be retired and become mirrors on which we do not accept contributions and all Sourcehut repos will be deleted. There is no timeline for this currently. If you would like to keep track of the timeline once we have one, or submit comments or suggestions you can track the issue https://mellium.im/issue/304 > > Some repos are still being moved, but the main project is now on Codeberg and ready to accept contributions. To track the overall migration, see https://mellium.im/issue/301 > > Thanks for your continued support and contributions!
fedilink

For the last few years we've accepted patches on both GitHub and Sourcehut and used Sourcehut for our CI system. We have tried to move entirely to Sourcehut in the past but it ended up [not meeting our needs](https://codeberg.org/mellium/xmpp/issues/51), and we've tried starting our own co-op code hosting, but were not able to find many cooperators who wanted to help (if you'd like to join us and cooperatively host a Gitea instance, [reach out](https://blog.samwhited.com/about/)!). We have been experimenting with mirroring a few of the main repos on Codeberg and using their experimental CI feature, and this has been going much smoother and has been much simpler than the current SourceHut integration. With all this in mind, we've decided that the time is right to move to [Codeberg](https://codeberg.org/). For the time being we will continue to accept pull requests for the main project and a few of the support libraries over on GitHub, and we will keep the main projects CI running on Sourcehut as well as on the new Codeberg CI so that both Codeberg and GitHub based PRs can show the status. However, smaller support libraries that do not receive contributions often will be moved entirely to Codeberg and PRs on GitHub will be automatically closed. Eventually, once we are certain everything is working smoothly, the old GitHub repos will be retired and become mirrors on which we do not accept contributions and all Sourcehut repos will be deleted. There is no timeline for this currently. If you would like to keep track of the timeline once we have one, or submit comments or suggestions you can track the issue https://mellium.im/issue/304 Some repos are still being moved, but the main project is now on Codeberg and ready to accept contributions. To track the overall migration, see https://mellium.im/issue/301 Thanks for your continued support and contributions!
fedilink


Moving to Codeberg
We previously discussed moving to [Codeberg](https://codeberg.org/), and I'm thinking the time is right to make the move from our current GitHub/SourceHut mix entirely to Codeberg. If you have any concerns or comments, now is the time!
fedilink






Copied here for discussion among non-contributors: As more people begin to rely on this project I have become somewhat concerned that our bus factor of 1 (ie. "me") is too low. It would be good to find more maintainers or leads from among the contributors who can be given access and continue the project if I become incapacitated or stop working on the project for any other reason. However, there really aren't enough contributions (or contributors who have a deep understanding of the full project) to do this right now, so the first step would be to try and find/engage more regular contributors. Suggestions welcome.
fedilink

Oh nifty, I do this when backpacking to keep rice, noodles, or whatever grains and cereals I’m carrying dry, but it never occurred to me that folks might do it at home too! What bottles work/look the best I wonder? On the trail I always used Gatorade bottles because they’re a bit thicker walled.





Right? Can I just sit on my bike and pretend to pedal?


I created a new Gajim community and cross posted there as well, for future use!


I’ve been looking forward to the UI overhaul since the office hours demo! I’m looking forward to it trickling into Fedora.


Welcome, and thanks for the newsletter translations!


Yes, I’m aware, but “rarely” is not “never”, so it seems worth having them.


It doesn’t “just” do that, it also makes it easier for the elderly, those in a wheelchair, those rolling a grocery trolley full of bags, etc.


I apologize if thatwsas a joke, my bad


This is exactly why we should stop pretending everything is fine and actually try to address the problem of Google doing damage to open ecosystems.


This kind of language is literally what I was replying to. You’re not helping, you’re just ensuring fewer people use XMPP. Stop spreading fud.


When people say “killed” they obviously don’t mean “literally no one uses it”. Also no one really cares that Whatsapp or Google are still using it internally. Google did serious damage to the public network and the broader XMPP ecosystem and it’s worth acknowledging and learning from that instead of just complaining that someone wasn’t absolutely precise in their language. For all intents and purposes, XMPP is effectively dead to the general public. Let’s try to bring it back to popular use and make sure Google et al. can’t do their “embrace, extend, extinguish” thing again.

TL;DR — please stop being snarky to the OP.


When you say “not quite there yet”, what issues did you run into?


Do you already have a bridge setup and hooked up to your account, eg https://jmp.chat? If you go to add a contact, for instance, it will let you add a phone number and automatically append the bridge address (@cheogram.com in this case)


I’ve been using Cheogram (another Conversations fork that adds features related to telephone dialing and SMS gateways; if you don’t use one of those, it’s probably not super useful and Conversations is a better choice). I think it’s only available on F-Droid, sadly: https://f-droid.org/en/packages/com.cheogram.android/


Seems okay to me, but I’d bet existing ones are already established and probably other instances will have a wider user base. But I don’t see any reason to forbid it, personally.


The account applications appear to be working again (or maybe they always were?) but are just a bit slow. Expect registrations to take a few hours before approval. Thanks!