Urgent.News

What's breaking now, across thousands of outlets.

Tech

too lazy to post too obsessed with building so built slothgram, one Dev one Psot🦥

This is a submission for the Hacktoberfest Open-Source AI Challenge Week 3: Slow and Steady What I Built Slothgram: ONE DEV ONE POST. You ship something, then open four tabs, rewrite the same update four times, pick hashtags, and publish one platform at a time. Slothgram turns that into one step: write the update once, get a separate version for each destination (X, LinkedIn, DEV.to, GitHub),…

This submission for the Hacktoberfest Open-Source AI Challenge Week 3 is titled Slothgram: ONE DEV ONE POST. The builder crafted a tool that enables developers, students, and open-source contributors to create and publish posts to various developer communities with ease. Instead of struggling with repetitive writing and platform-specific formatting, users write the post once and then generate tailored versions for each destination (X, LinkedIn, DEV.to, GitHub).

The tool handles character limits, hashtag counts, and other platform-specific requirements. It uses an open-weight AI model running locally on the user's machine to generate the content, ensuring data privacy and no per-token costs. Temporal handles each destination as a separate, retryable, independent job, with a user-approved workflow to prevent duplicate posts.

The demo runs in the browser with simulated publishing, allowing users to preview the process without actually posting anything.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Three.js Terrain Scatter: Fix Floating, Then Fix Clumping

AI-assisted disclosure: Codex assisted with research, code and writing. Measurements, failure cases and limitations are retained from the original article.

  • BVH accelerated raycasting reduces placement time significantly
  • MeshSurfaceSampler does not guarantee separation of instances
  • Both methods produce clumping of terrain instances

Moving a stop to breakeven in MQL5 without rejected modifies or hidden losses

Moving the stop loss to breakeven once a trade is in profit is one of the most requested Expert Advisor features. It also produces a surprising number of bug reports: the stop never moves, the journal…

  • Stop loss moved to breakeven upon profitability.
  • Correct price used for profit calculation, bid for buy, ask for sell.
  • Breakeven set above entry for buy, below for sell to cover costs.

More from Sunday 25 October →