Block Together VS cppq

• Community Sharing
  Block Together allows users to share block lists publicly, fostering a community-driven effort to combat harassment and unwanted content on social media platforms.
• User Empowerment
  The tool empowers individuals to create and manage their own block lists, giving them more control over their online experience.
• Privacy Protection
  By automating the blocking process, Block Together helps protect users' privacy and mental well-being by reducing exposure to harmful content.
• Ease of Use
  The platform's interface is user-friendly, making it accessible for individuals who may not be tech-savvy to manage their block lists effectively.

Possible disadvantages

• Overblocking
  There is a risk of overblocking, where shared block lists might include accounts that aren't necessarily harmful, potentially silencing innocent users.
• Platform Dependence
  The effectiveness of Block Together is reliant on its compatibility with specific platforms, meaning it may not work universally across all social media sites.
• Lack of Customization
  While shared lists are useful, they may not cater to individual preferences, leading to a one-size-fits-all approach that may not suit every user's needs.
• Maintenance Requirement
  Block lists require regular updates and maintenance, which can become a time-consuming task for users managing large lists.

• Lightweight C++ implementation
  cppq is written in modern C++ and designed to be a minimal, efficient task queue library, making it a good fit for performance-sensitive applications where the overhead of scripting language runtimes is undesirable.
• Redis-backed reliability
  Built on top of Redis as the message broker, cppq benefits from Redis's persistence, atomic operations, and wide adoption, giving the queue system durability and the ability to survive process restarts.
• Inspired by proven design (asynq)
  The library's architecture mirrors the popular Go asynq task queue, so it inherits a well-thought-out API design for task enqueueing, retries, and worker processing patterns that have already been validated in production systems.
• Native integration for C++ projects
  For teams already working in a C++ codebase, cppq allows adding background job processing without needing to introduce a separate service written in another language (like Go or Python), simplifying the technology stack.
• Open source and inspectable
  Being open source on GitHub, developers can review the source code, modify it for custom needs, and contribute improvements, which offers transparency not available with closed-source queueing solutions.

Possible disadvantages

• Limited maturity and battle-testing
  Compared to established task queue libraries like Sidekiq, Celery, or asynq itself, cppq is a newer and smaller project with less real-world production usage, which may translate into undiscovered bugs or edge cases.
• Smaller community and ecosystem
  Because it has far fewer users and contributors than mainstream task queue systems, finding community support, third-party tutorials, or pre-built integrations is more difficult.
• Documentation gaps
  As a smaller project, cppq may have less comprehensive documentation compared to major task queue frameworks, requiring developers to read source code directly to understand advanced features or edge-case behaviors.
• C++ build and dependency complexity
  Using cppq requires managing C++ build toolchains and dependencies (such as a Redis client library), which can be more cumbersome than installing a package via pip or npm in other ecosystems.
• Fewer built-in features and tooling
  cppq likely lacks the extensive ecosystem tooling of more mature queues, such as web-based monitoring dashboards, extensive metrics/observability integrations, or advanced scheduling features found in more established solutions.

No analysis of Block Together yet.

• Alpine statement regarding receiving huge amounts of hate on social media following the Sprint

  (Put simply, they need to spin back up BlockTogether and then build out the same concept for IG or other platforms.). Source: almost 4 years ago

• Rhea Ripley: Hi, Demi here…. Ya know, the real life human inside Rhea Ripley. Just wanted to point out that WRESTLERS & any form of ENTERTAINER is a real life human off screen. Don’t wish harm on ANYONE. Don’t wish for anyone to be BURIED. Don’t wish for anyone to be FIRED. F’N disgrace.

  I'm wishing Twitter had integrated something like the late Block Together. Get enough top talent subscribing to the block lists of the women in solidarity, and you'd start shifting the gravity. I bet it wouldn't even take that many. Source: over 4 years ago

• I am Sophie Zhang, whistleblower. At FB, I worked to stop major political figures from deceiving their own populace; I became a whistleblower because Facebook turned a blind eye. Ask me anything.

  Formerly, Block Together offered tools to share Twitter block lists. Source: over 5 years ago

View more

Tracking cppq since Nov 2022.