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/

  • 19 Posts
Joined 8M ago
Cake day: Apr 13, 2022

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)

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)

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!

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.

Togethr: Soprani.ca Social
A new initiative from the folks at jmp.chat creates a fediverse compatible hosting solution that eventually aims to integrate with XMPP!

Welcome, and thanks for the newsletter translations!

This release fixes RFC 3920 session building ([#3468](https://lab.louiz.org/poezio/slixmpp/-/issues/3468)), improves certificate errors handling, and adds an XEP-0454 (OMEMO Media Sharing) plugin. The python cryptography package is required to use the XEP-0454 plugin.

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.

New Community: /c/accessibility
Join us in a new community space dedicated to accessibility concerns in clients and the network more broadly! We hope to see you there.

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!

Taking the Temperature
What are your thoughts on Lemmy so far? I'd love to know how people feel about it; what could be improved; etc.

Quick update: it looks like email confirmations aren’t being sent and account applications aren’t working. I’ve emailed the hosting provider to ask for a fix and will update when account registration has been re-enabled.

On the main home page you can choose “local”, but otherwise no, Lemmy doesn’t have any real admin tools which is quite frustrating.

Temporary Registration Restrictions
Hi all, there was a wave of spam this evening so I’ve temporarily required moderator approval to create a new account or community. If this causes any issues, please let me know. Thanks!

I believe I have cleaned up all the spam now; please file reports if you notice anything I’ve missed, thanks!

Ahh, fair enough; I could go either way on that one, but it does make more sense to me. I think the same logic applies though: the prosody developers wouldn’t necessarily be better stewards than a user, and if users make some other kind of group the prosody developers wouldn’t necessarily be able to excersize control over it. That’s not to say that our position can’t favor “official” project groups, I just can’t figure out if it’s a good idea or not.

That seems to have worked; hopefully you get replies too :)

I think they meant that the reference client/server get the new features. You’re correct that the other third party clients have the same issue as XMPP where they all implement their distinct subsets of features or take a long time to update. Having the specs in one giant document or in multiple little documents doesn’t make much difference there.

If no one else has opinions, I’m going to go ahead and link this from the sidebar as a temporary measure. Moderation policy should still be chatted about though.

Should the default community be meta or general?
Someone mentioned that they don't have a good place to post releases for a community that's not on this instance. Maybe we should make this default group a more general group? It can still be for discussion about the instance too (or we can have a separate /c/meta if we think people won't want them together). What do others think? (the sidebar already says this is for general discussion, so this is really about whether we should rename it and/or split the group in two)

Anyone want to make an icon for the support room?
Over on /r/xmpp they get a lot of questions about how to configure a server and what not, so I decided to make a home for those sorts of questions here when the community isn't on Lemmy over at /c/support. Would anyone like to design an icon or possibly a header banner for /c/support community? It would be nice to spruce things up a bit!

What types of communities should be allowed?
If someone creates a community for their XMPP project, that should obviously be allowed. But what about tangentially related technologies or XMPP-focused general discussion communities? Eg. would an IETF KITTEN Working Group community be disallowed because it's not specific to XMPP (not that they're likely to create a group, I was just trying to think of something tangentially related)? What about a group to discuss XMPP Security or XMPP UX that's not specifically tied to a project or group? It may be worth us developing a policy on this early on to stop conflicts before they arise and to stop having to grandfather in to many groups if we decide later that they're out of scope.

How should local moderation decisions be handled?
Each community can appoint its own moderators and make its own separate decisions about what sort of content is allowed, but we should also likely think about an instance wide way of determining what sorts of content are and are not allowed and how moderation decisions are made. It's not a problem yet, but I figure it can't hurt to go ahead and get feedback from the community about what sorts of communities have good or bad moderation practices that we can emulate. What do others think?

Welcome to Lemmy!
Oops, hi again all; I am just learning to administer a Lemmy instance and accidentally deleted all my posts. Not to worry though, feel free to re-introduce yourself here, and welcome to lemmy!