@onyxflow1: I Built a Dueling Retractable Lightsaber Part 2 Translation carried out with the author’s permission. Author - @herotech.engineering #Озвучка #Перевод #OnyxFlow #video #tiktok #starwarsfan #lightsabers #lightsaber #engineering #handmade

Onyxflow
Onyxflow
Open In TikTok:
Region: UA
Sunday 27 September 2026 10:00:00 GMT
161279
7163
63
113

Music

Download

Comments

hamloy777
Hamloy$ :
а не проще было заставить ленту моргать а не крутить меч
2026-09-27 10:19:35
348
angor42
Ⓐ 🆘angor³⁷🆘☮︎ :
Морти, Он крутится
2026-09-29 14:46:29
1
user9063705042677
Глав. Душнила :
внутри лезвия модно поставить толстый металлический стержень против биения и изгиба
2026-09-27 11:33:32
117
witcherdeleb
deleb :
легче плазму выпускать
2026-09-27 12:59:23
14
ctobnikolaichnevtical
шашлык :
а нельзя сделать чтобы светодиоды внутри крутились?
2026-09-27 11:31:20
24
fur1nadefonta1ne
𝙼𝚒𝚔𝚢 𝚜𝚎𝚔𝚊 :
ну так можно сделать так чтоб было визуально крутилось а не чтоб оно крутилось
2026-09-27 12:23:41
13
kost_maker
кост_ъ :
просто заставь светодиоды слабенько мигать
2026-09-27 15:13:43
1
flike87
Flike :
есть на ютубе?
2026-09-27 11:16:30
0
s.e_k
ПУШИСТЫЙ ЧЕРТИК 🇺🇦 :
лезвие обвисло и стало короче 🥲
2026-09-27 20:07:32
7
qazaq_ww
Qazaq??? :
перешить ленту на то чтобы она моргала рандомно. Да, будет потреблять больше энергии, но тупо поставить батареи по больше и всë
2026-09-27 14:21:23
2
._.andrey.m
🅐🅝🅓🅡🅔🅨 🅖🅔🅝🅘🅤🅢 :
очень странно что они не пытались изменить скорость вращения, может он про это просто не говорит, но если он качается то оно просто входит в резонанс, а там что не делай всё равно будет ломаться и шататься, но если поднять обороты могло бы стать лучше
2026-09-27 21:38:55
1
anarkot4
Anarkot :
вращение
2026-09-27 14:25:11
1
gudronys
Эпштейн :
а в чём проблема вращать не лезвие а светодиоды внутри?
2026-09-27 13:05:10
1
1god_game1
1God_game1 :
переходите на Ютуб Onyxflow , название ролика "создаём невозможный световой меч"
2026-09-27 12:04:23
3
user3160711981070
Nikuliin :
кстати если что есть 3д принтеры из металла, и уж шестерни можно было из металла и сделать
2026-09-28 17:02:21
0
abobus2.028
abobus2.0 :
Тони старых создал мини-реакторы из металлолома
2026-09-27 23:12:29
0
wertandenter
wertandenter :
нет проды 8 минут канал заброшен
2026-09-27 10:08:53
0
ion.bezezcini
ciburec :
🥰😁
2026-09-27 22:22:34
0
airnom6
@airnom :
продууу
2026-09-27 10:46:24
0
purple_hainz
Purple_Hainz :
нельзя было сделать ось внутри лезвия?
2026-09-28 10:00:27
0
gusmavoxniy
￴￴￴￴ ￴￴￴￴￴ ￴￴ ￴ ￴ ￴ :
их шотнет alex burkan
2026-09-27 11:33:14
0
artem_sparta
Умный чел в гп-5 :
пните
2026-09-27 10:51:24
0
gangsterrus_3
Sumrak :
2026-09-27 21:05:58
0
stecosky
Stecovsky :
Еслитды голивуд знал про этого чела то они бы сняли фильм без спец эфектов и у них вышла большая экономия
2026-09-27 20:49:21
0
skulba2
￴ ￴ ￴ ￴ ￴ ￴ ￴ ￴ ￴ ￴ ￴ :
1
2026-09-27 10:14:08
0
To see more videos from user @onyxflow1, please go to the Tikwm homepage.

Other Videos

How to build an entire app with AI, the kind a developer charges $10,000 for You don't need to know how to code to build a real app. You need one idea first: every app has two halves. The restaurant: Front end = the dining room. Everything the customer sees and touches: the menu, the buttons, the booking form. In your app, that's the screens. Back end = the kitchen. The customer never walks in, but that's where the work happens: check the time slot is free, take the payment, save the booking, send the text. Database = the pantry. It stores every customer, every dog, every booking. Close the app, come back next week, and it's all still there. API = the waiter carrying orders between them. The screen asks, the back end answers. Most people only describe the dining room when they ask AI to build something. They get a beautiful app that forgets everything the second they hit refresh. The build, in Claude Code (a dog groomer's booking app): Plan: who it's for, the screens, what the kitchen does and what goes in the pantry, written to a plan file before any code. Front end: the booking page and owner dashboard, previewed in your browser. Point at what's off and it fixes it in seconds. Back end: a free Supabase project gives you two things, a web address for your database and a key. Keys go in one private file called .env: the key drawer in your back office. Then Claude Code connects the booking form and builds the tables. Log-in: email and Google, with Supabase handling the passwords. One rule, row level security: every customer only sees their own bookings. Test it by logging in as two different people. Getting paid: Stripe in test mode (play money). Copy the secret key into the drawer, ask for a $25 deposit with Stripe Checkout, test with 4242 4242 4242 4242. A webhook is Stripe calling your kitchen back to say
How to build an entire app with AI, the kind a developer charges $10,000 for You don't need to know how to code to build a real app. You need one idea first: every app has two halves. The restaurant: Front end = the dining room. Everything the customer sees and touches: the menu, the buttons, the booking form. In your app, that's the screens. Back end = the kitchen. The customer never walks in, but that's where the work happens: check the time slot is free, take the payment, save the booking, send the text. Database = the pantry. It stores every customer, every dog, every booking. Close the app, come back next week, and it's all still there. API = the waiter carrying orders between them. The screen asks, the back end answers. Most people only describe the dining room when they ask AI to build something. They get a beautiful app that forgets everything the second they hit refresh. The build, in Claude Code (a dog groomer's booking app): Plan: who it's for, the screens, what the kitchen does and what goes in the pantry, written to a plan file before any code. Front end: the booking page and owner dashboard, previewed in your browser. Point at what's off and it fixes it in seconds. Back end: a free Supabase project gives you two things, a web address for your database and a key. Keys go in one private file called .env: the key drawer in your back office. Then Claude Code connects the booking form and builds the tables. Log-in: email and Google, with Supabase handling the passwords. One rule, row level security: every customer only sees their own bookings. Test it by logging in as two different people. Getting paid: Stripe in test mode (play money). Copy the secret key into the drawer, ask for a $25 deposit with Stripe Checkout, test with 4242 4242 4242 4242. A webhook is Stripe calling your kitchen back to say "paid". The text reminder plugs in the same way with Twilio. Every outside service connects like this: account, key, drawer, sentence. Go live: push to GitHub, import into Vercel, paste the same keys into its settings, deploy. Buy your domain, add it in Vercel, copy two DNS lines into your domain company, and it's live on your own name with the padlock. Before real customers: point the webhook at the new address and swap test keys for live keys. After that, adding more is one sentence: Google Calendar sync, a loyalty card, review requests, or an automation that drops every new booking into your CRM. Your job becomes the owner who tests every button like a customer would. #buildwithai #claudecode #aiagent

About