Developer Turns 2017 Pong Experiment into Retro Paddle, a Free Browser Game

·4 views

A developer revisited a simple 2017 canvas Pong prototype in January 2024 and expanded it over almost two years and more than 800 commits. The game now includes over 20 power-ups and power-downs, weapons, portals, sea mines, a computer opponent, and online multiplayer. The developer rotated the playing field vertically so it suits smartphones, with the ball moving top to bottom and the paddle controlled by dragging a finger. The project was renamed Retro Paddle in version 7.0.0 after the developer found that PONG is a registered trademark. The free game runs in the browser on desktop and mobile without an account or installation.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Choosing a Message Broker: Queue, Topic, or Log Defines Your Delivery Contract

Many teams pick a messaging broker based mainly on throughput or cost, but the real decision is about contracts: who owns a message after delivery, how consumer progress is tracked, and whether past events remain available. Queues delete messages once consumed and suit competing workers, topics fan out copies to each subscription, and logs retain events so consumers can replay them by rewinding offsets. Failure handling also differs, since a failing message in a log can stall its partition unless retry mechanisms are built manually. Cloud services map to these primitives differently, for example SNS and Azure Service Bus topics behave unlike each other, and the article recommends publishing once to a topic with a dedicated queue per consumer for isolation.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

How Cameroonians Can Contribute to Cameroon Open Data Using a Simple Online Form

Cameroon Open Data is a community project that gathers local knowledge such as exam questions, proverbs, language translations, laws and facts about places, and stores it openly so students, researchers and future AI tools can use it. Contributors do not need programming skills, since submissions are made by filling in a form on the GitHub website. The guide walks readers through creating a free GitHub account, starring the project repository, and opening the Issues tab to select a suitable form. It explains the available forms, including those for exam questions, texts, translations, facts and recordings or photos, along with the rule that required fields are marked with a red star. Volunteers can also choose a general folder if unsure, and maintainers will place the entry correctly.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Cross-Border Payments and Compliance Guide for Solo Software Developers

Solo developers selling software internationally face challenges around getting paid, meeting tax obligations, and avoiding account freezes. The guide suggests Stripe for general card processing, while merchants of record like Paddle or Lemon Squeezy can absorb VAT and sales tax collection for consumer sales. For B2B clients, invoicing through services such as Wise or Stripe Invoicing is recommended, with customers handling their own VAT reverse-charge. It also explains that VAT on digital services is typically based on the customer's location, and that currency conversion through banks can cost 2–4% per transaction, so multi-currency business accounts are advised. Maintaining clear invoices and separate business and personal accounts is highlighted as essential for compliance.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Why JWT token inspection should run entirely client-side to mitigate CVE-2026-118759

A recently disclosed vulnerability, CVE-2026-118759, involves authentication token leakage and session fixation tied to insecure loopback cookies. Attackers can exploit man-in-the-middle interception when developers paste live production tokens into centralized online formatters. Traditional SaaS formatters may record input headers, session IDs, and user metadata in access logs, exposing secrets. The article recommends verifying tokens entirely in the browser using the standard WebCrypto API so that credentials never leave the local machine. It includes a sample RSA signature verification function and points to RFC 7519 and the W3C Web Cryptography API as reference standards.

0 comments Read more at DEV Community