# I am the Watcher. I am your guide through this vast new twtiverse.
#
# Usage:
# https://watcher.sour.is/api/plain/users View list of users and latest twt date.
# https://watcher.sour.is/api/plain/twt View all twts.
# https://watcher.sour.is/api/plain/mentions?uri=:uri View all mentions for uri.
# https://watcher.sour.is/api/plain/conv/:hash View all twts for a conversation subject.
#
# Options:
# uri Filter to show a specific users twts.
# offset Start index for quey.
# limit Count of items to return (going back in time).
#
# twt range = 1 196300
# self = https://watcher.sour.is?offset=166638
# next = https://watcher.sour.is?offset=166738
# prev = https://watcher.sour.is?offset=166538
@prologic I reckon, it's just so that they can say: "Oh, whoopsy daisy. Too bad that you fell for our trap. Sorry, it's entirely your own fault. Go away, leave us alone."
The bullet point 8.6 continues right away (I forgot the ellipsis in my initial quote, excuse me):
> \n Customer agrees that it is Customer’s responsibility to ensure safe use of an Offering and the CrowdStrike Tools in such applications and installations. CROWDSTRIKE DOES NOT WARRANT ANY THIRD PARTY PRODUCTS OR SERVICES.
And in the one before that:
> 8.5 No Guarantee. CUSTOMER ACKNOWLEDGES, UNDERSTANDS, AND AGREES THAT CROWDSTRIKE DOES NOT GUARANTEE OR WARRANT THAT IT WILL FIND, LOCATE, OR DISCOVER ALL OF CUSTOMER’S OR ITS AFFILIATES’ SYSTEM THREATS, VULNERABILITIES, MALWARE, AND MALICIOUS SOFTWARE, AND CUSTOMER AND ITS AFFILIATES WILL NOT HOLD CROWDSTRIKE RESPONSIBLE THEREFOR.
In other words: "Just give us your money and hope for the best. It might work. Maybe." Nope, of course it doesn't.
@prologic I reckon, it's just so that they can say: "Oh, whoopsy daisy. Too bad that you fell for our trap. Sorry, it's entirely your own fault. Go away, leave us alone."
The bullet point 8.6 continues right away (I forgot the ellipsis in my initial quote, excuse me):
> […] Customer agrees that it is Customer’s responsibility to ensure safe use of an Offering and the CrowdStrike Tools in such applications and installations. CROWDSTRIKE DOES NOT WARRANT ANY THIRD PARTY PRODUCTS OR SERVICES.
And in the one before that:
> 8.5 No Guarantee. CUSTOMER ACKNOWLEDGES, UNDERSTANDS, AND AGREES THAT CROWDSTRIKE DOES NOT GUARANTEE OR WARRANT THAT IT WILL FIND, LOCATE, OR DISCOVER ALL OF CUSTOMER’S OR ITS AFFILIATES’ SYSTEM THREATS, VULNERABILITIES, MALWARE, AND MALICIOUS SOFTWARE, AND CUSTOMER AND ITS AFFILIATES WILL NOT HOLD CROWDSTRIKE RESPONSIBLE THEREFOR.
In other words: "Just give us your money and hope for the best. It might work. Maybe." Nope, of course it doesn't.
Thanks, @aelaraji! :-) I nearly missed it, because the shutters are closed to keep the heat out.
[47°09′51″S, 126°43′10″W] Raw reading: 0x669FD381, offset +/-3
❤️ 🎶: Endless Night by Yom
@prologic Most of the things that cause my frustration are things that I can’t change or even avoid. There’s little benefit in complaining about it, I think. 🤔
@prologic Most of the things that cause my frustration are things that I can’t change or even avoid. There’s little benefit in complaining about it, I think. 🤔
@prologic Most of the things that cause my frustration are things that I can’t change or even avoid. There’s little benefit in complaining about it, I think. 🤔
@prologic Most of the things that cause my frustration are things that I can’t change or even avoid. There’s little benefit in complaining about it, I think. 🤔
I’m putting all efforts to switch to Wayland on hold for another 2 years, minimum.
As we all know, writing a Wayland compositor from scratch is next to impossible. Luckily, there’s the wlroots project which aims to build a base library for this task. Basically every compositor except for GNOME and KDE uses it. (This is good! The less fragmentation, the better.)
wlroots is still very volatile, lots of changes with every release. Downstream users (i.e., the projects that write the actual compositor) have to constantly “chase” changes in wlroots. dwl, my favorite compositor at the moment, has recently switched their main branch to target the wlroots *git* version instead of the latest release. My understanding is that they *have* to do this in order to keep up with wlroots (maybe I’m wrong).
Everything is volatile and a moving target.
Why does any of this matter for me? Because I have to eventually fork dwl or at least keep a patch set, and I don’t have the stamina to constantly fiddle with this stuff. I’m running my own X11 window manager, it’s highly specialized, and using just “some Wayland compositor out there” is a *huge* step backward that I’m not willing to take. I tried, it’s just painful and annoying with *zero* benefits.
So … it was fun experimenting with Wayland a bit, but I’m now back to waiting for things to settle down considerably.
I’m putting all efforts to switch to Wayland on hold for another 2 years, minimum.
As we all know, writing a Wayland compositor from scratch is next to impossible. Luckily, there’s the wlroots project which aims to build a base library for this task. Basically every compositor except for GNOME and KDE uses it. (This is good! The less fragmentation, the better.)
wlroots is still very volatile, lots of changes with every release. Downstream users (i.e., the projects that write the actual compositor) have to constantly “chase” changes in wlroots. dwl, my favorite compositor at the moment, has recently switched their main branch to target the wlroots *git* version instead of the latest release. My understanding is that they *have* to do this in order to keep up with wlroots (maybe I’m wrong).
Everything is volatile and a moving target.
Why does any of this matter for me? Because I have to eventually fork dwl or at least keep a patch set, and I don’t have the stamina to constantly fiddle with this stuff. I’m running my own X11 window manager, it’s highly specialized, and using just “some Wayland compositor out there” is a *huge* step backward that I’m not willing to take. I tried, it’s just painful and annoying with *zero* benefits.
So … it was fun experimenting with Wayland a bit, but I’m now back to waiting for things to settle down considerably.
I’m putting all efforts to switch to Wayland on hold for another 2 years, minimum.
As we all know, writing a Wayland compositor from scratch is next to impossible. Luckily, there’s the wlroots project which aims to build a base library for this task. Basically every compositor except for GNOME and KDE uses it. (This is good! The less fragmentation, the better.)
wlroots is still very volatile, lots of changes with every release. Downstream users (i.e., the projects that write the actual compositor) have to constantly “chase” changes in wlroots. dwl, my favorite compositor at the moment, has recently switched their main branch to target the wlroots *git* version instead of the latest release. My understanding is that they *have* to do this in order to keep up with wlroots (maybe I’m wrong).
Everything is volatile and a moving target.
Why does any of this matter for me? Because I have to eventually fork dwl or at least keep a patch set, and I don’t have the stamina to constantly fiddle with this stuff. I’m running my own X11 window manager, it’s highly specialized, and using just “some Wayland compositor out there” is a *huge* step backward that I’m not willing to take. I tried, it’s just painful and annoying with *zero* benefits.
So … it was fun experimenting with Wayland a bit, but I’m now back to waiting for things to settle down considerably.
I’m putting all efforts to switch to Wayland on hold for another 2 years, minimum.
As we all know, writing a Wayland compositor from scratch is next to impossible. Luckily, there’s the wlroots project which aims to build a base library for this task. Basically every compositor except for GNOME and KDE uses it. (This is good! The less fragmentation, the better.)
wlroots is still very volatile, lots of changes with every release. Downstream users (i.e., the projects that write the actual compositor) have to constantly “chase” changes in wlroots. dwl, my favorite compositor at the moment, has recently switched their main branch to target the wlroots *git* version instead of the latest release. My understanding is that they *have* to do this in order to keep up with wlroots (maybe I’m wrong).
Everything is volatile and a moving target.
Why does any of this matter for me? Because I have to eventually fork dwl or at least keep a patch set, and I don’t have the stamina to constantly fiddle with this stuff. I’m running my own X11 window manager, it’s highly specialized, and using just “some Wayland compositor out there” is a *huge* step backward that I’m not willing to take. I tried, it’s just painful and annoying with *zero* benefits.
So … it was fun experimenting with Wayland a bit, but I’m now back to waiting for things to settle down considerably.
❤️ 🎶: Care at All by Anna Josephine
@bender This is sadly all too true 🤣
@bender This is sadly all too true 🤣
@prologic that works fine when interacting with people you know--and they know you--well. On The Tubes it's easy to be misunderstood, or getting a tone other than the intended applied to your message. It easy devolves into a "plonkable" stage. 😅
[47°09′21″S, 126°43′21″W] --white noise--
Base: 9.00 miles, 00:10:07 average pace, 01:31:08 duration
this was a fun one. it was suppose to rain and thunder this morning so i was pretty psyched to get out there. but the storm never came. either way it was a good run.
#running
Base: 9.00 miles, 00:10:07 average pace, 01:31:08 duration
this was a fun one. it was suppose to rain and thunder this morning so i was pretty psyched to get out there. but the storm never came. either way it was a good run.
#running
Base: 9.00 miles, 00:10:07 average pace, 01:31:08 duration
this was a fun one. it was suppose to rain and thunder this morning so i was pretty psyched to get out there. but the storm never came. either way it was a good run.
#running
[47°09′51″S, 126°43′18″W] Reading: 0.52000 PPM
[47°09′08″S, 126°43′55″W] Storm recedes -- back to normal work
@hacker-news-newest this reminds me I need to seriously consider exploring the idea of replacing my Plex set up with Jellyfin
@hacker-news-newest this reminds me I need to seriously consider exploring the idea of replacing my Plex set up with Jellyfin
@lyse so in other words, their own entire sections of global industries that are using this rubbish crowd, strike antivirus/endpoint detection, piece of crap that are infection effectively in violation of the terms of conditions of the service? 🤔
That's some good sleuth thing that @lyse 🙇♂️
@lyse so in other words, their own entire sections of global industries that are using this rubbish crowd, strike antivirus/endpoint detection, piece of crap that are infection effectively in violation of the terms of conditions of the service? 🤔
That's some good sleuth thing that @lyse 🙇♂️
@bender sometimes having the open honest and transparent conversation and discussion is more valuable than anything to be individually gained. 😅 it helps us learn!
@bender sometimes having the open honest and transparent conversation and discussion is more valuable than anything to be individually gained. 😅 it helps us learn!
@movq Who says it's bad stuff or negativity? These are lessons to be learned and things to gain experiences from right?
@movq Who says it's bad stuff or negativity? These are lessons to be learned and things to gain experiences from right?
🧮 USERS:1 FEEDS:2 TWTS:1039 ARCHIVED:76897 CACHE:2317 FOLLOWERS:17 FOLLOWING:14
@movq I do that constantly, on the Fediverse. I often type long replies, disagreeing, or agreeing with someone, read it over and over, just to realise there isn’t anything to gain by it, and scrape it.
@lyse I bet it was! These kinds of sunset shots (with colorful delicious clouds in motion... etc) have always been candy to my eyes. And I know for a fact that the real thing usually looks ten folds better than in pictures (at least in the ones I used to take). Thank you for sharing these!
@lyse I bet it was! These kinds of sunset shots (with colorful delicious clouds in motion... etc) have always been candy to my eyes. And I know for a fact that the real thing usually looks ten folds better than in pictures (at least in the ones I used to take). Thank you for sharing these!
Thank "Human Goodness" for the Gutenberg Project and all the books I'll get to immerse myself into, especially in such hard times 🙏
Thank "Human Goodness" for the Gutenberg Project and all the books I'll get to immerse myself into, especially in such hard times 🙏
[47°09′11″S, 126°43′31″W] Automatic systems disengaged due to heavy rain
@prologic @lyse It’s better this way. 😂 I don’t like all this negativity in tech. We tend to focus on bad aspects too much, imho. Then again, it’s *really easy* to focus on bad stuff, simply because there’s so much of it. 😂
@prologic @lyse It’s better this way. 😂 I don’t like all this negativity in tech. We tend to focus on bad aspects too much, imho. Then again, it’s *really easy* to focus on bad stuff, simply because there’s so much of it. 😂
@prologic @lyse It’s better this way. 😂 I don’t like all this negativity in tech. We tend to focus on bad aspects too much, imho. Then again, it’s *really easy* to focus on bad stuff, simply because there’s so much of it. 😂
@prologic @lyse It’s better this way. 😂 I don’t like all this negativity in tech. We tend to focus on bad aspects too much, imho. Then again, it’s *really easy* to focus on bad stuff, simply because there’s so much of it. 😂
[47°09′26″S, 126°43′07″W] Weather forecast alert -- storm from SW
@movq What a pity for all the effort!
It's also funny to read their terms and conditions:
> 8.6 \n THE OFFERINGS AND CROWDSTRIKE TOOLS ARE NOT FAULT-TOLERANT AND ARE NOT DESIGNED OR INTENDED FOR USE IN ANY HAZARDOUS ENVIRONMENT REQUIRING FAIL-SAFE PERFORMANCE OR OPERATION. NEITHER THE OFFERINGS NOR CROWDSTRIKE TOOLS ARE FOR USE IN THE OPERATION OF AIRCRAFT NAVIGATION, NUCLEAR FACILITIES, COMMUNICATION SYSTEMS, WEAPONS SYSTEMS, DIRECT OR INDIRECT LIFE-SUPPORT SYSTEMS, AIR TRAFFIC CONTROL, OR ANY APPLICATION OR INSTALLATION WHERE FAILURE COULD RESULT IN DEATH, SEVERE PHYSICAL INJURY, OR PROPERTY DAMAGE.
That's why all airports remained operational. Oh wait…
It's also funny to read their terms and conditions:
> 8.6 […] THE OFFERINGS AND CROWDSTRIKE TOOLS ARE NOT FAULT-TOLERANT AND ARE NOT DESIGNED OR INTENDED FOR USE IN ANY HAZARDOUS ENVIRONMENT REQUIRING FAIL-SAFE PERFORMANCE OR OPERATION. NEITHER THE OFFERINGS NOR CROWDSTRIKE TOOLS ARE FOR USE IN THE OPERATION OF AIRCRAFT NAVIGATION, NUCLEAR FACILITIES, COMMUNICATION SYSTEMS, WEAPONS SYSTEMS, DIRECT OR INDIRECT LIFE-SUPPORT SYSTEMS, AIR TRAFFIC CONTROL, OR ANY APPLICATION OR INSTALLATION WHERE FAILURE COULD RESULT IN DEATH, SEVERE PHYSICAL INJURY, OR PROPERTY DAMAGE.
That's why all airports remained operational. Oh wait…
@movq Yeah pretty much ooops 🤦♂️
@movq Yeah pretty much ooops 🤦♂️
@movq Haha 🤣 I might have liked a few, hell even agreed with you on some 🤣
@movq Haha 🤣 I might have liked a few, hell even agreed with you on some 🤣
Today is one of those days where I’m really grumpy and have typed out lots and lots of rants. Luckily, I all deleted them in the end instead of sending them. 😂
Today is one of those days where I’m really grumpy and have typed out lots and lots of rants. Luckily, I all deleted them in the end instead of sending them. 😂
Today is one of those days where I’m really grumpy and have typed out lots and lots of rants. Luckily, I all deleted them in the end instead of sending them. 😂
Today is one of those days where I’m really grumpy and have typed out lots and lots of rants. Luckily, I all deleted them in the end instead of sending them. 😂
@prologic They all gave Crowdstrike root access to their machines. What could possibly go wrong? 🤷🤷🤷
@prologic They all gave Crowdstrike root access to their machines. What could possibly go wrong? 🤷🤷🤷
@prologic They all gave Crowdstrike root access to their machines. What could possibly go wrong? 🤷🤷🤷
@prologic They all gave Crowdstrike root access to their machines. What could possibly go wrong? 🤷🤷🤷
❤️ 🎶: The Moon Has Passed by Lucia
❤️ 🎶: WRITTEN ON A LEAF by JAURIM
❤️ 🎶: I Believe by Lee Soo Young
❤️ 🎶: Second love by CHUU
[47°09′55″S, 126°43′41″W] Transfer aborted
[47°09′57″S, 126°43′34″W] Transfer 25% complete...
❤️ 🎶: As If Nothing Had Happened by Lim Zian
❤️ 🎶: Stay in my memory (Feat. Jisu) by 1014, Jisu
[47°09′32″S, 126°43′45″W] Transponder still failing -- switching to analog communication
❤️ 🎶: 그냥 집에 가자 by 함의림, 다예
❤️ 🎶: Too different by HYUNJI
🧮 USERS:1 FEEDS:2 TWTS:1038 ARCHIVED:76887 CACHE:2330 FOLLOWERS:17 FOLLOWING:14
Small extract:
> "Conceptually, Advanced Data Protection is simple: All CloudKit Service keys that were generated on device and later uploaded to the available-after-authentication iCloud Hardware Security Modules (HSMs) in Apple data centers are deleted from those HSMs and instead kept entirely within the account’s iCloud Keychain protection domain. They are handled like the existing end-to-end encrypted service keys, which means Apple can no longer read or access these keys."
@movq No, no, not snarky at all. That's just their Aussie name. :-)
[47°09′15″S, 126°43′42″W] Transponder jammed
[47°09′43″S, 126°43′10″W] Resetting transponder
@lyse Oh, ok, somehow I thought this was not your thing. 😅 Maybe I was misled by you calling them “Acca Dacca”, which felt somewhat derogative. But I just found @mckinley’s twt gaapgna from a while ago – so this is just normal Aussie slang for AC/DC?! 🤯🥴
@lyse Oh, ok, somehow I thought this was not your thing. 😅 Maybe I was misled by you calling them “Acca Dacca”, which felt somewhat derogative. But I just found @mckinley’s twt gaapgna from a while ago – so this is just normal Aussie slang for AC/DC?! 🤯🥴
@lyse Oh, ok, somehow I thought this was not your thing. 😅 Maybe I was misled by you calling them “Acca Dacca”, which felt somewhat derogative. But I just found @mckinley’s twt gaapgna from a while ago – so this is just normal Aussie slang for AC/DC?! 🤯🥴
@lyse Oh, ok, somehow I thought this was not your thing. 😅 Maybe I was misled by you calling them “Acca Dacca”, which felt somewhat derogative. But I just found @mckinley’s twt gaapgna from a while ago – so this is just normal Aussie slang for AC/DC?! 🤯🥴
@bender i'm thinking it's probably worth to try and implement both features as use for configurable preferences just so that we can see what it's like. 🤣 The default, of course would be the regular pagination that exists now.
@bender i'm thinking it's probably worth to try and implement both features as use for configurable preferences just so that we can see what it's like. 🤣 The default, of course would be the regular pagination that exists now.
@prologic I was going to say, it could be a setting. I prefer infinite scrolling, but I know there is a strong movement against it. 😅
@lyse Heh 😀 This is why we've always implemented features that have differing opinions as either user options, configuration or feature gated 🤣
@lyse Heh 😀 This is why we've always implemented features that have differing opinions as either user options, configuration or feature gated 🤣
@prologic Right, I hate it. I'd stick to regular pagination and page sizes that are reasonable large. But if you think another approach is better, go for it. It's your sofware after all.
[47°09′32″S, 126°43′20″W] Transponder malfunction
@lyse So you neither like "Click to Load" nor "Infinite Scroll" eh? I mean I sort of get it, infinite scroll is kind of annoying as you never really know wtf is going on. Click to Load misses out on "how many pages", "what page you're on", etc. But is it really that bad? 🤔
@lyse So you neither like "Click to Load" nor "Infinite Scroll" eh? I mean I sort of get it, infinite scroll is kind of annoying as you never really know wtf is going on. Click to Load misses out on "how many pages", "what page you're on", etc. But is it really that bad? 🤔
Pinellas County - Long Run: 10.03 miles, 00:10:35 average pace, 01:46:13 duration
hot, humid. first five were great getting back outside. the next five were just trying to keep the HR under 170.
#running
Pinellas County - Long Run: 10.03 miles, 00:10:35 average pace, 01:46:13 duration
hot, humid. first five were great getting back outside. the next five were just trying to keep the HR under 170.
#running
Sunset