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
18
Joined
9 mo. ago

  • Steam is not a subscription service

    Steam provides a cloud service. Not dissimilar to other subscription-based services. Had they been using AWS, they would also have been affected by the outage, resulting in Steam also being mentioned in the headline. So it's just as relevant as the others.

    you'll never own a piece of software by buying it in a video game store.

    Sure, I'm both granted a license on both Steam or GOG, but the crucial difference is still about offline access. If GOG stopped existing tomorrow, I'd still be able to install, and play, all my GOG games. The same cannot be said for Steam. Which one, then, grants the most ownership? License or no license.

  • It IS a scam since a lot of subscription services do not make it clear that the buyer is only granted limited access, and not ownership of the product.

    Just last year, due to legal reasons, Steam placed a notice on their cart page stating that purchases only grant a license—much to the surprise of some Steam users. Steam has been around for 20+ years, and it took a piece of legislation to force the company to inform their buyers of this very important fact. It is clear that they would rather have misinformed customers, much like in a scam.

  • Ideas

    Jump
  • I host many services on my server. Just to list a few: my website, Jellyfin, Lemmy, a Monero node, and Nextcloud.

    My main reasons for choosing home-hosting over cloud-hosting are:

    • Full Privacy
    • Complete Data Ownership
    • Local Access
  • 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.

  • Try Valibot. It is inspired by Zod.

    According to the Valibot FAQ, the main difference with Zod is:

    The functionality of Valibot is very similar to Zod. The biggest difference is the modular design of our API and the ability to reduce the bundle size to a minimum through tree shaking and code splitting. Depending on the schema, Valibot can reduce the bundle size up to 95% compared to Zod. Especially for client-side validation of forms and serverless environments this can be a big advantage.

  • 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.