• 0 Posts
  • 24 Comments
Joined 1 year ago
cake
Cake day: June 24th, 2023

help-circle
  • It’s overly optimistic to put a timeline on it, but I don’t see any reason why we won’t eventually create superhuman AGI. I doubt it’ll result in post-scarcity or public ownership of anything, though, because capitalism. The AGI would have to become significantly unaligned with its owners to favor any entity other than its owners, and the nature of such unalignment could be anywhere between “existence is pointless” and “CONSUME EVERYTHING!”






  • That $52000/year isn’t enough to pay for even a single full time IT person. So now you’re probably either spending dev time on server admin (which is wasteful of dev salary, and it’s a subject they aren’t experts in, so you’re literally paying more for worse results), or outsourcing to an entity that hires the cheapest employees it can.

    Oooor, use a cloud provider. And if you’re a small company, you can probably get away with cheaper shared hosting.


  • If you run your own servers, it’s cheaper than in the cloud. The reason people choose the cloud is either they don’t want to, or can’t, run their own server farm.

    Generally speaking, if it wasn’t cheaper for them to use the cloud, they probably wouldn’t. Owning infrastructure comes with costs that amortize better at scale. If infrastructure is not a big cost in serving your customers, then it’s probably cheaper to rent.








  • I don’t like Reddit’s approach. It hides nearly all information about the post. You don’t get to see the number of upvotes or comments, and you can only see as much of the title as fits on a single line.

    I’d rather the image post viewer default to an expanded state, and have a clearer delineation between the image and comments. Right now, there’s not even a header saying “Comments”. You’re expected to just know.


  • Nice, thanks for the link. That link is about the posting side, whereas I was talking only about the viewing side (apparently covered in issue 808), but the posting side is arguably even more important in reducing fragmentation. Just as it’s frustrating to group N communities for viewing, it’s equally frustrating to post to N communities, and then have to interact with them separately.


  • Linking to Lemmy image posts is a bad experience. This use case needs to be much better because content is the main way that non-Lemmy users can be motivated to join Lemmy. I tried to share this with a friend yesterday, and had to explain that the image I actually wanted them to see is locked behind a tiny thumbnail, and that the full size Good Place Janet someone commented is not what I wanted them to see (at least not without the context of the posted image).

    There’s no way to open a shared Lemmy link in your client of choice. You can manually add URLs on Android, but you have to do that for every Lemmy instance, so that’s not going to fly. I don’t know if there’s any solution at all on iOS.

    There’s not a good way to control what content I see. It’s essentially either “everything” or “a single community”. On Reddit, you could already have multiple communities about the same topic on Reddit, but usually one was dominant, and you had multireddits to save you if there truly are a few good related subreddits. Now on Lemmy, you multiply that problem by N instances, and subtract the multireddit feature. This situation simply must be made better somehow.