Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)FH
Posts
0
Comments
13
Joined
6 mo. ago

  • I think the Forgejo project should be given some leniency when it comes to the development of its federation. After all, no other software forge has achieved such a feat as of this date, not even the likes of Gitlab.

    The good news is that we don't have to wait for Forgejo federation. We already have software, such as Lemmy, that can supplement as a federated discussion and issue board. To maintain an audit trail, just cross-reference between Forgejo issues and Lemmy posts as needed.

  • I'm open to the idea of using Lemmy for discussions, and feature requests, for my open-source software projects. My projects are on a self-hosted Forgejo instance and Forgejo currently lacks a discussion feature. But, unfortunately, none of my projects are popular enough to deserve a discussion board. 😭

  • I updated my MinIO instance yesterday only to find that many features have been removed (such as SSO). Of course, this is a move to force users to pay for a license.

    I will wait it out to see if a fork happens so I can switch to that. If not, then I'll switch to Garage.

  • I've tried both and I prefer Ultrawide for the following reasons:

    • Less cables. Cable management is already hard enough as it is.
    • No borders in between screens. Looks amazing when watching movies and for gaming.

    My current monitor is a GIGABYTE G34WQC.

  • You can try out Peer Calls. It's a peer-to-peer video and text chat that uses WebRTC, and is very lightweight. You can either use the flagship instance or self-host your own. One of the disadvantages is that text messages are not stored and are lost when the chat room is closed.

  • Ogrim is influenced by ALTCHA. Taking a quick glance, Anubis is a similar solution with some differences of solving the same problem:

    • Anubis sits between the target service and the reverse proxy, while Ogrim sits behind the target service.
    • One Anubis instance is needed per service, while a single Ogrim instance can be used for multiple services.
    • The target service does not need integration with Anubis. On the other hand, Ogrim and its services must be integrated to work.
    • Anubis will block search engine indexers, affecting the SEO of the target service. This is not the case with Ogrim.