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/)C

cron

@ cron @feddit.org

Posts
32
Comments
186
Joined
2 yr. ago

  • OpenAI, Google, Anthropic admit they can’t scale up their chatbots any further

    Jump

  • It's absurd that some of the larger LLMs now use hundreds of billions of parameters (e.g. llama3.1 with 405B).

    This doesn't really seem like a smart usage of ressources if you need several of the largest GPUs available to even run one conversation.

  • Self-Hosting Isn't a Solution; It's A Patch

    Jump

  • There is no way to be 100% sure, but:

    • bitwarden and ente have open source clients that ecrypt all data locally in a way that the provider can't restore data
    • nextcloud isn't optimal, while you can encypt data at rest, the provider might be able to spy on you
    • With mail providers it is difficult, but mailbox.org has my (personal) trust by building their business model on data protection and open source

  • Self-Hosting Isn't a Solution; It's A Patch

    Jump

  • I can and do self host, but I'm not willing to provide these services for free. I don't want to be responsible for other peoples passwords or family photos.

    Thats where good, privacy-respecting services come into play. Instead of hosting for my neighbours, I would recommend mailbox.org, bitwarden, ente or a hosted nextcloud.

  • Vulnerability Disclosure: Authentication Bypass in Vaultwarden versions < 1.32.5

    Jump

  • The blog post contains an interesting tineline. Apparently, the first fix was not sufficient. So if you have updated Vaultwaren before November 18, update it again.

    Copy of the timeline:

    • End of October 2024: ERNW assesses Vaultwarden for the customer.
    • November 08, 2024: ERNW discloses the vulnerabilities to the Vaultwarden team.
    • November 10, 2024: Fix and release of Vaultwarden v1.32.4.
    • November 11, 2024: ERNW retests the software and identifies that the fix is not sufficient.
    • November 11, 2024: Public merge with fix and request for feedback by the Vaultwarden team.
    • November 12, 2024: ERNW acknowledges that the fix is complete.
    • November 18, 2024: Release of Vaultwarden v1.32.5.

  • Post your setup. no matter how uggo

    Jump

  • My HP has a 65 watt CPU built in, when it's running at full load it is quite loud.

  • Post your setup. no matter how uggo

    Jump

  • Small, 10 inch rack, with some 3D printed rack mounts.

  • VPN bypassing Firewalls (Wireguard DPI)

    Jump

  • Maybe try some TLS-based VPN? This should work almost anywhere, because it looks like a standard HTTPS connection.

    Wireguard - even on port 443 - is special as it uses UDP protocol and not the more widely used TCP protocol.

  • Never throw them out

    Jump

  • Does anyone need some old SCART, VGA, DVI, serial, parallel, USB type B, coax, RJ11 cables? And that's only the stuff I know the names of.

  • Never throw them out

    Jump

  • No dad, YOU never know when you might need them. I know for sure that keeping charging cables and headphones with proprietary connectors will never again be useful.

  • Self Built Home Monitoring System

    Jump

  • I like it :) Can you provide a link to the sensors you used?

  • Immich Public Proxy: Safely share your photos and albums without exposing your Immich instance

    Jump

  • You‘re supposed to host this yourself.

  • Loadbalancing between 2 locations

    Jump

  • Set the DNS cache time to 60 seconds.

    Set the script to run on every host delayed by some time to avoid simultaneously accessing the API (e.g. run the script every other minute).

    With this approach, you get automatic failover in at most 3 minutes.

  • Loadbalancing between 2 locations

    Jump

  • I'd host it on both webservers. The script sets the A record to all the servers that are online. Obviously, the script als has to check it's own service.

    It seems a little hacky though, for a business use case I would use another approach.

  • Loadbalancing between 2 locations

    Jump

  • OP said that they have a static website, this eliminates the need for session sync.

  • Loadbalancing between 2 locations

    Jump

  • Your challenge is that you need a loadbalancer. By hosting the loadbalancer yourself (e.g. on a VPS), you could also host your websites directly there...

    My approach would be DNS-based. You can have multiple DNS A records, and the client picks one of them. With a little script you could remove one of the A Records of that server goes down. This way, you wouldn't need a central hardware.

  • 2024-11-08 - Lemmy Release v0.19.6

    Jump

  • Looks like a small release, but has some IMO pretty interesting changes, like

    Allow users to view their own removed/deleted communities

    and

    Add backend check to enforce hierarchy of admins and mods

  • Where to start as a beginner

    Jump

  • For a start, try hosting something in your own home. A raspberry or an older PC or laptop should be enough.

    My first projects were a print server (so I can print via wifi) and a file server. Try to find something that is useful for you.

    Only start hosting on the internet when you've learned the basics and have more experience.

  • My blog now has Lemmy comments

    Jump

  • It seems like a tedious workflow, but the end result is quite good.

  • My blog now has Lemmy comments

    Jump

  • Interesting. What is tge reasoning behind only fetching the comments vs. a full fediverse integration?