Skip to content

Releases: motaz-hefny/Distrib_Repo

MoTekLab MetaForge v0.9.1

09 Jun 22:07

Choose a tag to compare

Automated release build of MoTekLab MetaForge v0.9.1.

Installation:

  • Debian/Ubuntu: sudo dpkg -i *amd64.deb
  • Fedora/RPM: sudo rpm -i *x86_64.rpm
  • Standalone: Make the .AppImage executable (chmod +x) and run.

MoTekLab MetaForge v0.9.0

09 Jun 00:07

Choose a tag to compare

Automated release build of MoTekLab MetaForge v0.9.0.

Installation:

  • Debian/Ubuntu: sudo dpkg -i *amd64.deb
  • Fedora/RPM: sudo rpm -i *x86_64.rpm
  • Standalone: Make the .AppImage executable (chmod +x) and run.

MoTekLab MetaForge v0.5.4

04 Jun 22:47

Choose a tag to compare

Automated release build of MoTekLab MetaForge v0.5.4.

Installation:

  • Debian/Ubuntu: sudo dpkg -i *amd64.deb
  • Fedora/RPM: sudo rpm -i *x86_64.rpm
  • Standalone: Make the .AppImage executable (chmod +x) and run.

MoTekLab MetaForge v0.5.3

04 Jun 20:42

Choose a tag to compare

Automated release build of MoTekLab MetaForge v0.5.3.

Installation:

  • Debian/Ubuntu: sudo dpkg -i *amd64.deb
  • Fedora/RPM: sudo rpm -i *x86_64.rpm
  • Standalone: Make the .AppImage executable (chmod +x) and run.

MoTekLab MetaForge v0.5.2

04 Jun 13:02

Choose a tag to compare

Automated release build of MoTekLab MetaForge v0.5.2.

Installation:

  • Debian/Ubuntu: sudo dpkg -i *amd64.deb
  • Fedora/RPM: sudo rpm -i *x86_64.rpm
  • Standalone: Make the .AppImage executable (chmod +x) and run.

MoTekLab MetaForge v0.3.2

03 Jun 18:49

Choose a tag to compare

Release of MoTekLab MetaForge v0.3.2

Linux amd64 packages:

  • .deb (Debian/Ubuntu)
  • .rpm (Fedora/RHEL)

Source: https://github.com/motaz-hefny/MoTekLab-MetaForge

v1.7.1

10 May 19:41

Choose a tag to compare

[1.7.1] - 2026-05-10

Added

  • Arabic concurrency slider entry in help docs — added Q&A for the concurrency slider setting in the Arabic proxy-checker help section.

Changed

  • CHANGELOG and README now include full app description — top of v1.7.0 section and README subtitle now describe the complete proxy lifecycle (harvesting, validation, management, chains, judge, diagnostics, multilingual help) for new users.

v1.7.0

10 May 19:11

Choose a tag to compare

[1.7.0] - 2026-05-10

Changed

  • Keyboard reset uses GDK setEnabled + X11 setFocusable toggle with yield instead of blur/focus — replaced the old setFocusable(false)+blur()+setFocusable(true)+focus() sequence (which changed window Z‑order) with setEnabled(false)+setFocusable(false)setImmediate yield → setFocusable(true)+setEnabled(true)+webContents.focus(). Disables both GTK sensitivity (GDK) and WM_HINTS.input (X11), lets GLib process both disconnections, then re-enables and forces Chromium to register fresh keyboard signal handlers. Z‑order impact: none — the window stays in place.
  • Batch SQLite operations broken into 100-item chunks with setImmediate yieldsperformBatchOperation for delete, updateStatus, updateProtocol, and check now processes proxies in batches of 100, yielding to the event loop between each batch via setImmediate.
  • Proxy checker yields to full event loop between batches — replaced await this.delay(20) with await new Promise(resolve => setImmediate(resolve)) in processQueue().

Added

  • Concurrency slider for Proxy Checkercheck.concurrent setting is now rendered as a <input type="range"> slider (range 5–200, step 5). Concurrency is read from settings when a batch check starts.
  • Automatic keyboard reset restored — since setEnabled+setFocusable toggle has no Z‑order impact, keyboard reset is called automatically after proxy check completion and batch database operations.

Fixed

  • Permanent keyboard freeze triggered by "Cleanup Dead" (batch delete) on Linux — root cause identified as GLib-GObject IME signal handler disconnect (gsignal.c:2685: instance has no handler with id). Three-pronged fix:
    1. Removed confirm() dialogs from handleCleanDead and handleCleanByLatency — the Chromium modal dialog generated focus events that triggered internal IME teardown IPC, which disconnected the GLib keyboard signal handlers.
    2. Switched db:batch IPC from invoke/handle to send/onipcRenderer.invoke() uses the Mojo synchronous IPC path which corrupts GLib state during dispatch. ipcRenderer.send() uses the message path which avoids this.
    3. Added setImmediate yield at start of batch IPC handler — gives GLib time to settle any pending IME/focus events before our handler runs.
  • confirm() dialogs removed from batch delete operations — deleting dead/slow/filtered proxies no longer shows a confirmation dialog, preventing the focus-change→IME-teardown→GLib-corruption sequence. The notification toast on completion provides sufficient feedback.

v1.6.40

10 May 15:06

Choose a tag to compare

Release v1.6.40

v1.6.39

10 May 14:56

Choose a tag to compare

Release v1.6.39