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/)XA
Posts
2
Comments
1,057
Joined
7 mo. ago

  • Obviously, they monetize Codeberg because they’re providing a service. That monetization feeds Forgejo development. They could also sell official support for people hosting their own instances of Forgejo. This is a very common thing that open source companies do…

    This is literally what I said in my original post. Free products must monetize, as they get larger they have to continue to monetize more and more because development and infrastructure costs continue to climb...and you budged in as if this somehow doesn't apply to Forgejo and then literally listed examples of why it does. I mean, Jesus my guy.

    You are claiming Forgejo will do this.

    I'm claiming that it is a virtual certainty of the age of technology that we live in that popular free products (like Github) eventually balloon into sizes which are unmanageable while maintaining a completely free model (especially without restriction), which then proceed to get even more popular at which time they have to find new revenue streams or die.

    It's what's happened with Microsoft, Apple, Netflix, Hulu, Amazon Prime, Amazon Prime Video, Discord, Reddit, Emby, MongoDB, just about any CMS CRM or forum software, and is currently happening to Plex, I mean the list is quite literally endless. You could list any large software company that provides a free or mostly free product and you'll find a commercial product that they use to fund future development because their products become so popular and so difficult/costly to maintain they were forced into a monetization model to continue development.

    Why you think Forgejo is the only exception to this natural evolution is beyond my understanding.

    I'm fully aware of the difference between Codeberg and Forgejo. And Forgejo is a product and its exceptionally costly to build and maintain. Costs which will continue to rise as it has to change over time to suit more and more user needs. People seem to heavily imply that free products cost nothing to build, which is just insane.

    I've been a FOSS developer for 25 years and a tech PM for almost 20. I speak with a little bit of authority here because it's my literal wheelhouse.

  • That's a very accurate statement which has absolutely nothing to do with what I've said. Fact of the matter stands, is that those who generally seek to use a Github alternative do so because they dislike Microsoft or closed source platforms. Which is great, but those platforms with hosted instances see an overwhelmingly significant portion of users who visit because they choose not to selfhost. It's a lifecycle.

    1. Create cool software for free
    2. Cool software gets popular
    3. Release new features and improve free software
    4. Lots of users use your cool software
    5. Running software becomes expensive, monetize
    6. Software becomes even more popular, single stream monetization no longer possible
    7. Monetize more
    8. Get more popular
    9. Monetize more

    By step 30 you're selling everyone's data and pushing resource restrictions because it's expensive to run a popular service that's generally free. That doesn't change simply because people can selfhost if they want.

  • VPN.. This is a specific problem that VPNs were created to solve.

    On your Wireguard network (or whichever), note your vLAN IPs, and configure rclone/rsync with them like normal. Ensure you're connected to Wireguard and then run your command;

     cli
        
    ❯ fd --change-older-than 30days -X rclone sync phone:my/path/here pc:destination/path/here
    
      

    Using a VPN ensures that regardless of WiFi/Cellular connections you'll still be able to transfer at home, or remotely. Using methods like hostnames only work locally.

  • Am I not allowed to tell people I like the beer I brew?

    That's not really what he's doing though. It would be like if you pretended to be a customer and drink your own beer in front of actual customers and were like "WOW! This beer is super good! The guy who made it has a really big dick!"

    It's just shitty to do because it's sheistery as fuck.

    Plex employees totally have the right to review Plex in the store. But they should be expected to advertise that they work for Plex...because he didn't the review loses any credibility that it had previously.

  • Until there will be.

    I think people are grossly underestimating the sheer size and significance of the issue at hand. Forgejo will very likely eventually get to the same point Github is at right now, and will have to employ some of the same safeguards.

  • Hate to point it out, but it's an entirely different scenario.

    43 USC §364.e: With respect to geographic names the pertinent decisions and principles issued by the Secretary shall be standard for all material published by the Federal Government. The United States Board on Geographical Names in the Department of the Interior created by Executive order, is abolished, and the duties of said Board are transferred to the Board herein created, and all departments, bureaus, and agencies of the Federal Government shall refer all geographic names and problems to the said Board for the purpose of eliminating duplication of work, personnel, and authority.

    We didn't rename the Gulf, but the way its referenced from within the federal government (and its agencies) was changed by EO. Since Google is a government contractor, they're contractually obligated (and legally obligated) to follow the nomenclature expressed by the US board on geographical names or they risk losing all of their government contracts.

    So did we change the name of the Gulf? No. Is it shown different to US residence now? Yes. Google additionally released a statement saying;

    “a longstanding practice of applying name changes when they have been updated in official government sources.”

  • If you want to support a *nix distro, that's awesome and I fully support you. What you shouldn't support is distributions locking features behind a paywall.

    This is how you get Microsoft Windows and Copilot.


    To answer your question--Windows is destructive to *nix boot sectors. When you update Windows, it will bork your *nix install. Dual booting with Windows is a real PITA.

  • I was unaware of this change, and it's perfectly acceptable. No one has any ground to lambast Signal for requiring phone numbers to get an account. I think that's a perfectly reasonable spam mitigation technique. The issue is having to shotgun your phone number to every Howard and Susan that you want to use Signal to communicate with.

    This was honestly the only thing holding me back from actually using Signal. I'll likely register for an account now.

  • Only a matter of time now, really.

    This shift of the dollar from a global reserve to being just another currency went from a realistic impossibility to "probable" in the course of a 90 days. If it weren't so fucking crazy it would actually be impressive.