Search

I don't have a Github account after deleting it some time after it was ought by Microsoft. Given the rise of anti-US sentiment and calls to stop using their products, more people leaving Github might be a real occurrence. How can I and others who have left, are leaving, and will leave Github, be able to contribute?

As part of the ongoing missionary work.ober on The Bad Place, I posted this and thought it would be also worth posting it over here as a snapshot.of the current state of play. ____ One of the main complaints about signing up to a Lemmy instance/server is the decision paralysis caused by having to pick one. I've found that picking a local/regional instance or one related to a topic/subject can really help narrow the choices right down. This is a list of the local/regional servers currently available.

There was a similar list posted last year, but a lot has changed since.

Africa

Only has one instance covering the whole continent: https://baraza.africa/

Asia

• 🇧🇩 Bangladesh: https://buddyverse.one/
• 🇯🇵 Japan: https://lm.korako.me/
• 🇲🇾 Malaysia: https://monyet.cc/
• 🇰🇷 South Korea: https://lemmy.funami.tech/
• 🇹🇷 Turkey: https://lemmy.com.tr/

Europe

• Basque Country: https://lemmy.eus/
• 🇧🇪 Belgium: https://0d.gs/
• 🇧🇬 Bulgaria: https://feddit.bg/
• Catalonia: https://lemmy.cat/
• 🇩🇰 Denmark, including Greenland (for now): https://feddit.dk/
• 🇫🇷🇧🇪🇨🇭 France, Belgium, Switzerland: https://jlai.lu/
• 🇩🇪🇦🇹🇨🇭🇱🇮 Germany, Austria, Switzerland and Lichtenstein: https://feddit.org/
• 🇫🇮 Finland: https://sopuli.xyz/ and https://suppo.fi/
• 🇮🇸 Iceland: https://feddit.is/
• 🇮🇹 Italy: https://feddit.it/
• 🇱🇹 Lithuania: https://group.lt/
• 🇳🇱 Netherlands: https://feddit.nl/
• 🇵🇱 Poland: https://fedit.pl/ and https://szmer.info/
• 🇵🇹 Portugal: https://lemmy.pt/
• 🇸🇮 Slovenia: https://gregtech.eu/
• 🇸🇪 Sweden: https://feddit.nu/
• 🇹🇷 Turkey: https://lemmy.com.tr/
• 🇬🇧 UK: https://feddit.uk/

North America

• 🇨🇦 Canada: https://lemmy.ca/ and https://sh.itjust.works/
• 🇲🇽 Mexico: https://mujico.org/
• 🇺🇸 USA: https://lemmyusa.com/ and https://discuss.online/, also for the Midwest: https://midwest.social/ and for Madison, Wisconsin: https://lemmy.fan/

Oceania

• 🇦🇺 Australia: https://aussie.zone/
• 🇳🇿 New Zealand: https://lemmy.nz/

South America

• 🇧🇷 Brazil: http://lemmy.eco.br/
• 🇨🇱 Chile: https://feddit.cl/

____ Addendum to the Reddit post

Defunct:

• 🇭🇺 Hungary: https://fost.hu/
• 🇮🇩 Indonesia: https://lemmy.id/
• 🇯🇵 Japan: https://feddit.jp/
• 🇷🇴 Romania: https://feddit.ro/
• 🇪🇸 Spain: http://eslemmy.es/ and https://lemuria.es/
• 🇨🇭 Switzerland: https://feddit.ch/
• 🇺🇦 Ukraine: https://feddit.kyiv.ua/

Although note that https://lemuria.es/ still seems to be running a Lemmy instance, albeit a broken one, so there is a chance it could be saved.

Thanks to @Blaze@feddit.org , @Sunshine@lemmy.ca and everyone in this post who contributed links.

Generic Threadiverse support

Thanks to @rikudou@lemmings.world's contribution (#28), Lemmy Federate now supports all software types that implements group federation such as PieFed, NodeBB, Guppe 🎉

But unfortunately, not everything is perfect. Since there is no Fediverse standard for verifying whether a user is an admin, I have to register admins manually. I am also considering manually approving instances that are not guaranteed in Fediseer against spam attacks. Please contact me for this.

Note: Lemmy and Mbin works as before.

Top instances of Lemmy

With the addition of Lemmy.ml, the top 25 largest instances on Lemmy now use Lemmy Federate (except slrpnk.net). I think we can now consider that we have fixed the accessibility issue that was the reason I created this tool. Even if we didn't fix it, at least we band-aided it :)

Instance blocking feature

In addition to the allow list, a block list has been added.

• If you allow at least one instance, you will not follow any other instances.
• If you block an instance, you will continue to follow instances other than those you blocked.

Dedicated community

I didn't want to open it before, but now that we are trying to be compatible with more software, I believe a dedicated community could be useful. That's why I created a community here !lemmyfederate@lemy.lol. If I make an update from now on, I'll probably post it there.

https://lemmy-federate.com/ https://github.com/ismailkarsli/lemmy-federate

cross-posted from: https://lemmy.world/post/25243870

> I recently started messing around with ActivityPub, Mastodon and Lemmy and created LemmyLink, an open-source bot that seamlessly bridges Reddit and Lemmy. Triggered by the phrase “LemmyLink!” in a Reddit post title, body, or comment, the bot automatically creates a corresponding post on your chosen Lemmy instance. This allows Bidirectional post and comments between Reddit and Lemmy by triggering a Reddit bot. > > Feel free to play around with it on r/LemmyLink. Simply include "LemmyLink!" anywhere in your post title, body or comment on the LemmyLink sub. This is setup on my own Lemmy instance lemmylink.com currently not federated and marked as a bot to avoid spamming the Fediverse. > > There are some pros and cons to bridging communities but I think if done with transparency and user opt-in it could serve as an interesting way to bring more users in to the Fediverse. But, I'm curious what others think. > > How LemmyLink Works > > Only works for Subreddits and Lemmy communities specified in the code > Reddit users include "LemmyLink!" in their Reddit post or comment > LemmyLink posts the Reddit comment or post to Lemmy > LemmyLink responds to the Reddit post or comment with link back to the Lemmy post > The code is rough so go easy on me but it is available on GitHub: > https://github.com/ateames/LemmyLink > > Feel free to fork it, suggest improvements, or simply try it out.

Currently, URLs to posts have this format:

lemmy.ml/post/[number]

I suggest changing it to this so people can see the community immediately in shared URLs:

lemmy.ml/c/[community-name]/[post-number]

What are best lemmy communities?

@lemmy

For you, what is the best Lemmy community/subreddit?

When viewing different instances, whether to copy a community link to make another instance aware of it & subscribe to it or otherwise, it would be nice to have a switch along the top bar to switch between admin-set light/dark mode themes.

That way you aren't either forced into being blinded by light mode or having to let your eyes adjust to dark mode. Admins could choose the variant of light or dark theme to have the switch toggle between, so in the case of more customized instances they could retain their distinct style.

For reference, see almost any site with a light/dark toggle, but for a closer example, see Piefed's approach.

cross-posted from: https://lemmy.ml/post/22529967

> ## What is Lemmy? > > Lemmy is a self-hosted social link aggregation and discussion platform. It is completely free and open, and not controlled by any company. This means that there is no advertising, tracking, or secret algorithms. Content is organized into communities, so it is easy to subscribe to topics that you are interested in, and ignore others. Voting is used to bring the most interesting items to the top. > > ## Changes > > This is a small bugfix release with the following: > > - Fixing cors origin wildcard. by @dessalines in #5194 > - Fetch community mods synchronously by @Nutomic in #5169 > - Move aggregates to replaceable_schema, fix error (fixes #5186) by @Nutomic in #5190 > > ### Full Changelog > > - Lemmy Backend > - Lemmy-UI > > ## Upgrade instructions > > There are no breaking changes with this release. > > Follow the upgrade instructions for ansible or docker. > > If you need help with the upgrade, you can ask in our support forum or on the Matrix Chat. > > ## Thanks to everyone > > We'd like to thank our many contributors and users of Lemmy for coding, translating, testing, and helping find and fix bugs. We're glad many people find it useful and enjoyable enough to contribute. > > ## Support development > > We (@dessalines and @nutomic) have been working full-time on Lemmy for over five years. This is largely thanks to support from NLnet foundation, as well as donations from individual users. > > If you like using Lemmy, and want to make sure that we will always be available to work full time building it, consider donating to support its development. A recurring donation is the best way to ensure that open-source software like Lemmy can stay independent and alive, and helps us grow our little developer co-op to support more full-time developers. > > - Liberapay (preferred option) > - Open Collective > - Patreon > - Cryptocurrency >

I'm not sure if this post should instead be put in !lemmy_support@lemmy.ml, rather than here; please let me know if this would be better suited there, and/or if it is out of the scope of this community. Also, please let me know if there is a different community, other than where it has already been posted, in which this post would be better suited.

---

Topics could include (this list is not intending to be exhaustive — if you think something is relevant, then please don't hesitate to share it):

• Moderation
• Handling of illegal content
• Server structure (system requirements, configs, layouts, etc.)
• Community transparency/communication
• Server maintenance (updates, scaling, etc.)

---

What is Lemmy?

Lemmy is a self-hosted social link aggregation and discussion platform. It is completely free and open, and not controlled by any company. This means that there is no advertising, tracking, or secret algorithms. Content is organized into communities, so it is easy to subscribe to topics that you are interested in, and ignore others. Voting is used to bring the most interesting items to the top.

Changes

This release took a long time to complete due to a major performance problem which brought lemmy.ml to a crawl every time we tried to deploy the new version. It took a lot of testing (in production) to narrow it down to a single commit, and finally fix the problem.

The release itself contains numerous bug fixes and minor improvements:

Lemmy

Enhancements

• Parallel federation sending by @phiresky in #4623
• Reduce CPU usage for generating link previews by @phiresky in #4957
• Switch from OpenSSL to rustls by @kwaa in #4901
• Increase max post url length to 2000 characters by @dessalines in #4960
• Increase max length of user bio to 1000 charactes by @dessalines #5014
• Reduce maximum comment depth to 50 by @nutomic #5009
• Resize post thumbnails by @nutomic #5107/files
• Add category to RSS feeds by @nutomic #5030
• Allow users to view their own removed/deleted communities by @dessalines in #4912
• Add backend check to enforce hierarchy of admins and mods by @dessalines in #4860
• Do pictrs transformations for proxied image urls by @dessalines in #4895
• Enable more build optimizations by @nutomic in #5168
• Calculate "controversial" ranking with exponent instead of multiply (just like Reddit) by @dullbananas in #4872
• Automatically remove tracking parameters from URLs by @dessalines #5018
• Relax timeout for sending activities by @Nothing4You in #4864

Bug Fixes

• Fix admin notification for new user registration (fixes #4916) by @Nutomic in #4925
• Allow community settings changes by remote mods @flamingo-cant-draw in #4937
• Fix problem with connecting to Postgres with TLS @FenrirUnbound in #4910
• Fix bug when commenting in local-only community by @dessalines in #4854 and @abdel-m in #4920
• Fix scheduled task to delete users with denied applications by @Nothing4You in #4907

API

• Return image dimensions and content type in API responses by @dessalines in #4704
• Adding a show_read override to GetPosts. by @dessalines in #4846
• Add show_nsfw override filter to GetPosts. by @dessalines in #4889
• Require authentication for site metadata fetch endpoint by @dessalines in #4968
• Add the ability to fetch a registration application by person_id by @dessalines in #4913
• Order community posts by published data, not id by @dullbananas in #4859
• Throw error when non-mod posts to mod-only comm or when URL is blocked by @flamingo-cant-draw in #4966
• Add option to search exclusively by post title by Carlos-Cabello #5015

Database

• Approve applications in transaction by @Nothing4You in #4970
• Use trigger to generate apub URL in insert instead of update, and fix query planner options not being set when TLS is disabled by @dullbananas in #4797

Lemmy-UI

• Fix full-size post images. by @dessalines in #2797
• Fix modlog ID filtering. by @dessalines in #2795
• Allow Arabic and Cyrillic characters when signing up or creating community by @SleeplessOne1917
• UX - Swap "Select Language" and "Cancel/Preview/Reply" button locations around in commentsReverse order of buttons in Reply TextArea
• Fix jump to content by @SleeplessOne1917
• Fixing peertube and ordinary video embeds. by @dessalines in #2676
• Changing sameSite cookie from Strict to Lax. by @dessalines in #2677
• Remove show new post notifs setting. by @dessalines in #2675
• Fix memory leak around emojis on server render by @makotech222 in #2674
• Enable spellcheck for markdown text area by @SleeplessOne1917 in #2669
• Pre release dep bump by @SleeplessOne1917 in #2661
• Add ability to fill magnet link title on post creation. by @dessalines in #2654
• Registration application view by @SleeplessOne1917 in #2651
• Add torrent help by @dessalines in #2650
• More moderation history by @dessalines in #2649
• Fix tribute related bug by @SleeplessOne1917 in #2647
• Remove min and max length from password input when using login form by @SleeplessOne1917 in #2643
• Remove trending communities card from home. by @dessalines in #2639
• Set data-bs-theme based on the presence of "dark" in theme name by @SleeplessOne1917 in #2638
• Fixing modlog filtering to allow admins and mods to filter by mod. by @dessalines in #2629
• Fix issue from logo bugfix by @SleeplessOne1917 in #2620
• Make more post params cross-postable by @SleeplessOne1917 in #2621
• Fix wonky comment action icon button alignment by @SleeplessOne1917 in #2622
• Prevent broken logo from crashing site by @SleeplessOne1917 in #2619
• Add rate limit info message. by @dessalines in #2563
• Fix getQueryString by @matc-pub in #2558

New Contributors

• @abdel-m made their first contribution in #4920
• @johnspurlock made their first contribution in #4917
• @FenrirUnbound made their first contribution in #4910
• @kwaa made their first contribution in #4901
• @Daniel15 made their first contribution in #4892

Full Changelog

• Lemmy Backend
• Lemmy-UI

Upgrade instructions

This upgrade could take as long as ~30 minutes for larger servers, due to needing to recalculate controversy ranks for all historical posts.

There are no breaking changes with this release.

Follow the upgrade instructions for ansible or docker.

If you need help with the upgrade, you can ask in our support forum or on the Matrix Chat.

Thanks to everyone

We'd like to thank our many contributors and users of Lemmy for coding, translating, testing, and helping find and fix bugs. We're glad many people find it useful and enjoyable enough to contribute.

Special shout out to @SleeplessOne1917, @phiresky, @dullbananas, @mv-gh, @Nothing4u, @asonix, @sunaurus, @flamingo-cant-draw, and @Freakazoid182 for their many code contributions and helpful insights.

Support development

We (@dessalines and @nutomic) have been working full-time on Lemmy for over five years. This is largely thanks to support from NLnet foundation, as well as donations from individual users.

If you like using Lemmy, and want to make sure that we will always be available to work full time building it, consider donating to support its development. A recurring donation is the best way to ensure that open-source software like Lemmy can stay independent and alive, and helps us grow our little developer co-op to support more full-time developers.

• Liberapay (preferred option)
• Open Collective
• Patreon
• Cryptocurrency

Don't !panic , we're just doing some server upgrades.

An idea I just recently had was to add the ability for users to verify accounts on Lemmy using Matrix accounts as an alternative to Email. I think this would be a great idea since it allows for users to have choices in how they sign-up to their accounts. It would also encourage more usage of Matrix accounts for secure messaging between users, a feature which hasn't seen much use among users here.

It would still in most cases be optional and server admins could choose if it's even enabled at all, just like how email verification is right now. Even if it was required I feel like it should be a supplement to email in most cases but servers could choose to make it required instead of email, especially in cases where they don't have a mail server.

The different states of it could be:

• Matrix or Email Required
• Matrix required, Email optional
• Email Required, Matrix optional
• Email and/or Matrix Optional

Servers could also choose to have the matrix account used for verification be on a server that isn't their own, though this would generally be discouraged and would be specifically for admins who don't have their own infrastructure (like the ones who don't have a mail server).

I made an issue on the Main Lemmy github, feel free to check it out here. Feel free to either share your opinions on this here or on the Github issue.

I feel like there's an easy win to keep up with the fragmentation of discussions without waiting for some implementation of this feature request.

All a frontend needs to do is group all posts with the same URL together and display all their comments in the as one unified comment section. If you reply to the OP, you can either choose which community the comment goes to, and maybe set a default as well.

This functionality should be an extra switch for the frontend, so that the user can disable it and see individual posts.

This also nicely avoids not knowing how to deal with moderation, as each community moderator still maintains control.

Comments from blocked communities would not appear ofc.

This would both prevent seeing the same post multiple times on your feed, but also drive view to smaller communities where comment in their sections are ignored.

Doing some server upgrade testing.

Time zone converter

cross-posted from: https://eventfrontier.com/post/150886

> I'm pleased to announce the release of Echo for Lemmy! Echo is a Lemmy client for iPhone that I've been working on for a while and I'm excited to finally share it with you all. > > Echo for Lemmy is a fully native iOS application built using fully native Apple SDKs. This means it feels right at home on your iPhone and is designed to be fast, efficient, and easy to use. No overhead from web views or cross-platform frameworks. > > Here are some of the features available in Echo for Lemmy: > > - Connect with communities based on your interests. > - Sort your feed by most active, trending posts, new posts, and many more. > - Upvote and downvote posts & comments. > - Powerful search experience to find the content you're looking for. > - Create posts using share extension from any app on your device. > - Bookmark posts to easily find later. > - Fully native application with dark mode support & accessibility features. > > Echo for Lemmy is available for free on the App Store, with subscription plans available for Echo+. You can download it here: Echo for Lemmy on the App Store. > > You can also join the official Echo Lemmy community at !echo@eventfrontier.com. > > I'm excited to hear feedback, suggestions, bug reports, and feature suggestions. Feel free to comment here, or create a new post! You can also reach out via email at support@rrainn.com. > > This is only the beginning. Much more to come! > > --- > > Download Echo for Lemmy: https://echo.rrainn.com/download/iphone > > Echo Lemmy Community: !echo@eventfrontier.com > > Echo Mastodon Profile: @echo@mstdn-social.com > > --- > > !Screenshot of Echo for Lemmy on an iPhone showing a list of posts in your home feed.

Rather than communities being hosted by an instance, they should function like hashtags, where each instance hosts posts to that community that originate from their instance, and users viewing the community see the aggregate of all of these. Let me explain.

Currently, communities are created and hosted on a single instance, and are moderated by moderators on that instance. This is generally fine, but it has some undesirable effects:

• Multiple communities exist for the same topics on different instances, which results in fractured discussions and duplicated posts (as people cross-post the same content to each of them).
• One moderation team is responsible for all content on that community, meaning that if the moderation team is biased, they can effectively stifle discussion about certain topics.
• If an instance goes down, even temporarily, all of its communities go down with it.
• Larger instances tend to edge out similar communities on other instances, which just results in slow consolidation into e.g. lemmy.ml and lemmy.world. This, in turn, puts more strain on their servers and can have performance impact.

I'm proposing a new way of handling this:

• Rather than visiting a specific community, e.g. worldnews@lemmy.world, you could simply visit the community name, like a hashtag. This is, functionally, the same as visiting that community on your own local instance: [yourinstance]/c/worldnews
  • You'd see posts from all instances (that your instance is aware of), from their individual /worldnews communities, in a single feed.
  • If you create a new post, it would originate from your instance (which effectively would create that community on your instance, if it didn't previously exist).
  • Other users on other instances would, similarly, see your post in their feed for that "meta community".
• Moderation is handled by each instance's version of that community separately.
  • An instance's moderators have full moderation rights over all posts, but those moderator actions only apply to that instance's view of the community.
    • If a post that was posted on lemmy.ml is deleted by a moderator on e.g. lemmy.world, a user viewing the community from lemmy.ml could still see it (unless their moderators had also deleted the post).
    • If a post is deleted by moderators on the instance it was created on, it is effectively deleted for everyone, regardless of instance.
    • This applies to all moderator actions. Banning a user from a community stops them from posting to that instance's version of the community, and stops their posts from showing up to users viewing the community through that instance.
    • Instances with different worldviews and posting guidelines can co-exist; moderators can curate the view that appears to users on their instance. A user who disagreed with moderator actions could view the community via a different instance instead.
• Users could still visit the community through another instance, as we do now - in this case, [yourinstance]/c/worldnews@lemmy.world, for example.
  • In this case, you'd see lemmy.world's "view" of the community, including all of their moderator actions.

The benefit is that communities become decentralized, which is more in line with (my understanding of) the purpose of the fediverse. It stops an instance from becoming large enough to direct discussion on a topic, stops community fragmentation due to multiple versions of the community existing across multiple instances, and makes it easier for smaller communities to pop up (since discoverability is easier - you don't have to know where a community is hosted, you just need to know the community name, or be able to reasonably guess it. You don't need to know that a community for e.g. linux exists or where it is, you just need to visit [yourinstance]/c/linux and you'll see posts.

If an instance wanted to have their own personal version of a community, they could either use a different tag (e.g. world_news instead of worldnews), or, one could choose to view only local posts.

Go ahead, tear me apart and tell me why this is a terrible idea.

I first became aware of this about 4 months ago.

GitHub issue is 3069:

> It would be awesome if we could follow a post to be alerted of new comments added.

> As we are at it, why stop with posts? I'd suggest also having such alerts with comment sub-trees would be nice.

I was in a thread in !fediverse@lemmy.world earlier today, and it seems like there is still interest in this feature.

Last I heard, it seemed like progress on this feature is dependent on fixing an SQL Paging and filtering issue.

Any progress on this? Anything we can do to expedite the development of this feature?

Probably a hot take for everybody who just wants a drop-in replacement for Reddit, but I think a new platform needs to take the opportunity to improve over what's gone before.

So what I'm proposing is a more granular approach to curating one's feed on an individual user level, much like both Mastodon and apps for that platform offer (I'm going to use Tusky as an example because I've used that for a while and know its features fairly well).

Imagine a filter list where you could block specific terms, source URLs or other. No more irrelevant mentions of whatever annoys the hell out of you when you open /all. Along with your individual block list, limited as that is, it would help you as a user to home in on what matters to you.

Might this create filter bubbles? Yes, but if it's implemented on a per user level it won't affect other users' feeds. The "bubble" is a one-person act. In my experience /all on both Reddit and Lemmy suffers from people trying to curate it to their personal liking with downvotes, which just creates a monoculture.

Personally, I think free text filters would help solve that problem, and might aid users in engaging with their preferred communities. Suggestions, ideas?

EDIT: Looked a little deeper/better on GitHub and found this issue, #4865 which is likely the most related issue, and it seems the devs are aware.

It also seems to be a recent v19.5 -ish issue too from some of the comments there

---

I seem to be encountering what may be a bug with pinning/featuring posts ... interested if anyone's got similar/counter experiences

The issue is that the pinning of a post doesn't get federated correctly.

The conditions, AFAICT are:

• Post originates from a "federated instance" (IE, an instance other than the community's home instance)
• The mod action of pinning is also done by a moderator on a "federated instance"
• Lemmy versions 19.4 or greater (much more tentative, but from a brief perusal, it seems true)

The effect seems to be:

• The pinning works fine on the "home instance" of the community
• But federation breaks in two slightly different ways:
  • No pinning occurs
  • If a mod on a "federated instance" tries to pin, after an initially failed federation of "pinning", it will succeed on the federated instance only temporarily

The last dynamic is hopefully a clue to what could be happening (sounds like some queued tasks colliding in an incorrect way)

What is Lemmy?

Lemmy is a self-hosted social link aggregation and discussion platform. It is completely free and open, and not controlled by any company. This means that there is no advertising, tracking, or secret algorithms. Content is organized into communities, so it is easy to subscribe to topics that you are interested in, and ignore others. Voting is used to bring the most interesting items to the top.

Changes

This is a smaller bugfix release, with the following changes:

Lemmy

• Don't change encoding style in clean_url_params.
• Fix for federation last_successful_id.
• Fixing featured_local trigger.
• Fix postres TLS connection.

Lemmy-UI

• Fix for fetch page title.
• Fix create post focus resets.
• Make media uploads viewable only on your own profile.
• Fixing an auto-download bug.
• Regenerating lemmy-ui themes.

Full Changelog

• Lemmy Backend
• Lemmy-UI

Upgrade instructions

Follow the upgrade instructions for ansible or docker.

If you need help with the upgrade, you can ask in our support forum or on the Matrix Chat.

Thanks to everyone

We'd like to thank our many contributors and users of Lemmy for coding, translating, testing, and helping find and fix bugs. We're glad many people find it useful and enjoyable enough to contribute.

Support development

We (@dessalines and @nutomic) have been working full-time on Lemmy for over three years. This is largely thanks to support from NLnet foundation, as well as donations from individual users.

If you like using Lemmy, and want to make sure that we will always be available to work full time building it, consider donating to support its development. A recurring donation is the best way to ensure that open-source software like Lemmy can stay independent and alive, and helps us grow our little developer co-op to support more full-time developers.

• Liberapay (preferred option)
• Open Collective
• Patreon
• Cryptocurrency (scroll to bottom of page)