SDF ARPA member & Saint

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

help-circle
  • For light users, $36/mo is very expensive. However, for middle and upper management types that live, breathe, and eat PowerPoint, this is huge. If this is good enough to allow non-technical people to connect to their BI and generate charts and reports without the need of IT, it will be incredibly cheap to them. There’s a whole cottage industry of consultants for small business who do these sorts of things so having this automated will save time and cost for these businesses.

    As a developer, I’m still interested in seeing what CoPilot integrated in my development environment will be able to do. My company is currently paying for ChatGPT+ at $20/mo for me. At my salary, it’s a no brainer since even an hour a month is a huge ROI. However, it’s quite manual since I have to copy paste everything. If I can get ChatGPT 4 with the full context of my project, $36/mom is a no brainer. If we can get a private version that is trained on our company code base, it will be a game changer.





  • I think this could be very valuable for the community and the Lemmy devs. However, I believe to be successful, there needs to be a volunteer(s) who “sync” the community to the GitHub issues. We could automate this but that would make the situation worse. Here’s how I could imagine this working:

    When a new feature or bug is posted, the mod determines if this is duplicated or not. If so, they will reply to the post with a link to the previous post and lock the current one. If it is truly new, the community can vote and comment. After a week or so, if the community supports the new feature or fixing the bug, the mod will open a new GitHub issue with a summary of the community discussion and link to the discussion.

    This is a lot of work for the mods, but I believe it would really add value for both the Lemmy community and the devs.


  • I think that would only work when the number of instances is small. Two solutions to this might be:

    • have instances act like relays where the home instance of a community notifies 10 instances and then each of those instances notifies 10 instances, etc.
    • batch updates on a timer such that once a minute all posts, comments, boosts, etc within a minutes are buffered and sent together.