<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Http Api on ukue.com</title>
    <link>https://ukue.com/tags/http-api/</link>
    <description>Recent content in Http Api on ukue.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 06 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://ukue.com/tags/http-api/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>AI Transcription on a Rented GPU: Python Workers Pull Jobs From ukue Over HTTP</title>
      <link>https://ukue.com/ai-transcription-on-a-rented-gpu-python-workers-pull-jobs-from-ukue-over-http/</link>
      <pubDate>Tue, 06 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://ukue.com/ai-transcription-on-a-rented-gpu-python-workers-pull-jobs-from-ukue-over-http/</guid>
      <description>&lt;p&gt;Say a small podcast-hosting service wants to offer transcripts. Speech-to-text models are quick on a GPU and painfully slow without one, and the service&amp;rsquo;s web server is a modest cloud machine with no GPU. So it rents a GPU server by the month from another provider, and needs a way to hand it work: here&amp;rsquo;s an episode, transcribe it, report back when it&amp;rsquo;s done. Episodes are long, so one job can take ten minutes. And the GPU server might be restarted, or swapped for a bigger one, at any time.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Appointment Reminders With ukue: Jobs Scheduled Days Ahead, Deleted When a Booking Moves</title>
      <link>https://ukue.com/appointment-reminders-with-ukue-jobs-scheduled-days-ahead-deleted-when-a-booking-moves/</link>
      <pubDate>Tue, 06 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://ukue.com/appointment-reminders-with-ukue-jobs-scheduled-days-ahead-deleted-when-a-booking-moves/</guid>
      <description>&lt;p&gt;Picture a hair salon in London that takes bookings online, weeks ahead, and texts every client a reminder 24 hours before the appointment. No-shows cost it money, so the reminders matter. The obvious way to send them is a cron job that wakes up every few minutes and searches the bookings for appointments about a day away. That works until two runs overlap and a client gets two texts, or the server is down at the wrong moment and an hour of reminders never goes out, or a booking moves and the reminder still names the old time.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
