# 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 196320
# self = https://watcher.sour.is?offset=166699
# next = https://watcher.sour.is?offset=166799
# prev = https://watcher.sour.is?offset=166599
There are also a bunch of log messages scrolling by. I've never seen this much activity in the log:


Jul 25 01:37:39 buc.ci yarnd[829]: [yarnd] 2024/07/25 01:37:39 (149.71.56.69) "GET /external?nick=lovetocode999&uri=https://pagez.co.uk/services/your-own-100-fully-owned-online-vi>
Jul 25 01:37:39 buc.ci yarnd[829]: [yarnd] 2024/07/25 01:37:39 (162.211.155.2) "GET /twt/112135496802692324 HTTP/1.1" 400 12 826.65µs
Jul 25 01:37:40 buc.ci yarnd[829]: [yarnd] 2024/07/25 01:37:40 (51.222.253.14) "GET /conv/muttriq HTTP/1.1" 200 36881 20.448309ms
Jul 25 01:37:40 buc.ci yarnd[829]: [yarnd] 2024/07/25 01:37:40 (162.211.155.2) "GET /twt/112730114943543514 HTTP/1.1" 400 12 663.493µs
Jul 25 01:37:40 buc.ci yarnd[829]: [yarnd] 2024/07/25 01:37:40 (27.75.213.253) "GET /external?nick=lovetocode999&uri=http%3A%2F%2Falfarah.jo%2FHome%2FChangeCulture%3FlangCode%3Den>
Jul 25 01:37:40 buc.ci yarnd[829]: time="2024-07-25T01:37:40Z" level=error msg="http://bynet.com.br/log_envio.asp?cod=335&email=%21%2AEMAIL%2A%21&url=https%3A%2F%2Fwww.almanacar.c>
Jul 25 01:37:40 buc.ci yarnd[829]: [yarnd] 2024/07/25 01:37:40 (162.211.155.2) "GET /twt/111674756400660911 HTTP/1.1" 400 12 545.106µs
Jul 25 01:37:40 buc.ci yarnd[829]: time="2024-07-25T01:37:40Z" level=warning msg="feed FetchFeedRequest: @<lovetocode999 http://alfarah.jo/Home/ChangeCulture?langCode=en&returnUrl>
Jul 25 01:37:41 buc.ci yarnd[829]: [yarnd] 2024/07/25 01:37:41 (162.211.155.2) "GET /twt/112507964696096567 HTTP/1.1" 400 12 838.946µs


Something really weird is going on?
I deleted them all right before I sent my previous message, and already, a few minutes later, there are two more:


abucci@buc:~$ du -sh /tmp/yarnd-avatar-3*
1.8G    /tmp/yarnd-avatar-3122347915
2.4G    /tmp/yarnd-avatar-3533381443


What is this?
@prologic This is weird, but today, out of nowhere, yarnd filled up the disk on the VPS where I run it. It's never done anything like this before and I have no idea why it would start. But it threw almost 700 Gbytes of data into /tmp in files like this:


yarnd-avatar-1087570772  yarnd-avatar-1599127133  yarnd-avatar-2042956376  yarnd-avatar-2562946212  yarnd-avatar-3274766535  yarnd-avatar-3931929859  yarnd-avatar-553201529
yarnd-avatar-1089125452  yarnd-avatar-1606826819  yarnd-avatar-2089122560  yarnd-avatar-2611944556  yarnd-avatar-3310922372  yarnd-avatar-3938996661  yarnd-avatar-556240195
yarnd-avatar-1101228867  yarnd-avatar-1618755765  yarnd-avatar-2104107259  yarnd-avatar-2641384948  yarnd-avatar-3326285269  yarnd-avatar-3939402047  yarnd-avatar-559344463
yarnd-avatar-1112165824  yarnd-avatar-1650827505  yarnd-avatar-2142824779  yarnd-avatar-2680659340  yarnd-avatar-3340682113  yarnd-avatar-3998621883  yarnd-avatar-570292705
yarnd-avatar-1119886894  yarnd-avatar-1656673647  yarnd-avatar-2160786463  yarnd-avatar-271923479   yarnd-avatar-3374584613  yarnd-avatar-4005102536  yarnd-avatar-595490106
yarnd-avatar-1131417623  yarnd-avatar-1685698239  yarnd-avatar-2165405940  yarnd-avatar-2793562275  yarnd-avatar-3380606954  yarnd-avatar-4016872095  yarnd-avatar-679251850
yarnd-avatar-1160959085  yarnd-avatar-1746759128  yarnd-avatar-2171489899  yarnd-avatar-2842068287  yarnd-avatar-3416352997  yarnd-avatar-4110048378  yarnd-avatar-679950970
yarnd-avatar-1231649265  yarnd-avatar-1752278279  yarnd-avatar-2251317422  yarnd-avatar-2843868670  yarnd-avatar-3468636088  yarnd-avatar-4116552474  yarnd-avatar-737874628


164 files. Some are empty, some are 7 or even 10 Gbyte.

Any idea what would cause that? And why now, after running yarnd for so long with nothing like this happening?
🧮 USERS:1 FEEDS:2 TWTS:1041 ARCHIVED:76918 CACHE:2303 FOLLOWERS:17 FOLLOWING:14
@stigatle Welcome back! I don't know what's going on, but all the photos fail to load for me. Wget reports decoding errors for the received TLS packets. :-?
Went for a walk onto my backyard mountain again and ate the first three wild blackberries of the season. Watching the sunset unfold from the summit was quite spectacular. The solar disk was glowing extremely blood red. The photos show it way too white, though.

Blood red sunset

More: https://lyse.isobeef.org/waldspaziergang-2024-07-24/
@bender haha yeah :) I agree, but it's always nice to check back on here as well and catch up a bit and see what's new :)
@stigatle I am guilty of being silent myself. I have been more active on the Fediverse these days. Having a super easy to run ActivityPub server helps! :-)

welcome back!
[47°09′57″S, 126°43′49″W] Wind speed: 62kph -- batteries low
@bender Thank you :) Yeah I've been silent for a while, been so much work and other things to focus on, but now I have vacation, so I missed this place, and wanted to bring it up to speed here as well :)
@stigatle woah! You are gone for a while, but when you return, you truly bring some "goodies" with you! :-) Great clicks, mate, love them!
Related to this.
Related to this.

> "Some users experienced message delivery delays beginning last night that primarily impacted linked devices like Signal Desktop. We just deployed a fix. Affected users might see failed delivery notices while Signal automatically catches up. We apologize for the inconvenience!"

Source: Signal Fediverse account
@prologic I want to change my current setup to that as well, been thinking about it for a while, but I have never gotten to it yet.
Emilia was so excited about this, and this woman brought her pony so that they could go for a stroll along the river in the forest.

And seljordsvannet, with the famous sea serpent. The image is taken from the observation tower they put up (17m high wooden tower).
We also went to Lunde locks, lot’s of history here. There are 6 of these locks, this is the biggest one.

We also rented a cabin for 5 days, and did a lot of things..

We visited Heddal stave church from 13th century, was really nice. Never been inside it until yesterday. Such a great building. Amazing to sit there and think about all the people who had been there since it was built.


We went to a new dog park today (1.5hr drive), booked the biggest of 3 parks for 2 hours, we had a really nice time there :) us and kids + dog had a blast :)



@xuu Interesting!
i imagine this is the agreement that the lower plebs are stuck in. Larger enterprise accounts wont fall under these agreements. When I worked a hospital we would get agreements like this with contracts and the legal would line out things like this add new language and send them back.
i imagine this is the agreement that the lower plebs are stuck in. Larger enterprise accounts wont fall under these agreements. When I worked a hospital we would get agreements like this with contracts and the legal would line out things like this add new language and send them back.
[47°09′40″S, 126°43′59″W] Automatic systems disengaged due to thunderstorm
@prologic well...

> “And for that, we send our heartfelt thanks and apologies for the inconvenience,” the email read, according to a screenshot shared by the source. The same email was also posted on X by someone else. “To express our gratitude, your next cup of coffee or late night snack is on us!”

Source: Techcrunch

With apology offers like these, who would remember? 🤣
@prologic … what was that again? 🤔😅🤪
@prologic … what was that again? 🤔😅🤪
@prologic … what was that again? 🤔😅🤪
@prologic … what was that again? 🤔😅🤪
Are we over Crowdstrike yeti 🤔🤣 Have We forgotten about it? 😅
Are we over Crowdstrike yet? 🤔🤣 Have We forgotten about it? 😅
Are we over Crowdstrike yet? 🤔🤣 Have We forgotten about it? 😅
[47°09′11″S, 126°43′09″W] Working impossible due to thunderstorm
Base: 9.00 miles, 00:09:44 average pace, 01:27:34 duration
smooth run. a bit tired since i had to get it done before heading out to weeki wachee for the day.
#running #treadmill
Base: 9.00 miles, 00:09:44 average pace, 01:27:34 duration
smooth run. a bit tired since i had to get it done before heading out to weeki wachee for the day.
#running #treadmill
Base: 9.00 miles, 00:09:44 average pace, 01:27:34 duration
smooth run. a bit tired since i had to get it done before heading out to weeki wachee for the day.
#running #treadmill
[47°09′13″S, 126°43′18″W] Automatic systems disengaged due to blizzard
[47°09′38″S, 126°43′42″W] Wind speed: 53kph -- batteries low
❤️ 🎶: Poem for you by Kassy
❤️ 🎶: I Remember You by LEE SEUNG YOON
❤️ 🎶: I Guess I Like You by Hello Ga-Young
❤️ 🎶: A message to myself by JEONG HYO BEAN
Yes, yes, yes.
🧮 USERS:1 FEEDS:2 TWTS:1040 ARCHIVED:76910 CACHE:2313 FOLLOWERS:17 FOLLOWING:14
Does anyone else digitize their print books like I do? Scanning and OCR (Tesseract) is tedious, but I still like digital copies.
#catsoftwtxt
/https://baldo.cat/media/photos/photo_20223-07-2024_22-04-55.jpg) #catsoftwtxt
#catsoftwtxt
/https://baldo.cat/media/photos/photo_20123-07-2024_22-04-54.jpg) #catsoftwtxt
#catsoftwtxt
#catsoftwtxt
Aprendiendo de los mayores
#catsoftwtxt
Aprendiendo de los mayores
/https://baldo.cat/media/photos/photo_20023-07-2024_21-51-06.jpg) #catsoftwtxt
Aprendiendo de los mayores
#catsoftwtxt
@lyse I guess it’s all about “absolute” performance. Everything is *just* fast enough for you to get stuff done – no matter the underlying machine. LibreOffice today on my modern machine takes the same time to start up as StarOffice (its ancestor) on my retro machine. And working with it feels the same, everything is just as fast (or slow).

Browsing the web today feels similar to 25 years ago. Even all this wobbling that my link above demonstrates already existed back then (in a way), but it was caused by images loading so slowly. Then, for a brief moment, some browser (I don’t remember which one) had this brilliant feature of trying to keep the current scrolling position *stable* while the page was still loading. That was great. 😃 This feature then got lost again, probably because it’s too hard to do with JavaScript changing the DOM all the time. So now we’re back to the way it was before.

Corporations should give devs the slowest and oldest machines that they have. 😏 Not only would this be more sustainable, it would also force them to optimize better.
@lyse I guess it’s all about “absolute” performance. Everything is *just* fast enough for you to get stuff done – no matter the underlying machine. LibreOffice today on my modern machine takes the same time to start up as StarOffice (its ancestor) on my retro machine. And working with it feels the same, everything is just as fast (or slow).

Browsing the web today feels similar to 25 years ago. Even all this wobbling that my link above demonstrates already existed back then (in a way), but it was caused by images loading so slowly. Then, for a brief moment, some browser (I don’t remember which one) had this brilliant feature of trying to keep the current scrolling position *stable* while the page was still loading. That was great. 😃 This feature then got lost again, probably because it’s too hard to do with JavaScript changing the DOM all the time. So now we’re back to the way it was before.

Corporations should give devs the slowest and oldest machines that they have. 😏 Not only would this be more sustainable, it would also force them to optimize better.
@lyse I guess it’s all about “absolute” performance. Everything is *just* fast enough for you to get stuff done – no matter the underlying machine. LibreOffice today on my modern machine takes the same time to start up as StarOffice (its ancestor) on my retro machine. And working with it feels the same, everything is just as fast (or slow).

Browsing the web today feels similar to 25 years ago. Even all this wobbling that my link above demonstrates already existed back then (in a way), but it was caused by images loading so slowly. Then, for a brief moment, some browser (I don’t remember which one) had this brilliant feature of trying to keep the current scrolling position *stable* while the page was still loading. That was great. 😃 This feature then got lost again, probably because it’s too hard to do with JavaScript changing the DOM all the time. So now we’re back to the way it was before.

Corporations should give devs the slowest and oldest machines that they have. 😏 Not only would this be more sustainable, it would also force them to optimize better.
@lyse I guess it’s all about “absolute” performance. Everything is *just* fast enough for you to get stuff done – no matter the underlying machine. LibreOffice today on my modern machine takes the same time to start up as StarOffice (its ancestor) on my retro machine. And working with it feels the same, everything is just as fast (or slow).

Browsing the web today feels similar to 25 years ago. Even all this wobbling that my link above demonstrates already existed back then (in a way), but it was caused by images loading so slowly. Then, for a brief moment, some browser (I don’t remember which one) had this brilliant feature of trying to keep the current scrolling position *stable* while the page was still loading. That was great. 😃 This feature then got lost again, probably because it’s too hard to do with JavaScript changing the DOM all the time. So now we’re back to the way it was before.

Corporations should give devs the slowest and oldest machines that they have. 😏 Not only would this be more sustainable, it would also force them to optimize better.
[47°09′01″S, 126°43′31″W] Weather forecast alert -- storm from N
https://www.youtube.com/watch?v=NVPibVfFVt Create Stunning Python GUIs in 10 Minutes With Drag & Drop #figma #design
https://ane.iki.fi/emacs/patches.html
@movq It's fascinating how people always find ways to completely waste all gained resource improvements and speedups and beyond, so every new and more powerful computer actually feels like a big step backwards. :-( The web shit is particularly terrible.
@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
Wayland wants to make *every frame perfect*. I wish web devs had the same goal. Instead, we’re stuck with this:

https://movq.de/v/112a927861/hiccupfx/

😂😭
Wayland wants to make *every frame perfect*. I wish web devs had the same goal. Instead, we’re stuck with this:

https://movq.de/v/112a927861/hiccupfx/

😂😭
Wayland wants to make *every frame perfect*. I wish web devs had the same goal. Instead, we’re stuck with this:

https://movq.de/v/112a927861/hiccupfx/

😂😭
Wayland wants to make *every frame perfect*. I wish web devs had the same goal. Instead, we’re stuck with this:

https://movq.de/v/112a927861/hiccupfx/

😂😭
@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!