HDMI-Sync-Box: WiZ bringt Philips-Hue-Konkurrenten für unter 100 Euro https://www.computerbase.de/news/smart-home/hdmi-sync-box-wiz-bringt-philips-hue-konkurrenten-fuer-unter-100-euro.92419/ #Signify #PhilipsHue #WiZ #SmartHome
#Signify
Looking back at being the MC at the Signify VAP online event at the Hilversum TV studio, the Netherlands. #signify #onlineevent #hilversum #masterofceremonies
XXL Lịch Phí Giáng Sinh 2024 (Ngày 15)
XXL Lịch Phí Giáng Sinh 2024 (Ngày 15) Chúng tôi, cùng với Signify, xin được trao tặng một chuỗi đèn nháy WiZ Fairy Lights 20m để tạo nên không khí Giáng sinh rực rỡ. Giải thưởng: 1 x Chuỗi đèn nháy WiZ Fairy Lights 20m #XXLAdventskalender2024 #GiángSinh2024 #QuàTặng #WiZFairyLights #ĐènNháy #Signify #Ngày15 #CuộcThi XXL Adventskalender 2024 (Tür 15) Für festliche Beleuchtung verlosen wir zusammen mit…
https://phukiendinh.com/xxl-lich-phi-giang-sinh-2024-ngay-15
Philips Hue Sync TV App: App-Ersatz für Sync Box nun auch für LG-Fernseher verfügbar https://www.computerbase.de/news/smart-home/philips-hue-sync-tv-app-app-ersatz-fuer-sync-box-nun-auch-fuer-lg-fernseher-verfuegbar.91546/ #Hue #Signify
Show HN: Signify – FOSS tool to generate Email signatures (HTML and PNG)
https://signify.difuse.io
#ycombinator #Signify #Email_Signature #Signature #Email #Difuse #Difuse_io
I submitted a Pull Request to update signify in MacPorts here:
https://github.com/macports/macports-ports/pull/27046
It's a little confusing because: signify doesn't actually have "releases" as it is part of OpenBSD base; and so unlike GameofTrees is not part of /usr/ports and there is no -portable distinction (as with OpenSSH and OpenSMTPD, etc.)
The previous MacPorts' signify maintainer, last updated/synced from upstream circa 2018/2019 I think?
That maintainer, hasn't touched anything on GitHub since 2022.
Quote: "Been on hiatus from open source due to draconian corporate intellectual property policies, and not wanting to expose communities I care about to undue legal risk while bound by them." (from: https://github.com/jpouellet)
There are other "forks" (for lack of a better description) of signify elsewhere on GitHub used by Linux distros by the looks of things; but it seemed as if it would be less friction, to fork jpouellet's signify-osx (renaming my branch/fork to signify-macOS since Apple changed the name of their OS yet again); tweak the Makefile slightly to point to an anoncvs mirror that wasn't timing out (yikes!) and run % make fetch to sync from upstream to pick up whatever changes have occurred in the ensuing years.
I did, for the sake of completeness, also submit a PR to jpoullet's branch here:
https://github.com/jpouellet/signify-osx/pull/9
Though, I guess that got auto-closed by GitHub? Presumably because I changed my local branch to default and renamed it from the time I submitted that Pull Request? smdh I hate GitHub.
Anyhoot. Another oddity I encountered, while I tagged a 1.5 "release" in my fork here: https://github.com/artkiver/signify-macOS/releases/tag/1.5
The tarball I grab from that?
signify-macOS-1.5.tar.gz
Has different check sums and file sizes that the tarball which MacPorts fetches which is called:
artkiver-signify-macOS-1.5-0-g3e9082b.tar.gz
And why that is, I have no idea!
Weird GitHub inconsistencies or something. I have encountered something similar in the past (with ZMap I think?), but I haven't the foggiest idea wtfh it happens, so I figured I would just update the check sums and file size in the Portfile to match the artkiver-signify-macOS-1.5-0-g3e9082b.tar.gz tarball MacPorts grabs, rather than the one that is tagged in my branch.
Anyway, I tested it and it still verifies LibreSSL's tarball OK; so yay?
No idea when that will get merged, since the previous maintainer (who hasn't had any activity on GitHub since 2022) probably won't be chiming in, so it will probably go to "maintainer timeout" and I may need to email macports-dev to have the maintainer removed like I had to do with the previous libressl and libressl-devel maintainer? sigh I will cross that bridge when I get to it I guess.
#signify #MacPorts #OpenSource #OpenBSD #CryptographicSignatures #CodeSigning #cryptography #macOS #OSX #Apple
https://github.com/macports/macports-ports/pull/27046
It's a little confusing because: signify doesn't actually have "releases" as it is part of OpenBSD base; and so unlike GameofTrees is not part of /usr/ports and there is no -portable distinction (as with OpenSSH and OpenSMTPD, etc.)
The previous MacPorts' signify maintainer, last updated/synced from upstream circa 2018/2019 I think?
That maintainer, hasn't touched anything on GitHub since 2022.
Quote: "Been on hiatus from open source due to draconian corporate intellectual property policies, and not wanting to expose communities I care about to undue legal risk while bound by them." (from: https://github.com/jpouellet)
There are other "forks" (for lack of a better description) of signify elsewhere on GitHub used by Linux distros by the looks of things; but it seemed as if it would be less friction, to fork jpouellet's signify-osx (renaming my branch/fork to signify-macOS since Apple changed the name of their OS yet again); tweak the Makefile slightly to point to an anoncvs mirror that wasn't timing out (yikes!) and run % make fetch to sync from upstream to pick up whatever changes have occurred in the ensuing years.
I did, for the sake of completeness, also submit a PR to jpoullet's branch here:
https://github.com/jpouellet/signify-osx/pull/9
Though, I guess that got auto-closed by GitHub? Presumably because I changed my local branch to default and renamed it from the time I submitted that Pull Request? smdh I hate GitHub.
Anyhoot. Another oddity I encountered, while I tagged a 1.5 "release" in my fork here: https://github.com/artkiver/signify-macOS/releases/tag/1.5
The tarball I grab from that?
signify-macOS-1.5.tar.gz
Has different check sums and file sizes that the tarball which MacPorts fetches which is called:
artkiver-signify-macOS-1.5-0-g3e9082b.tar.gz
And why that is, I have no idea!
Weird GitHub inconsistencies or something. I have encountered something similar in the past (with ZMap I think?), but I haven't the foggiest idea wtfh it happens, so I figured I would just update the check sums and file size in the Portfile to match the artkiver-signify-macOS-1.5-0-g3e9082b.tar.gz tarball MacPorts grabs, rather than the one that is tagged in my branch.
Anyway, I tested it and it still verifies LibreSSL's tarball OK; so yay?
No idea when that will get merged, since the previous maintainer (who hasn't had any activity on GitHub since 2022) probably won't be chiming in, so it will probably go to "maintainer timeout" and I may need to email macports-dev to have the maintainer removed like I had to do with the previous libressl and libressl-devel maintainer? sigh I will cross that bridge when I get to it I guess.
#signify #MacPorts #OpenSource #OpenBSD #CryptographicSignatures #CodeSigning #cryptography #macOS #OSX #Apple
Philips hue introduceert augmented reality-functie in app-update https://www.trendingtech.news/trending-news/2024/10/41216/philips-hue-introduceert-augmented-reality-functie-in-app-update #Philips Hue #augmented reality #smart home #Signify #Lidar #Trending #News #Nieuws
Philips hue introduceert augmented reality-functie in app-update https://www.trendingtech.news/trending-news/2024/10/41216/philips-hue-introduceert-augmented-reality-functie-in-app-update #Philips Hue #augmented reality #smart home #Signify #Lidar #Trending #News #Nieuws
Thank you #Signify for f#€king up the #Hue app which suddenly cannot log in to some unnecessary cloud account.
Luckily, thanks to 3rd party apps like iConnectHue and Hue Essentials I can still control my lights.
But can you please stop this #enshittification ?
My impression is that #cryptographers and vulnerability researchers recommend NOT using #PGP for any purpose whatsoever. For example, the Latacora post I shared earlier recommends replacing PGP with
#MagicWormhole for sharing files
#tarsnap for encrypted backups
#Signify or #Minisign for package signing
#libsodium for encrypting application data
#age for encrypting files
I think the idea is to minimize attack surface by using purpose-built tools.
(continues)
Signify hat bekanntgegeben, dass man als Sponsor beim Mercedes-AMG Petronas Formel 1 Team einsteigt. #signify
https://homekits.de/signify-steigt-beim-mercedes-f1-team-ein/
Candles!
Fireplace light effect.
#Hue #PhilipsHue #Philips_Hue #Signify #Lightbulb #Lightbulbs
Philips Hue wird seine Hue Labs Plattform zum Testen neuer Funktionen demnächst einstellen. #philipshue #signify #hue #huelabs
La tecnología LED puede ayudarnos a mejorar la calidad de sueño
#LucesLED #Signify #Salud #LED #Tecnología @SignifyCOL_CAM
https://portalgeek.co/2024/03/la-tecnologia-led-puede-ayudarnos-a-mejorar-la-calidad-de-sueno/
I have now achieved 25 years working at Philips & Signify. Here is a large #infographic which details my favorite ❤️ highlights. #philips #signify #socialmediamarketing #socialmedia #eCommerce #productcatalog #intranet #extranet #socialmediavideo
Wie angekündigt hat Signify jetzt auch die Philips Hue Pendelleuchtenkordel aus dem 3D-Drucker veröffentlicht. #philipshue #hue #signify
https://homekits.de/hue-pendelleuchtenkordel-aus-dem-3d-drucker-erhaeltlich/
Wacht eens, dus #PhilipsHue / #Signify implementeert een communicatieprotocol dat niet afdoende blijkt en gaat consumenten "straffen" door ze te verplichten een account te nemen zodat apparaten met hun servers moeten gaan praten.
Dat impliceert dat de apparaten wel certificate pinning kunnen doen, maar beetje slim pairen met fysieke gebruikers niet? Bijzonder, Bluetooth kan dat al een tijdje.
(Of doen ze zelfs niet aan pinning en kan je ze met DNS trucjes met een lokale server laten praten?)
Ze gaan inderdaad enorm lang mee de Hue LED lampen is mijn ervaring, lastig voor een producent als #Signify #LED
https://nos.nl/artikel/2506310-lampenfabrikant-signify-ex-lichtdivisie-van-philips-schrapt-1000-banen
Client Info
Server: https://mastodon.social
Version: 2025.04
Repository: https://github.com/cyevgeniy/lmst