Expensive Chat VS Commit Together by Github

• Unique Experience
  Expensive Chat offers a unique experience by charging money for general conversation, distinguishing itself from free chat platforms.
• Exclusivity
  The higher costs can create an exclusive community, potentially leading to more meaningful and serious interactions.
• Quality Control
  By charging a fee, Expensive Chat may deter spammers and trolls, ensuring higher quality conversations.

Possible disadvantages

• High Cost
  The service can be cost-prohibitive for many people, limiting accessibility based on users' financial situations.
• Niche Audience
  The concept of paying for chat may not appeal to a broad audience, resulting in a smaller user base.
• Value Perception
  Potential users may question the value offered relative to the cost, especially when many chat services are free.

• Enhanced Collaboration
  Commit Together allows multiple authors to be credited in a single commit, which fosters a more collaborative environment and ensures everyone involved receives recognition for their contributions.
• Improved Code Review Process
  With multiple authors clearly listed, reviewers can better understand who contributed to which parts of the code, facilitating more directed questions and discussions.
• Accountability
  By attributing every change to the respective author, teams can easily track who made specific changes, which helps in accountability and understanding the history of a project.
• Efficiency in Pair Programming
  When pair programming, both developers can be credited for their combined effort, streamlining the process of sharing code ownership during collaborative sessions.

Possible disadvantages

• Complex Commit History
  Having multiple authors for a single commit may lead to a more complex commit history, making it harder to pinpoint individual contributions over time.
• Potential Workflow Conflicts
  Teams that are used to single-author commits may experience workflow conflicts or require adjustments in practices to accommodate multi-author contributions.
• Initial Setup Overhead
  Learners and new users might face a learning curve or require additional setup to understand and correctly implement the multi-author commit feature.
• Tooling Compatibility
  Some third-party tools and extensions might not fully support or display multi-author commits, leading to inconsistencies in those environments.

• I bootstrapped BetaList 11 years ago and can't help myself starting new products (WIP.co, Startup.Jobs, BuildInPublic.com, etc). AMA!

  Yes I also made wip.co startup.jobs highscore.money expensive.chat buildinpublic.com pr.co caption.cat getfaces.com requestforstartup.co openmargin.com eatmore.io pushmore.io [😁.to](https://😁.to) linkhyper.com tweet.photo sp-forums.com... Source: almost 5 years ago

• I bootstrapped BetaList 11 years ago and can't help myself starting new products (WIP.co, Startup.Jobs, BuildInPublic.com, etc). AMA!

  And two, try to build a product that is interesting to read about. This may not always be possible, but for example Expensive Chat and Highscore Money were specifically designed to get press coverage. I made sure to make the concept... Source: almost 5 years ago

• Ask HN: Do you rewrite pull requests?

  There is "Co-authored-by" which is supported on GitHub [1] and seems appropriate if the maintainer is basing the solution on someone's code. [1] https://github.blog/2018-01-29-commit-together-with-co-authors/. - Source: Hacker News / over 4 years ago