Aussie living in the San Francisco Bay Area.
Coding since 1998.
.NET Foundation member. C# fan
https://d.sb/
Mastodon: @dan@d.sb

  • 1 Post
  • 262 Comments
Joined 3 years ago
cake
Cake day: June 14th, 2023

help-circle



  • cost of AI going up

    The highly subsidized Anthropic and OpenAI subscriptions will go away, but open weight models are getting much better over time - GLM-5.2 and Kimi K3 are both very good.

    The most expensive part by far is training the model. That’s why OpenAI and Anthropic are losing so much money (well, that and the subscriptions).

    With an open weight model, someone has already trained it, and you just have to cover the cost of inference, making it a lot cheaper. Any company (or individual!) with powerful enough equipment can host the model, which means there’s competition in terms of price, compared to something like Claude Opus where the only four hosts (Anthropic, Amazon Bedrock, Google Vertex AI, and Azure AI Foundry) use Anthropic’s pricing.


  • I agree that AI slop is bad, but I don’t really agree with their method of determining if an app is abandoned (no updates in 2-3 months).

    Sometimes apps don’t need updates. Some Linux apps don’t receive major updates for years. I used backupninja (https://0xacab.org/liberate/backupninja) for long time even though sometimes there’s 2-3 years between releases, because it did what I needed. (I switched to Borgmatic at some point though).

    I didn’t update one of my apps for over a year because it already did everything I needed, and I wasn’t receiving any major feature requests. There’s still some bugs I need to fix but I just haven’t gotten around to it yet.


  • And I don’t ever know if it’ll get better because you need to know why you want to build something someway.

    The major issue I’m seeing with junior (and even intermediate) developers is that they trust that the AI will always do things the correct way and don’t question its approach, and they don’t develop proper debugging skills and just rely on the AI to attempt it.

    To get decent quality output out of an AI model, you need to have critical thinking skills, at least basic knowledge of the overall architecture for whatever you’re trying to build, and enough knowledge to question the model when it does something wrong.

    Blindly trusting AI is why so many old security issues are coming back - stored/reflected XSS, SQL injection, exposing databases directly to the internet with no password, things like that. Newer frameworks mostly got rid of them, and now AI is bringing them back. It’s a fun time for red teams at least.




  • This is good to know. I haven’t had issues with using a USB drive though, since it doesn’t receive many reads or writes - the system is copied to a RAM drive on boot and runs off that rather than the USB.

    I assume this means I’d need another drive to boot it from? My current setup is that I have 2 x 22TB drives in a ZFS mirror for data storage, and 2 x 2TB NVMe SSDs in a ZFS mirror for things like VMs, Docker containers, documents, etc.





  • Does it use http or MQTT?

    Home Assistant uses HTTP for this. Realistically, you won’t see much difference between HTTP and MQTT for this use case.

    MQTT is harder to secure than HTTP, and has some limitations (eg it normally only supports username and password auth - no SSO, no 2FA) so I’d avoid it for anything public-facing unless you have a specific reason to use it. Using it via a VPN is fine, but you’d still need to configure a separate MQTT username and password per user.



  • The end goal is to have no reliance on tailscale as i am preparing for the eventual enshitification.

    Tailscale is mostly open-source. If they do anything bad then someone could fork the project. The coordination server isn’t open-source, but you could self-host Headscale as a replacement.

    If it still doesn’t suit your use cases, there’s some alternatives.

    I personally wouldn’t directly deal with iptables or nftables rules, and instead use some other software to deal with that.



  • dan@upvote.autoSelfhosted@lemmy.worldKittygram v1.1 has released
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    2 months ago

    All the data gathered by Cambridge Analytica was gathered through the public API though, after users had consented to share it (by logging into a quiz app that requested the permissions). That’s why the API is very locked down now, and the approval process to get any sort of data access is very strict.

    The main issue was that they gathered data from people whose profiles were set to be visible only to friends. If someone logged into the quiz and granted permissions, their friends’ data was also accessible via the API.


  • dan@upvote.autoSelfhosted@lemmy.worldKittygram v1.1 has released
    link
    fedilink
    English
    arrow-up
    8
    ·
    edit-2
    2 months ago

    aggressively guard

    tbh it’s a hard balance for any social media company.

    Guard content too little and you end up with Cambridge Analytica, which was literally because the public APIs allowed too much access (third-party apps could see any data through the API that you could see through your Facebook account, including friends profiles). You also end up with headlines talking about big data leaks which really just end up being compilations of public data (which has happened to both Facebook and LinkedIn).

    Guard content too much and you restrict users’ freedom too much.


  • It’s not too bad if you use an outbound SMTP relay for sending. SMTP2Go is pretty good, and they have a free plan with 1000 emails per month. I use Mailcow and you can configure relays in their web UI, but it works just as well with the sender_dependent_relayhost_maps setting in Postfix.

    Sure, it’s not fully self-hosted, but the interesting part to self-host is the storage of your emails, not the sending (which will just relay through other SMTP servers along the way anyways).