#semaphore — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #semaphore, aggregated by home.social.
-
Heads up Port Adelaide folk. Bad stuff is going down, close the windows, don't go to the shops.
See the AlertSA app for latest
<outdated status map removed for public safety>
-
Heads up Port Adelaide folk. Bad stuff is going down, close the windows, don't go to the shops.
See the AlertSA app for latest
<outdated status map removed for public safety>
-
Heads up Port Adelaide folk. Bad stuff is going down, close the windows, don't go to the shops.
See the AlertSA app for latest
<outdated status map removed for public safety>
-
Heads up Port Adelaide folk. Bad stuff is going down, close the windows, don't go to the shops.
See the AlertSA app for latest
<outdated status map removed for public safety>
-
Heads up Port Adelaide folk. Bad stuff is going down, close the windows, don't go to the shops.
See the AlertSA app for latest
<outdated status map removed for public safety>
-
Hmm, I was liking https://enafore.social as a #Semaphore replacement, but I just replied to a local-only post and it set it to federate :flan_facepalm:
(For context, Semaphore doesn't interpret local-only status at all. But if you reply to a local-only post without specifying either way, Hometown will keep your reply local-only. #Enafore does interpret local-only status, but unhelpfully set the reply to federate.)
-
Hmm, I was liking https://enafore.social as a #Semaphore replacement, but I just replied to a local-only post and it set it to federate :flan_facepalm:
(For context, Semaphore doesn't interpret local-only status at all. But if you reply to a local-only post without specifying either way, Hometown will keep your reply local-only. #Enafore does interpret local-only status, but unhelpfully set the reply to federate.)
-
Hmm, I was liking https://enafore.social as a #Semaphore replacement, but I just replied to a local-only post and it set it to federate :flan_facepalm:
(For context, Semaphore doesn't interpret local-only status at all. But if you reply to a local-only post without specifying either way, Hometown will keep your reply local-only. #Enafore does interpret local-only status, but unhelpfully set the reply to federate.)
-
Hmm, I was liking https://enafore.social as a #Semaphore replacement, but I just replied to a local-only post and it set it to federate :flan_facepalm:
(For context, Semaphore doesn't interpret local-only status at all. But if you reply to a local-only post without specifying either way, Hometown will keep your reply local-only. #Enafore does interpret local-only status, but unhelpfully set the reply to federate.)
-
Hmm, I was liking https://enafore.social as a #Semaphore replacement, but I just replied to a local-only post and it set it to federate :flan_facepalm:
(For context, Semaphore doesn't interpret local-only status at all. But if you reply to a local-only post without specifying either way, Hometown will keep your reply local-only. #Enafore does interpret local-only status, but unhelpfully set the reply to federate.)
-
Engineer Cracks Adobe HQ's Longtime Semaphore Puzzle
https://atlas.whatip.xyz/post.php?slug=engineer-cracks-adobe-hqs-longtime-semaphore-puzzle
Latest: <p>For three years
#semaphore #engineer #longtime #cracks -
От потоков к корутинам: как и почему видоизменились примитивы синхронизации в языке Kotlin (Часть 2)
В первой части статьи были рассмотрены следующие распространённые способы организации конкурентного кода при работе с потоками и корутинами: критические секции, атомарные переменные, реактивные переменные, барьерная синхронизация. В этой части будут разобраны другие важные подходы: семафоры, каналы передачи данных, горячие потоки, модель акторов, последовательные обработчики задач, thread confinement. Для каждого из этих подходов рассмотрим конкретные реализации, выделим плюсы и минусы, приведём примеры использования. В конце объединим все реализации в общую таблицу.
https://habr.com/ru/companies/garage8/articles/1049508/
#kotlin #kotlin_coroutines #coroutines #multithreading #concurrency #android #android_development #kotlin_multiplatform #semaphore #actors
-
От потоков к корутинам: как и почему видоизменились примитивы синхронизации в языке Kotlin (Часть 2)
В первой части статьи были рассмотрены следующие распространённые способы организации конкурентного кода при работе с потоками и корутинами: критические секции, атомарные переменные, реактивные переменные, барьерная синхронизация. В этой части будут разобраны другие важные подходы: семафоры, каналы передачи данных, горячие потоки, модель акторов, последовательные обработчики задач, thread confinement. Для каждого из этих подходов рассмотрим конкретные реализации, выделим плюсы и минусы, приведём примеры использования. В конце объединим все реализации в общую таблицу.
https://habr.com/ru/companies/garage8/articles/1049508/
#kotlin #kotlin_coroutines #coroutines #multithreading #concurrency #android #android_development #kotlin_multiplatform #semaphore #actors
-
От потоков к корутинам: как и почему видоизменились примитивы синхронизации в языке Kotlin (Часть 2)
В первой части статьи были рассмотрены следующие распространённые способы организации конкурентного кода при работе с потоками и корутинами: критические секции, атомарные переменные, реактивные переменные, барьерная синхронизация. В этой части будут разобраны другие важные подходы: семафоры, каналы передачи данных, горячие потоки, модель акторов, последовательные обработчики задач, thread confinement. Для каждого из этих подходов рассмотрим конкретные реализации, выделим плюсы и минусы, приведём примеры использования. В конце объединим все реализации в общую таблицу.
https://habr.com/ru/companies/garage8/articles/1049508/
#kotlin #kotlin_coroutines #coroutines #multithreading #concurrency #android #android_development #kotlin_multiplatform #semaphore #actors
-
Golden hour warmth shifting across the coastal ridges.
Semaphore Beach, Semaphore, South Australia.
© All Rights Reserved by Kev Peirce.
#Photo #Photography #Australia #SouthAustralia #Beach #GoldenHour #SunsetPhotography #SandDunes #CoastalErosion #Semaphore #BeachTextures #TwilightSky #WarmLight
-
Golden hour warmth shifting across the coastal ridges.
Semaphore Beach, Semaphore, South Australia.
© All Rights Reserved by Kev Peirce.
#Photo #Photography #Australia #SouthAustralia #Beach #GoldenHour #SunsetPhotography #SandDunes #CoastalErosion #Semaphore #BeachTextures #TwilightSky #WarmLight
-
Golden hour warmth shifting across the coastal ridges.
Semaphore Beach, Semaphore, South Australia.
© All Rights Reserved by Kev Peirce.
#Photo #Photography #Australia #SouthAustralia #Beach #GoldenHour #SunsetPhotography #SandDunes #CoastalErosion #Semaphore #BeachTextures #TwilightSky #WarmLight
-
Golden hour warmth shifting across the coastal ridges.
Semaphore Beach, Semaphore, South Australia.
© All Rights Reserved by Kev Peirce.
#Photo #Photography #Australia #SouthAustralia #Beach #GoldenHour #SunsetPhotography #SandDunes #CoastalErosion #Semaphore #BeachTextures #TwilightSky #WarmLight
-
Golden hour warmth shifting across the coastal ridges.
Semaphore Beach, Semaphore, South Australia.
© All Rights Reserved by Kev Peirce.
#Photo #Photography #Australia #SouthAustralia #Beach #GoldenHour #SunsetPhotography #SandDunes #CoastalErosion #Semaphore #BeachTextures #TwilightSky #WarmLight
-
https://www.europesays.com/fr/993817/ « J’ai eu la lourde tâche de le fermer » : le dernier chef du sémaphore de Villerville #Actualités #caen #chef #dernier #EU #europe #EuropeanUnion #fermer #FR #France #Histoire #lourde #News #RépubliqueFrançaise #revient #sémaphore #site #Taché #UE #UnionEuropéenne #villerville
-
Dead Letter Queue в Kafka на практике
DLQ — это просто топик. Сложное — всё, что вокруг него. Эта статья — про практическую архитектуру обработки событий из Kafka с отправкой данных во внешний REST API. Главная проблема такого сценария — нестабильность внешнего API. Он периодически деградирует по latency или начинает отвечать с ошибками, и это напрямую влияет на пропускную способность всего консьюмера.
https://habr.com/ru/articles/1045324/
#kafka #concurrency #asyncio #semaphore #finite_state_machine #dead_letter_queue #highload #api
-
Dead Letter Queue в Kafka на практике
DLQ — это просто топик. Сложное — всё, что вокруг него. Эта статья — про практическую архитектуру обработки событий из Kafka с отправкой данных во внешний REST API. Главная проблема такого сценария — нестабильность внешнего API. Он периодически деградирует по latency или начинает отвечать с ошибками, и это напрямую влияет на пропускную способность всего консьюмера.
https://habr.com/ru/articles/1045324/
#kafka #concurrency #asyncio #semaphore #finite_state_machine #dead_letter_queue #highload #api
-
Dead Letter Queue в Kafka на практике
DLQ — это просто топик. Сложное — всё, что вокруг него. Эта статья — про практическую архитектуру обработки событий из Kafka с отправкой данных во внешний REST API. Главная проблема такого сценария — нестабильность внешнего API. Он периодически деградирует по latency или начинает отвечать с ошибками, и это напрямую влияет на пропускную способность всего консьюмера.
https://habr.com/ru/articles/1045324/
#kafka #concurrency #asyncio #semaphore #finite_state_machine #dead_letter_queue #highload #api
-
Almost 4 years ago Mastodon, and by extension the Fediverse, became and continues to be essentially my sole social media platform.
A significant factor in this was when I discovered Pinafore and immediately fell in love. You know when you use software that just *feels* right, like Corel Paradox or Turbo Pascal and so on?
I was using Paradox daily at a former employer sixteen years after Corel ceased active development, and it could very well still be in use there today. Pinafore quickly became as vital for me as Paradox was for the more than eight years I worked there.
Unfortunately Pinafore's creator archived the project, but it lives on in various forks, of which I hopped from one to the next as each one eventually became archived, or dormant, or disappeared altogether (Anyone remember Mahoot?).
It's almost like the project is cursed, because I know of at least half a dozen Pinafore variants that all started out with great intentions and noticeable activity but eventually fell silent.
At least.. a year ago maybe? a bug was introduced somewhere along the line that caused buffers to hang if any posts fall under a "hide with warning" filter were found. Watching the spinning circle of dots endlessly loading, refreshing because *sometimes* that fixed things, as it triggered a BPD meltdown in me countless times.
Other issues or lacking vital new features (translation, editing a post, etc.) caused me to very reluctantly try other front-ends but I just couldn't deal with it. I even tried consciously *forcing* myself to use the other ones and despite the aforementioned buffering problem, I found Pinafore and its successors *less* maddening than these other interfaces. (No offense to the other front-ends; they're all amazing projects and work great for some people, but for whatever reasons they just don't work well for me.)
As I mentioned before, the Pinafore-style interface just fit my needs perfectly. So I just continued to be frustrated because I didn't have the knowledge/experience.
Yesterday, however I discovered @dome 's new Pinafore fork, Zocial. (Pinafore -> Semaphore -> Enafore -> Zocial). It's available at https://zocial.ztfr.eu.
True, Zocial is generated using Claude, but this seems like the only practical opportunity for us to have to attain a fully-operational Pinafore-style interface. I honestly believe it's a matter of accessibility because no other front-end has given me the freedom to learn about the Fediverse more than Pinafore.
Maybe I'm being a selfish, neurotic, myopic Goldilocks. I have no rebuttal for those accusations and I apologize for disappointing anyone, but the Fedi is basically my makeshift warm line and I need to keep that as easy for me to use as possible because I can't function without it.
Yes, I know.. "just don't use it!" Yes, I realize if Nolan Lawson had never developed Pinafore, life would go on. Life would also continue if we'd never invented defibrillators, but they sure are handy sometimes.
@dome fixed the above-mentioned bug, and a couple of others, in a matter of minutes today. It feels like finally being rid of a sore tooth. I hadn't realized just how infuriated I was becoming rather than coping.
Look, if someone wants to fork Enafore and repair the bugs that Claude already took care of, I'll almost certainly follow because with all due respect to @dome, I trust a human programmer more than I trust AI output.
However, that just doesn't seem to be possible. We're humans, and humans (understandably) have lives that aren't always congruent to dev plans.
But I personally *need* this interface to work. I love it. Surely I can't be the only one either, with so many people making forks of Pinafore.
So.. it's up to you dear reader (if you're even still awake) to decide if you want to try Zocial, but as for me I've already jumped head-first into it, slop or not.
/end_essay
-
Almost 4 years ago Mastodon, and by extension the Fediverse, became and continues to be essentially my sole social media platform.
A significant factor in this was when I discovered Pinafore and immediately fell in love. You know when you use software that just *feels* right, like Corel Paradox or Turbo Pascal and so on?
I was using Paradox daily at a former employer sixteen years after Corel ceased active development, and it could very well still be in use there today. Pinafore quickly became as vital for me as Paradox was for the more than eight years I worked there.
Unfortunately Pinafore's creator archived the project, but it lives on in various forks, of which I hopped from one to the next as each one eventually became archived, or dormant, or disappeared altogether (Anyone remember Mahoot?).
It's almost like the project is cursed, because I know of at least half a dozen Pinafore variants that all started out with great intentions and noticeable activity but eventually fell silent.
At least.. a year ago maybe? a bug was introduced somewhere along the line that caused buffers to hang if any posts fall under a "hide with warning" filter were found. Watching the spinning circle of dots endlessly loading, refreshing because *sometimes* that fixed things, as it triggered a BPD meltdown in me countless times.
Other issues or lacking vital new features (translation, editing a post, etc.) caused me to very reluctantly try other front-ends but I just couldn't deal with it. I even tried consciously *forcing* myself to use the other ones and despite the aforementioned buffering problem, I found Pinafore and its successors *less* maddening than these other interfaces. (No offense to the other front-ends; they're all amazing projects and work great for some people, but for whatever reasons they just don't work well for me.)
As I mentioned before, the Pinafore-style interface just fit my needs perfectly. So I just continued to be frustrated because I didn't have the knowledge/experience.
Yesterday, however I discovered @dome 's new Pinafore fork, Zocial. (Pinafore -> Semaphore -> Enafore -> Zocial). It's available at https://zocial.ztfr.eu.
True, Zocial is generated using Claude, but this seems like the only practical opportunity for us to have to attain a fully-operational Pinafore-style interface. I honestly believe it's a matter of accessibility because no other front-end has given me the freedom to learn about the Fediverse more than Pinafore.
Maybe I'm being a selfish, neurotic, myopic Goldilocks. I have no rebuttal for those accusations and I apologize for disappointing anyone, but the Fedi is basically my makeshift warm line and I need to keep that as easy for me to use as possible because I can't function without it.
Yes, I know.. "just don't use it!" Yes, I realize if Nolan Lawson had never developed Pinafore, life would go on. Life would also continue if we'd never invented defibrillators, but they sure are handy sometimes.
@dome fixed the above-mentioned bug, and a couple of others, in a matter of minutes today. It feels like finally being rid of a sore tooth. I hadn't realized just how infuriated I was becoming rather than coping.
Look, if someone wants to fork Enafore and repair the bugs that Claude already took care of, I'll almost certainly follow because with all due respect to @dome, I trust a human programmer more than I trust AI output.
However, that just doesn't seem to be possible. We're humans, and humans (understandably) have lives that aren't always congruent to dev plans.
But I personally *need* this interface to work. I love it. Surely I can't be the only one either, with so many people making forks of Pinafore.
So.. it's up to you dear reader (if you're even still awake) to decide if you want to try Zocial, but as for me I've already jumped head-first into it, slop or not.
/end_essay
-
Almost 4 years ago Mastodon, and by extension the Fediverse, became and continues to be essentially my sole social media platform.
A significant factor in this was when I discovered Pinafore and immediately fell in love. You know when you use software that just *feels* right, like Corel Paradox or Turbo Pascal and so on?
I was using Paradox daily at a former employer sixteen years after Corel ceased active development, and it could very well still be in use there today. Pinafore quickly became as vital for me as Paradox was for the more than eight years I worked there.
Unfortunately Pinafore's creator archived the project, but it lives on in various forks, of which I hopped from one to the next as each one eventually became archived, or dormant, or disappeared altogether (Anyone remember Mahoot?).
It's almost like the project is cursed, because I know of at least half a dozen Pinafore variants that all started out with great intentions and noticeable activity but eventually fell silent.
At least.. a year ago maybe? a bug was introduced somewhere along the line that caused buffers to hang if any posts fall under a "hide with warning" filter were found. Watching the spinning circle of dots endlessly loading, refreshing because *sometimes* that fixed things, as it triggered a BPD meltdown in me countless times.
Other issues or lacking vital new features (translation, editing a post, etc.) caused me to very reluctantly try other front-ends but I just couldn't deal with it. I even tried consciously *forcing* myself to use the other ones and despite the aforementioned buffering problem, I found Pinafore and its successors *less* maddening than these other interfaces. (No offense to the other front-ends; they're all amazing projects and work great for some people, but for whatever reasons they just don't work well for me.)
As I mentioned before, the Pinafore-style interface just fit my needs perfectly. So I just continued to be frustrated because I didn't have the knowledge/experience.
Yesterday, however I discovered @dome 's new Pinafore fork, Zocial. (Pinafore -> Semaphore -> Enafore -> Zocial). It's available at https://zocial.ztfr.eu.
True, Zocial is generated using Claude, but this seems like the only practical opportunity for us to have to attain a fully-operational Pinafore-style interface. I honestly believe it's a matter of accessibility because no other front-end has given me the freedom to learn about the Fediverse more than Pinafore.
Maybe I'm being a selfish, neurotic, myopic Goldilocks. I have no rebuttal for those accusations and I apologize for disappointing anyone, but the Fedi is basically my makeshift warm line and I need to keep that as easy for me to use as possible because I can't function without it.
Yes, I know.. "just don't use it!" Yes, I realize if Nolan Lawson had never developed Pinafore, life would go on. Life would also continue if we'd never invented defibrillators, but they sure are handy sometimes.
@dome fixed the above-mentioned bug, and a couple of others, in a matter of minutes today. It feels like finally being rid of a sore tooth. I hadn't realized just how infuriated I was becoming rather than coping.
Look, if someone wants to fork Enafore and repair the bugs that Claude already took care of, I'll almost certainly follow because with all due respect to @dome, I trust a human programmer more than I trust AI output.
However, that just doesn't seem to be possible. We're humans, and humans (understandably) have lives that aren't always congruent to dev plans.
But I personally *need* this interface to work. I love it. Surely I can't be the only one either, with so many people making forks of Pinafore.
So.. it's up to you dear reader (if you're even still awake) to decide if you want to try Zocial, but as for me I've already jumped head-first into it, slop or not.
/end_essay
-
Almost 4 years ago Mastodon, and by extension the Fediverse, became and continues to be essentially my sole social media platform.
A significant factor in this was when I discovered Pinafore and immediately fell in love. You know when you use software that just *feels* right, like Corel Paradox or Turbo Pascal and so on?
I was using Paradox daily at a former employer sixteen years after Corel ceased active development, and it could very well still be in use there today. Pinafore quickly became as vital for me as Paradox was for the more than eight years I worked there.
Unfortunately Pinafore's creator archived the project, but it lives on in various forks, of which I hopped from one to the next as each one eventually became archived, or dormant, or disappeared altogether (Anyone remember Mahoot?).
It's almost like the project is cursed, because I know of at least half a dozen Pinafore variants that all started out with great intentions and noticeable activity but eventually fell silent.
At least.. a year ago maybe? a bug was introduced somewhere along the line that caused buffers to hang if any posts fall under a "hide with warning" filter were found. Watching the spinning circle of dots endlessly loading, refreshing because *sometimes* that fixed things, as it triggered a BPD meltdown in me countless times.
Other issues or lacking vital new features (translation, editing a post, etc.) caused me to very reluctantly try other front-ends but I just couldn't deal with it. I even tried consciously *forcing* myself to use the other ones and despite the aforementioned buffering problem, I found Pinafore and its successors *less* maddening than these other interfaces. (No offense to the other front-ends; they're all amazing projects and work great for some people, but for whatever reasons they just don't work well for me.)
As I mentioned before, the Pinafore-style interface just fit my needs perfectly. So I just continued to be frustrated because I didn't have the knowledge/experience.
Yesterday, however I discovered @dome 's new Pinafore fork, Zocial. (Pinafore -> Semaphore -> Enafore -> Zocial). It's available at https://zocial.ztfr.eu.
True, Zocial is generated using Claude, but this seems like the only practical opportunity for us to have to attain a fully-operational Pinafore-style interface. I honestly believe it's a matter of accessibility because no other front-end has given me the freedom to learn about the Fediverse more than Pinafore.
Maybe I'm being a selfish, neurotic, myopic Goldilocks. I have no rebuttal for those accusations and I apologize for disappointing anyone, but the Fedi is basically my makeshift warm line and I need to keep that as easy for me to use as possible because I can't function without it.
Yes, I know.. "just don't use it!" Yes, I realize if Nolan Lawson had never developed Pinafore, life would go on. Life would also continue if we'd never invented defibrillators, but they sure are handy sometimes.
@dome fixed the above-mentioned bug, and a couple of others, in a matter of minutes today. It feels like finally being rid of a sore tooth. I hadn't realized just how infuriated I was becoming rather than coping.
Look, if someone wants to fork Enafore and repair the bugs that Claude already took care of, I'll almost certainly follow because with all due respect to @dome, I trust a human programmer more than I trust AI output.
However, that just doesn't seem to be possible. We're humans, and humans (understandably) have lives that aren't always congruent to dev plans.
But I personally *need* this interface to work. I love it. Surely I can't be the only one either, with so many people making forks of Pinafore.
So.. it's up to you dear reader (if you're even still awake) to decide if you want to try Zocial, but as for me I've already jumped head-first into it, slop or not.
/end_essay
-
Almost 4 years ago Mastodon, and by extension the Fediverse, became and continues to be essentially my sole social media platform.
A significant factor in this was when I discovered Pinafore and immediately fell in love. You know when you use software that just *feels* right, like Corel Paradox or Turbo Pascal and so on?
I was using Paradox daily at a former employer sixteen years after Corel ceased active development, and it could very well still be in use there today. Pinafore quickly became as vital for me as Paradox was for the more than eight years I worked there.
Unfortunately Pinafore's creator archived the project, but it lives on in various forks, of which I hopped from one to the next as each one eventually became archived, or dormant, or disappeared altogether (Anyone remember Mahoot?).
It's almost like the project is cursed, because I know of at least half a dozen Pinafore variants that all started out with great intentions and noticeable activity but eventually fell silent.
At least.. a year ago maybe? a bug was introduced somewhere along the line that caused buffers to hang if any posts fall under a "hide with warning" filter were found. Watching the spinning circle of dots endlessly loading, refreshing because *sometimes* that fixed things, as it triggered a BPD meltdown in me countless times.
Other issues or lacking vital new features (translation, editing a post, etc.) caused me to very reluctantly try other front-ends but I just couldn't deal with it. I even tried consciously *forcing* myself to use the other ones and despite the aforementioned buffering problem, I found Pinafore and its successors *less* maddening than these other interfaces. (No offense to the other front-ends; they're all amazing projects and work great for some people, but for whatever reasons they just don't work well for me.)
As I mentioned before, the Pinafore-style interface just fit my needs perfectly. So I just continued to be frustrated because I didn't have the knowledge/experience.
Yesterday, however I discovered @dome 's new Pinafore fork, Zocial. (Pinafore -> Semaphore -> Enafore -> Zocial). It's available at https://zocial.ztfr.eu.
True, Zocial is generated using Claude, but this seems like the only practical opportunity for us to have to attain a fully-operational Pinafore-style interface. I honestly believe it's a matter of accessibility because no other front-end has given me the freedom to learn about the Fediverse more than Pinafore.
Maybe I'm being a selfish, neurotic, myopic Goldilocks. I have no rebuttal for those accusations and I apologize for disappointing anyone, but the Fedi is basically my makeshift warm line and I need to keep that as easy for me to use as possible because I can't function without it.
Yes, I know.. "just don't use it!" Yes, I realize if Nolan Lawson had never developed Pinafore, life would go on. Life would also continue if we'd never invented defibrillators, but they sure are handy sometimes.
@dome fixed the above-mentioned bug, and a couple of others, in a matter of minutes today. It feels like finally being rid of a sore tooth. I hadn't realized just how infuriated I was becoming rather than coping.
Look, if someone wants to fork Enafore and repair the bugs that Claude already took care of, I'll almost certainly follow because with all due respect to @dome, I trust a human programmer more than I trust AI output.
However, that just doesn't seem to be possible. We're humans, and humans (understandably) have lives that aren't always congruent to dev plans.
But I personally *need* this interface to work. I love it. Surely I can't be the only one either, with so many people making forks of Pinafore.
So.. it's up to you dear reader (if you're even still awake) to decide if you want to try Zocial, but as for me I've already jumped head-first into it, slop or not.
/end_essay
-
Lunchtime railway project: build a Ratio home semaphore signal with working lantern.
-
Lunchtime railway project: build a Ratio home semaphore signal with working lantern.
-
Lunchtime railway project: build a Ratio home semaphore signal with working lantern.
-
Lunchtime railway project: build a Ratio home semaphore signal with working lantern.
-
Lunchtime railway project: build a Ratio home semaphore signal with working lantern.
-
Ah yes, the riveting tale of #submarines - a topic that's surely on everyone's mind in 2023! 🚤💨 The author dazzles us with groundbreaking #insights like "submarines are old" and "they're kind of like torpedoes." 🤯 Next up: a deep dive into the thrilling world of #semaphore. 🏴☠️📡
https://computer.rip/2026-05-09-extremely-low-frequencies.html #technology #maritime #HackerNews #ngated -
Ah yes, the riveting tale of #submarines - a topic that's surely on everyone's mind in 2023! 🚤💨 The author dazzles us with groundbreaking #insights like "submarines are old" and "they're kind of like torpedoes." 🤯 Next up: a deep dive into the thrilling world of #semaphore. 🏴☠️📡
https://computer.rip/2026-05-09-extremely-low-frequencies.html #technology #maritime #HackerNews #ngated -
Ah yes, the riveting tale of #submarines - a topic that's surely on everyone's mind in 2023! 🚤💨 The author dazzles us with groundbreaking #insights like "submarines are old" and "they're kind of like torpedoes." 🤯 Next up: a deep dive into the thrilling world of #semaphore. 🏴☠️📡
https://computer.rip/2026-05-09-extremely-low-frequencies.html #technology #maritime #HackerNews #ngated -
Ah yes, the riveting tale of #submarines - a topic that's surely on everyone's mind in 2023! 🚤💨 The author dazzles us with groundbreaking #insights like "submarines are old" and "they're kind of like torpedoes." 🤯 Next up: a deep dive into the thrilling world of #semaphore. 🏴☠️📡
https://computer.rip/2026-05-09-extremely-low-frequencies.html #technology #maritime #HackerNews #ngated -
Ah yes, the riveting tale of #submarines - a topic that's surely on everyone's mind in 2023! 🚤💨 The author dazzles us with groundbreaking #insights like "submarines are old" and "they're kind of like torpedoes." 🤯 Next up: a deep dive into the thrilling world of #semaphore. 🏴☠️📡
https://computer.rip/2026-05-09-extremely-low-frequencies.html #technology #maritime #HackerNews #ngated -
📅 Rendez-vous sur #Twitch vendredi 3 avril à 9h30 pour un nouveau Moment GEEK où @FlorentPoinsaut présentera à @tsaquet 4 outils open source et auto-hébergeables : Dashi, Coolify, Maintenant et Semaphore.
-
📅 Rendez-vous sur #Twitch vendredi 3 avril à 9h30 pour un nouveau Moment GEEK où @FlorentPoinsaut présentera à @tsaquet 4 outils open source et auto-hébergeables : Dashi, Coolify, Maintenant et Semaphore.
-
📅 Rendez-vous sur #Twitch vendredi 3 avril à 9h30 pour un nouveau Moment GEEK où @FlorentPoinsaut présentera à @tsaquet 4 outils open source et auto-hébergeables : Dashi, Coolify, Maintenant et Semaphore.
-
Grandeur preserved in stone and iron.
Semaphore, South Australia.
© 𝓐𝓵𝓵 𝓡𝓲𝓰𝓱𝓽𝓼 𝓡𝓮𝓼𝓮𝓻𝓿𝓮𝓭 𝓫𝔂 𝓚𝓮𝓿 𝓟𝓮𝓲𝓻𝓬𝓮.
#Photo #Photography #Australia #SouthAustralia #HistoricHomes #VictorianArchitecture #Semaphore #HeritageBuilding #Ironwork
-
Grandeur preserved in stone and iron.
Semaphore, South Australia.
© 𝓐𝓵𝓵 𝓡𝓲𝓰𝓱𝓽𝓼 𝓡𝓮𝓼𝓮𝓻𝓿𝓮𝓭 𝓫𝔂 𝓚𝓮𝓿 𝓟𝓮𝓲𝓻𝓬𝓮.
#Photo #Photography #Australia #SouthAustralia #HistoricHomes #VictorianArchitecture #Semaphore #HeritageBuilding #Ironwork
-
Grandeur preserved in stone and iron.
Semaphore, South Australia.
© 𝓐𝓵𝓵 𝓡𝓲𝓰𝓱𝓽𝓼 𝓡𝓮𝓼𝓮𝓻𝓿𝓮𝓭 𝓫𝔂 𝓚𝓮𝓿 𝓟𝓮𝓲𝓻𝓬𝓮.
#Photo #Photography #Australia #SouthAustralia #HistoricHomes #VictorianArchitecture #Semaphore #HeritageBuilding #Ironwork
-
Grandeur preserved in stone and iron.
Semaphore, South Australia.
© 𝓐𝓵𝓵 𝓡𝓲𝓰𝓱𝓽𝓼 𝓡𝓮𝓼𝓮𝓻𝓿𝓮𝓭 𝓫𝔂 𝓚𝓮𝓿 𝓟𝓮𝓲𝓻𝓬𝓮.
#Photo #Photography #Australia #SouthAustralia #HistoricHomes #VictorianArchitecture #Semaphore #HeritageBuilding #Ironwork
-
Grandeur preserved in stone and iron.
Semaphore, South Australia.
© 𝓐𝓵𝓵 𝓡𝓲𝓰𝓱𝓽𝓼 𝓡𝓮𝓼𝓮𝓻𝓿𝓮𝓭 𝓫𝔂 𝓚𝓮𝓿 𝓟𝓮𝓲𝓻𝓬𝓮.
#Photo #Photography #Australia #SouthAustralia #HistoricHomes #VictorianArchitecture #Semaphore #HeritageBuilding #Ironwork
-
Grandeur preserved in stone and iron.
Semaphore, South Australia.
© 𝓐𝓵𝓵 𝓡𝓲𝓰𝓱𝓽𝓼 𝓡𝓮𝓼𝓮𝓻𝓿𝓮𝓭 𝓫𝔂 𝟐 𝓟𝓮𝓮𝓹𝓼 𝓪𝓷𝓭 𝓪 𝓒𝓪𝓶𝓮𝓻𝓪.
(𝒟ℴ𝓊𝒷𝓁ℯ 𝓉𝒽ℯ 𝒫ℯℯ𝓅𝓈, 𝒹ℴ𝓊𝒷𝓁ℯ 𝓉𝒽ℯ 𝓅ℯ𝓇𝓈𝓅ℯ𝒸𝓉𝒾𝓋ℯ!)
#Photo #Photography #2PeepsAndACamera #Australia #SouthAustralia #HistoricHomes #VictorianArchitecture #Semaphore #HeritageBuilding #Ironwork
-
Grandeur preserved in stone and iron.
Semaphore, South Australia.
© 𝓐𝓵𝓵 𝓡𝓲𝓰𝓱𝓽𝓼 𝓡𝓮𝓼𝓮𝓻𝓿𝓮𝓭 𝓫𝔂 𝟐 𝓟𝓮𝓮𝓹𝓼 𝓪𝓷𝓭 𝓪 𝓒𝓪𝓶𝓮𝓻𝓪.
(𝒟ℴ𝓊𝒷𝓁ℯ 𝓉𝒽ℯ 𝒫ℯℯ𝓅𝓈, 𝒹ℴ𝓊𝒷𝓁ℯ 𝓉𝒽ℯ 𝓅ℯ𝓇𝓈𝓅ℯ𝒸𝓉𝒾𝓋ℯ!)
#Photo #Photography #2PeepsAndACamera #Australia #SouthAustralia #HistoricHomes #VictorianArchitecture #Semaphore #HeritageBuilding #Ironwork
-
Grandeur preserved in stone and iron.
Semaphore, South Australia.
© 𝓐𝓵𝓵 𝓡𝓲𝓰𝓱𝓽𝓼 𝓡𝓮𝓼𝓮𝓻𝓿𝓮𝓭 𝓫𝔂 𝟐 𝓟𝓮𝓮𝓹𝓼 𝓪𝓷𝓭 𝓪 𝓒𝓪𝓶𝓮𝓻𝓪.
(𝒟ℴ𝓊𝒷𝓁ℯ 𝓉𝒽ℯ 𝒫ℯℯ𝓅𝓈, 𝒹ℴ𝓊𝒷𝓁ℯ 𝓉𝒽ℯ 𝓅ℯ𝓇𝓈𝓅ℯ𝒸𝓉𝒾𝓋ℯ!)
#Photo #Photography #2PeepsAndACamera #Australia #SouthAustralia #HistoricHomes #VictorianArchitecture #Semaphore #HeritageBuilding #Ironwork
-
Grandeur preserved in stone and iron.
Semaphore, South Australia.
© 𝓐𝓵𝓵 𝓡𝓲𝓰𝓱𝓽𝓼 𝓡𝓮𝓼𝓮𝓻𝓿𝓮𝓭 𝓫𝔂 𝟐 𝓟𝓮𝓮𝓹𝓼 𝓪𝓷𝓭 𝓪 𝓒𝓪𝓶𝓮𝓻𝓪.
(𝒟ℴ𝓊𝒷𝓁ℯ 𝓉𝒽ℯ 𝒫ℯℯ𝓅𝓈, 𝒹ℴ𝓊𝒷𝓁ℯ 𝓉𝒽ℯ 𝓅ℯ𝓇𝓈𝓅ℯ𝒸𝓉𝒾𝓋ℯ!)
#Photo #Photography #2PeepsAndACamera #Australia #SouthAustralia #HistoricHomes #VictorianArchitecture #Semaphore #HeritageBuilding #Ironwork
