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/)DG
Posts
0
Comments
103
Joined
2 yr. ago

  • We will have more salespeople next year because we really need to explain to people exactly the value that we can achieve with AI. So, we will probably add another 1,000 to 2,000 salespeople in the short term.

    Well, good luck!

    I can't wait for the AI bubble to burst. It's going to be hilarious to see these kinds of CEOs falling flat on their faces. Unfortunately, it will not be the CEOs who will suffer the most from the consequences.

  • if the database "can't handle it" [...] that proves that they make poor choices.

    Exactly, the database should never even have to handle the password in it's original form and hashing algorithms don't care about special characters.

  • You're right.

    We’ve decided that IPFS is not yet ready for prime time. We’ll still link to files on IPFS from Anna’s Archive when possible, but we won’t host it ourselves anymore, nor do we recommend others to mirror using IPFS. Please see our Torrents page if you want to help preserve our collection.

  • I'd say ask the original developer directly. Getting your changes merged upstream should be the preferred option for you, the original dev and the users. If everything goes right, you both could figure out a way to do this, maybe by re-introducing your refactorings and fixes one by one in smaller pull requests. Maybe you could become a maintainer in the process and support the original dev long term so everybody wins.

    If the original developer doesn't respond or declines you could think about bringing your own fork forward. Think about the consequences though, the original dev might get frustrated by a competing fork and abandon the project completely. The users on the other hand might be confused or insecure about which version to choose. Your fork must offer a lot for them to jump ship and switch.

    Generally I'd say open source is about working together, not against one another, so just shoot them a message and see where it goes.

  • This is insane. You want to send kids to the frontline? No? Then how is this going to help?

    If your army needs more soldiers, maybe try a compulsory military service again. You don't need to get little kids all excited about guns, the military and the possibility of war.

    Look at those happy faces and sparkling eyes, they're all feeling so strong while fantasizing about real combat and asking themselves if they would shoot someone. Horrible.

    I'm not saying that we (speaking as a EU citizen) don't need a strong military to defend ourselves, we definitly do. But teaching young children how to operate assault rifles is not the way, it's dangerous symbolism at best and bleak warmongering at worst.

  • Having a solution that works for you is never a bad thing.

    Now it comes down to what you want to archive: Do you want something that just works? Great, you're done - now go on and do some other things that you like, that's perfectly fine. Or do you want to learn more about servers, virtualization, linux, networking and selfhosting in general? Then there are a million ways to get started.

    I'd suggest to setup a little lab, if you haven't already. Install Proxmox on your server and run CasaOS inside a virtual machine. Now you've learned about hypervisors and virtual machines. Afterwards you could create a second virtual machine to play around - maybe install debian and get used to the linux cli. Install docker manually, run some apps using docker-compose. Now you're already doing some stuff that CasaOS does under the hood.

    The possibilities are endless, the rabbit hole is deep. It can be a lot of fun, but don't force youself to go down there if you don't want to.