home.social

#highsierra — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #highsierra, aggregated by home.social.

fetched live
  1. Snowy Wren

    I usually associate Rock Wrens with places that are warm year round, but they're actually found all the way up to 10,000 and as far north as British Columbia. These populations migrate downslope or south for the winter. This one must have just returned to the High Sierra, following the melting snow back to its summer home.

    jacquesfortierart.com/2026/07/

  2. “Thundercloud, Ellery Lake, High Sierra, California,” 1934. Photo by Ansel Adams and one of 16 images the United States Postal Service included in its 2024 “Ansel Adams” Forever Stamp release.
    #HighSierra

  3. “Thundercloud, Ellery Lake, High Sierra, California,” 1934. Photo by Ansel Adams and one of 16 images the United States Postal Service included in its 2024 “Ansel Adams” Forever Stamp release.
    #HighSierra

  4. “Thundercloud, Ellery Lake, High Sierra, California,” 1934. Photo by Ansel Adams and one of 16 images the United States Postal Service included in its 2024 “Ansel Adams” Forever Stamp release.
    #HighSierra

  5. “Thundercloud, Ellery Lake, High Sierra, California,” 1934. Photo by Ansel Adams and one of 16 images the United States Postal Service included in its 2024 “Ansel Adams” Forever Stamp release.
    #HighSierra

  6. “Thundercloud, Ellery Lake, High Sierra, California,” 1934. Photo by Ansel Adams and one of 16 images the United States Postal Service included in its 2024 “Ansel Adams” Forever Stamp release.
    #HighSierra

  7. Seu iMac antigo perdeu o brilho depois de instalar um sistema mais novo como o High Sierra?

    Aqui está uma solução simples!

    macnarama.com/imac-2009-sem-br

  8. Este fin de semana he estado experimentando en el rescate de dos #Apple #iMac 2009 que tenía usando con #MacOS #HighSierra ; pero que ya las tenía practicamente abandonadas.

    Se me ocurrió comprar la versión PRO de #ZorinOS y ver que tal se comportaban. Quedé gratamente sorprendido!

    La instalación fue muy sencilla, TODO funciona, cero problema con controladores, y pese a ser equipos Intel Core2duo, funciona de manera muy agil. (1/4)

  9. Este fin de semana he estado experimentando en el rescate de dos #Apple #iMac 2009 que tenía usando con #MacOS #HighSierra ; pero que ya las tenía practicamente abandonadas.

    Se me ocurrió comprar la versión PRO de #ZorinOS y ver que tal se comportaban. Quedé gratamente sorprendido!

    La instalación fue muy sencilla, TODO funciona, cero problema con controladores, y pese a ser equipos Intel Core2duo, funciona de manera muy agil. (1/4)

  10. Este fin de semana he estado experimentando en el rescate de dos #Apple #iMac 2009 que tenía usando con #MacOS #HighSierra ; pero que ya las tenía practicamente abandonadas.

    Se me ocurrió comprar la versión PRO de #ZorinOS y ver que tal se comportaban. Quedé gratamente sorprendido!

    La instalación fue muy sencilla, TODO funciona, cero problema con controladores, y pese a ser equipos Intel Core2duo, funciona de manera muy agil. (1/4)

  11. Este fin de semana he estado experimentando en el rescate de dos #Apple #iMac 2009 que tenía usando con #MacOS #HighSierra ; pero que ya las tenía practicamente abandonadas.

    Se me ocurrió comprar la versión PRO de #ZorinOS y ver que tal se comportaban. Quedé gratamente sorprendido!

    La instalación fue muy sencilla, TODO funciona, cero problema con controladores, y pese a ser equipos Intel Core2duo, funciona de manera muy agil. (1/4)

  12. Este fin de semana he estado experimentando en el rescate de dos #Apple #iMac 2009 que tenía usando con #MacOS #HighSierra ; pero que ya las tenía practicamente abandonadas.

    Se me ocurrió comprar la versión PRO de #ZorinOS y ver que tal se comportaban. Quedé gratamente sorprendido!

    La instalación fue muy sencilla, TODO funciona, cero problema con controladores, y pese a ser equipos Intel Core2duo, funciona de manera muy agil. (1/4)

  13. Are excessive re-writes bad for SSD?

    See "Avoid excessive writes" here darwinsdata.com/how-do-i-fix-a

    I think, my external 2TB #SanDisk SSD just died.
    I use it mainly for analysis of weather station data.
    The usual workflows suspicious of "excessive writes" are:
    once or twice per month download about 1,000 to 10,000 station files, re-format them via scripts. And these scripts delete and re-write each station file multiple times until the procedure is finished.
    That workflow had caused performance degrading on a regular basis. Re-formatting (mostly to exFat) became necessary once every year, then every 6 months, and since December every third month.
    I always just did the re-formatting, without checking for cause or "bad blocks" or anything.

    Today's fail: I had just successfully re-formatted the SSD, this time to JHFS+. The reformatting took >1h, rather slow.
    Afterwards, I tried a restore of a backup **– which luckily had finished successfully, altho also taking an unusually looong time.
    The restore failed with error.
    I then tried re-formatting to JHFS+ again. But this then failed with error. * Tried multiply times with same error.

    Does this history mean I'll just have to replace the SSD every 3 years?
    Can I extend its lifetime somehow?

    Do I need to be cautious wrt frequency of backups to the other SSD? Really don't want to lose that one.. so far, I only write weather-data backups when performance degrades on the weather SSD. But I had thought of doing it more frequently so backups don't take so long.

    * Disk Utility App (GUI) error: Could not write to last block. original in German: "Auf den letzten Block konnte nicht geschrieben werden."

    ** backup software: CarbonCopyCloner
    German posting, same topic:
    climatejustice.social/@anlomed

    #SSD #format #MacOS #HighSierra

  14. Are excessive re-writes bad for SSD?

    See "Avoid excessive writes" here darwinsdata.com/how-do-i-fix-a

    I think, my external 2TB #SanDisk SSD just died.
    I use it mainly for analysis of weather station data.
    The usual workflows suspicious of "excessive writes" are:
    once or twice per month download about 1,000 to 10,000 station files, re-format them via scripts. And these scripts delete and re-write each station file multiple times until the procedure is finished.
    That workflow had caused performance degrading on a regular basis. Re-formatting (mostly to exFat) became necessary once every year, then every 6 months, and since December every third month.
    I always just did the re-formatting, without checking for cause or "bad blocks" or anything.

    Today's fail: I had just successfully re-formatted the SSD, this time to JHFS+. The reformatting took >1h, rather slow.
    Afterwards, I tried a restore of a backup **– which luckily had finished successfully, altho also taking an unusually looong time.
    The restore failed with error.
    I then tried re-formatting to JHFS+ again. But this then failed with error. * Tried multiply times with same error.

    Does this history mean I'll just have to replace the SSD every 3 years?
    Can I extend its lifetime somehow?

    Do I need to be cautious wrt frequency of backups to the other SSD? Really don't want to lose that one.. so far, I only write weather-data backups when performance degrades on the weather SSD. But I had thought of doing it more frequently so backups don't take so long.

    * Disk Utility App (GUI) error: Could not write to last block. original in German: "Auf den letzten Block konnte nicht geschrieben werden."

    ** backup software: CarbonCopyCloner
    German posting, same topic:
    climatejustice.social/@anlomed

    #SSD #format #MacOS #HighSierra

  15. Are excessive re-writes bad for SSD?

    See "Avoid excessive writes" here darwinsdata.com/how-do-i-fix-a

    I think, my external 2TB #SanDisk SSD just died.
    I use it mainly for analysis of weather station data.
    The usual workflows suspicious of "excessive writes" are:
    once or twice per month download about 1,000 to 10,000 station files, re-format them via scripts. And these scripts delete and re-write each station file multiple times until the procedure is finished.
    That workflow had caused performance degrading on a regular basis. Re-formatting (mostly to exFat) became necessary once every year, then every 6 months, and since December every third month.
    I always just did the re-formatting, without checking for cause or "bad blocks" or anything.

    Today's fail: I had just successfully re-formatted the SSD, this time to JHFS+. The reformatting took >1h, rather slow.
    Afterwards, I tried a restore of a backup **– which luckily had finished successfully, altho also taking an unusually looong time.
    The restore failed with error.
    I then tried re-formatting to JHFS+ again. But this then failed with error. * Tried multiply times with same error.

    Does this history mean I'll just have to replace the SSD every 3 years?
    Can I extend its lifetime somehow?

    Do I need to be cautious wrt frequency of backups to the other SSD? Really don't want to lose that one.. so far, I only write weather-data backups when performance degrades on the weather SSD. But I had thought of doing it more frequently so backups don't take so long.

    * Disk Utility App (GUI) error: Could not write to last block. original in German: "Auf den letzten Block konnte nicht geschrieben werden."

    ** backup software: CarbonCopyCloner
    German posting, same topic:
    climatejustice.social/@anlomed

    #SSD #format #MacOS #HighSierra

  16. Are excessive re-writes bad for SSD?

    See "Avoid excessive writes" here darwinsdata.com/how-do-i-fix-a

    I think, my external 2TB #SanDisk SSD just died.
    I use it mainly for analysis of weather station data.
    The usual workflows suspicious of "excessive writes" are:
    once or twice per month download about 1,000 to 10,000 station files, re-format them via scripts. And these scripts delete and re-write each station file multiple times until the procedure is finished.
    That workflow had caused performance degrading on a regular basis. Re-formatting (mostly to exFat) became necessary once every year, then every 6 months, and since December every third month.
    I always just did the re-formatting, without checking for cause or "bad blocks" or anything.

    Today's fail: I had just successfully re-formatted the SSD, this time to JHFS+. The reformatting took >1h, rather slow.
    Afterwards, I tried a restore of a backup **– which luckily had finished successfully, altho also taking an unusually looong time.
    The restore failed with error.
    I then tried re-formatting to JHFS+ again. But this then failed with error. * Tried multiply times with same error.

    Does this history mean I'll just have to replace the SSD every 3 years?
    Can I extend its lifetime somehow?

    Do I need to be cautious wrt frequency of backups to the other SSD? Really don't want to lose that one.. so far, I only write weather-data backups when performance degrades on the weather SSD. But I had thought of doing it more frequently so backups don't take so long.

    * Disk Utility App (GUI) error: Could not write to last block. original in German: "Auf den letzten Block konnte nicht geschrieben werden."

    ** backup software: CarbonCopyCloner
    German posting, same topic:
    climatejustice.social/@anlomed

    #SSD #format #MacOS #HighSierra

  17. what is a good browser for in 2025? so far only palemoon still supports it

  18. I have never been more frustrated trying to install an #OS as I have today with #MacOS. Can't install via Recovery. Won't install using a bootable USB. Guess I'll mess with it more later.

    #Apple #HighSierra #Garbage

  19. One of my colleagues works remotely and used to do occasional testing on a #Mac. However the Mac he had was left lying around since it was stuck on 10.13 and hence has not been getting security updates since November 12, 2020 and has not even been usable with Vivaldi for a long while also.

    We are sending him a newer Apple Silicon based Mac (since that would also allow easier testing of internal builds using iOS simulator) but in the mean time I pointed out that he could upgrade his current machine with #OpenCoreLegacyPatcher, despite Apple preventing upgraded via the regular method.

    He went all the way from #macOS #HighSierra 10.13, right up to macOS 15 #Sequoia without any obvious issues. Once again, it is silly that Apple is letting these working machines just be wasted.

    #OCLP

  20. One of my colleagues works remotely and used to do occasional testing on a #Mac. However the Mac he had was left lying around since it was stuck on 10.13 and hence has not been getting security updates since November 12, 2020 and has not even been usable with Vivaldi for a long while also.

    We are sending him a newer Apple Silicon based Mac (since that would also allow easier testing of internal builds using iOS simulator) but in the mean time I pointed out that he could upgrade his current machine with #OpenCoreLegacyPatcher, despite Apple preventing upgraded via the regular method.

    He went all the way from #macOS #HighSierra 10.13, right up to macOS 15 #Sequoia without any obvious issues. Once again, it is silly that Apple is letting these working machines just be wasted.

    #OCLP

  21. One of my colleagues works remotely and used to do occasional testing on a #Mac. However the Mac he had was left lying around since it was stuck on 10.13 and hence has not been getting security updates since November 12, 2020 and has not even been usable with Vivaldi for a long while also.

    We are sending him a newer Apple Silicon based Mac (since that would also allow easier testing of internal builds using iOS simulator) but in the mean time I pointed out that he could upgrade his current machine with #OpenCoreLegacyPatcher, despite Apple preventing upgraded via the regular method.

    He went all the way from #macOS #HighSierra 10.13, right up to macOS 15 #Sequoia without any obvious issues. Once again, it is silly that Apple is letting these working machines just be wasted.

    #OCLP

  22. One of my colleagues works remotely and used to do occasional testing on a #Mac. However the Mac he had was left lying around since it was stuck on 10.13 and hence has not been getting security updates since November 12, 2020 and has not even been usable with Vivaldi for a long while also.

    We are sending him a newer Apple Silicon based Mac (since that would also allow easier testing of internal builds using iOS simulator) but in the mean time I pointed out that he could upgrade his current machine with #OpenCoreLegacyPatcher, despite Apple preventing upgraded via the regular method.

    He went all the way from #macOS #HighSierra 10.13, right up to macOS 15 #Sequoia without any obvious issues. Once again, it is silly that Apple is letting these working machines just be wasted.

    #OCLP

  23. One of my colleagues works remotely and used to do occasional testing on a #Mac. However the Mac he had was left lying around since it was stuck on 10.13 and hence has not been getting security updates since November 12, 2020 and has not even been usable with Vivaldi for a long while also.

    We are sending him a newer Apple Silicon based Mac (since that would also allow easier testing of internal builds using iOS simulator) but in the mean time I pointed out that he could upgrade his current machine with #OpenCoreLegacyPatcher, despite Apple preventing upgraded via the regular method.

    He went all the way from #macOS #HighSierra 10.13, right up to macOS 15 #Sequoia without any obvious issues. Once again, it is silly that Apple is letting these working machines just be wasted.

    #OCLP

  24. I have an old #MacbookAir from 2010 that's been unused for years now since the Magsafe 1 power cable broke. So I bought a USBC to Magsafe1 adapter and the computer came to life.

    But I needed to reinstall the MBA and the recovery mode can't download the #OSX #HighSierra Image for some reason.

    Found a solution here: mrmacintosh.com/how-to-fix-the

    The https address don't work but works via http. So setting the right #NVRAM variable like this it works!

    nvram IASUCatalogURL="swscan.apple.com/content/catal"

  25. I have an old #MacbookAir from 2010 that's been unused for years now since the Magsafe 1 power cable broke. So I bought a USBC to Magsafe1 adapter and the computer came to life.

    But I needed to reinstall the MBA and the recovery mode can't download the #OSX #HighSierra Image for some reason.

    Found a solution here: mrmacintosh.com/how-to-fix-the

    The https address don't work but works via http. So setting the right #NVRAM variable like this it works!

    nvram IASUCatalogURL="swscan.apple.com/content/catal"

  26. I have an old #MacbookAir from 2010 that's been unused for years now since the Magsafe 1 power cable broke. So I bought a USBC to Magsafe1 adapter and the computer came to life.

    But I needed to reinstall the MBA and the recovery mode can't download the #OSX #HighSierra Image for some reason.

    Found a solution here: mrmacintosh.com/how-to-fix-the

    The https address don't work but works via http. So setting the right #NVRAM variable like this it works!

    nvram IASUCatalogURL="swscan.apple.com/content/catal"

  27. I have an old #MacbookAir from 2010 that's been unused for years now since the Magsafe 1 power cable broke. So I bought a USBC to Magsafe1 adapter and the computer came to life.

    But I needed to reinstall the MBA and the recovery mode can't download the #OSX #HighSierra Image for some reason.

    Found a solution here: mrmacintosh.com/how-to-fix-the

    The https address don't work but works via http. So setting the right #NVRAM variable like this it works!

    nvram IASUCatalogURL="swscan.apple.com/content/catal"

  28. I have an old #MacbookAir from 2010 that's been unused for years now since the Magsafe 1 power cable broke. So I bought a USBC to Magsafe1 adapter and the computer came to life.

    But I needed to reinstall the MBA and the recovery mode can't download the #OSX #HighSierra Image for some reason.

    Found a solution here: mrmacintosh.com/how-to-fix-the

    The https address don't work but works via http. So setting the right #NVRAM variable like this it works!

    nvram IASUCatalogURL="swscan.apple.com/content/catal"

  29. #RightToRepair must include software backward compatibility.

    This is ... not nice.
    I don't want to use the web in Safari just because my home instance Mastodon killed its compatibility with my Vivaldi browser version last night.
    Do I have to move to a non-Mastodon instance?

    Vivaldi 5 from 2023: Mastodon is unusable due to notifications and advanced view not opening.
    Safari 13: mangled display for notifications and considerable delay in first-time-actions, but then usable.

    Some detailed error reporting follows. cc @PaulaToThePeople

    #MastoAdmin

    My home Instance, #Mastodon version v4.3.1-stable+ff1 no longer displays notifications: "The requested page could not be rendered."

    Opening the advanced deck view fails with "Due to a bug in our code or a browser compatibility issue, this page could not be displayed correctly."

    Home feed and lists display okay.

    Browser #Vivaldi 5.7. – older version from 2023.
    Just updated to 5.8, apparently the last Vivaldi version compatible with my Mac: same issues.
    Current would be 7.x. which doesn't run on my #MacOS 13 #HighSierra from 2019.

    Safari 13.1 works okay-ish with notifications, although display of liked and boosted posts is mangled.

    It seems to time out without error on opening preferences. But after 5mins or so, it does open and also displays the advanced view correctly, tho with the mangled notifications.
    Opening a random oldish toot from within one of the columns won't display the toot, just an empty column, no error. Opening a new toot from 5mins ago displays immediately.
    Re-opening the oldish toot then displays fine.
    And it first doesn't open the window for emoticons. No error. Just doesn't react to mouse clicks.

    Reply to a toot works. Upon edit of the reply, the emoticon window suddenly displays normally and does so after that.

  30. #RightToRepair must include software backward compatibility.

    This is ... not nice.
    I don't want to use the web in Safari just because my home instance Mastodon killed its compatibility with my Vivaldi browser version last night.
    Do I have to move to a non-Mastodon instance?

    Vivaldi 5 from 2023: Mastodon is unusable due to notifications and advanced view not opening.
    Safari 13: mangled display for notifications and considerable delay in first-time-actions, but then usable.

    Some detailed error reporting follows. cc @PaulaToThePeople

    #MastoAdmin

    My home Instance, #Mastodon version v4.3.1-stable+ff1 no longer displays notifications: "The requested page could not be rendered."

    Opening the advanced deck view fails with "Due to a bug in our code or a browser compatibility issue, this page could not be displayed correctly."

    Home feed and lists display okay.

    Browser #Vivaldi 5.7. – older version from 2023.
    Just updated to 5.8, apparently the last Vivaldi version compatible with my Mac: same issues.
    Current would be 7.x. which doesn't run on my #MacOS 13 #HighSierra from 2019.

    Safari 13.1 works okay-ish with notifications, although display of liked and boosted posts is mangled.

    It seems to time out without error on opening preferences. But after 5mins or so, it does open and also displays the advanced view correctly, tho with the mangled notifications.
    Opening a random oldish toot from within one of the columns won't display the toot, just an empty column, no error. Opening a new toot from 5mins ago displays immediately.
    Re-opening the oldish toot then displays fine.
    And it first doesn't open the window for emoticons. No error. Just doesn't react to mouse clicks.

    Reply to a toot works. Upon edit of the reply, the emoticon window suddenly displays normally and does so after that.

  31. #RightToRepair must include software backward compatibility.

    This is ... not nice.
    I don't want to use the web in Safari just because my home instance Mastodon killed its compatibility with my Vivaldi browser version last night.
    Do I have to move to a non-Mastodon instance?

    Vivaldi 5 from 2023: Mastodon is unusable due to notifications and advanced view not opening.
    Safari 13: mangled display for notifications and considerable delay in first-time-actions, but then usable.

    Some detailed error reporting follows. cc @PaulaToThePeople

    #MastoAdmin

    My home Instance, #Mastodon version v4.3.1-stable+ff1 no longer displays notifications: "The requested page could not be rendered."

    Opening the advanced deck view fails with "Due to a bug in our code or a browser compatibility issue, this page could not be displayed correctly."

    Home feed and lists display okay.

    Browser #Vivaldi 5.7. – older version from 2023.
    Just updated to 5.8, apparently the last Vivaldi version compatible with my Mac: same issues.
    Current would be 7.x. which doesn't run on my #MacOS 13 #HighSierra from 2019.

    Safari 13.1 works okay-ish with notifications, although display of liked and boosted posts is mangled.

    It seems to time out without error on opening preferences. But after 5mins or so, it does open and also displays the advanced view correctly, tho with the mangled notifications.
    Opening a random oldish toot from within one of the columns won't display the toot, just an empty column, no error. Opening a new toot from 5mins ago displays immediately.
    Re-opening the oldish toot then displays fine.
    And it first doesn't open the window for emoticons. No error. Just doesn't react to mouse clicks.

    Reply to a toot works. Upon edit of the reply, the emoticon window suddenly displays normally and does so after that.

  32. #RightToRepair must include software backward compatibility.

    This is ... not nice.
    I don't want to use the web in Safari just because my home instance Mastodon killed its compatibility with my Vivaldi browser version last night.
    Do I have to move to a non-Mastodon instance?

    Vivaldi 5 from 2023: Mastodon is unusable due to notifications and advanced view not opening.
    Safari 13: mangled display for notifications and considerable delay in first-time-actions, but then usable.

    Some detailed error reporting follows. cc @PaulaToThePeople

    #MastoAdmin

    My home Instance, #Mastodon version v4.3.1-stable+ff1 no longer displays notifications: "The requested page could not be rendered."

    Opening the advanced deck view fails with "Due to a bug in our code or a browser compatibility issue, this page could not be displayed correctly."

    Home feed and lists display okay.

    Browser #Vivaldi 5.7. – older version from 2023.
    Just updated to 5.8, apparently the last Vivaldi version compatible with my Mac: same issues.
    Current would be 7.x. which doesn't run on my #MacOS 13 #HighSierra from 2019.

    Safari 13.1 works okay-ish with notifications, although display of liked and boosted posts is mangled.

    It seems to time out without error on opening preferences. But after 5mins or so, it does open and also displays the advanced view correctly, tho with the mangled notifications.
    Opening a random oldish toot from within one of the columns won't display the toot, just an empty column, no error. Opening a new toot from 5mins ago displays immediately.
    Re-opening the oldish toot then displays fine.
    And it first doesn't open the window for emoticons. No error. Just doesn't react to mouse clicks.

    Reply to a toot works. Upon edit of the reply, the emoticon window suddenly displays normally and does so after that.

  33. #RightToRepair must include software backward compatibility.

    This is ... not nice.
    I don't want to use the web in Safari just because my home instance Mastodon killed its compatibility with my Vivaldi browser version last night.
    Do I have to move to a non-Mastodon instance?

    Vivaldi 5 from 2023: Mastodon is unusable due to notifications and advanced view not opening.
    Safari 13: mangled display for notifications and considerable delay in first-time-actions, but then usable.

    Some detailed error reporting follows. cc @PaulaToThePeople

    #MastoAdmin

    My home Instance, #Mastodon version v4.3.1-stable+ff1 no longer displays notifications: "The requested page could not be rendered."

    Opening the advanced deck view fails with "Due to a bug in our code or a browser compatibility issue, this page could not be displayed correctly."

    Home feed and lists display okay.

    Browser #Vivaldi 5.7. – older version from 2023.
    Just updated to 5.8, apparently the last Vivaldi version compatible with my Mac: same issues.
    Current would be 7.x. which doesn't run on my #MacOS 13 #HighSierra from 2019.

    Safari 13.1 works okay-ish with notifications, although display of liked and boosted posts is mangled.

    It seems to time out without error on opening preferences. But after 5mins or so, it does open and also displays the advanced view correctly, tho with the mangled notifications.
    Opening a random oldish toot from within one of the columns won't display the toot, just an empty column, no error. Opening a new toot from 5mins ago displays immediately.
    Re-opening the oldish toot then displays fine.
    And it first doesn't open the window for emoticons. No error. Just doesn't react to mouse clicks.

    Reply to a toot works. Upon edit of the reply, the emoticon window suddenly displays normally and does so after that.

  34. I really wanted this to be the year I went to High Sierra Music Festival, but health stuff prevented that. Maybe that’s ok. Stay cool and safe out there friends #HSMF #HighSierra #cawx

  35. I really wanted this to be the year I went to High Sierra Music Festival, but health stuff prevented that. Maybe that’s ok. Stay cool and safe out there friends #HSMF #HighSierra #cawx

  36. I really wanted this to be the year I went to High Sierra Music Festival, but health stuff prevented that. Maybe that’s ok. Stay cool and safe out there friends #HSMF #HighSierra #cawx

  37. I really wanted this to be the year I went to High Sierra Music Festival, but health stuff prevented that. Maybe that’s ok. Stay cool and safe out there friends #HSMF #HighSierra #cawx

  38. As the first light of dawn graces the towering Crystal Crag, its majestic form casts a captivating reflection over the tranquil waters of Lake Mamie, creating a stunning panorama of nature's serene beauty. Mammoth Lakes, California.

    rhprintsco.etsy.com/listing/15

  39. As the first light of dawn graces the towering Crystal Crag, its majestic form casts a captivating reflection over the tranquil waters of Lake Mamie, creating a stunning panorama of nature's serene beauty. Mammoth Lakes, California.

    rhprintsco.etsy.com/listing/15

    #MammothLakes #Lakes #Mountains #Mountainsunrise #Nature #Photography #Art #MastoArt #wallart #canvas #SierraNevada #Ayearforart #California #HighSierra #sunrise #Lake

  40. As the first light of dawn graces the towering Crystal Crag, its majestic form casts a captivating reflection over the tranquil waters of Lake Mamie, creating a stunning panorama of nature's serene beauty. Mammoth Lakes, California.

    rhprintsco.etsy.com/listing/15

    #MammothLakes #Lakes #Mountains #Mountainsunrise #Nature #Photography #Art #MastoArt #wallart #canvas #SierraNevada #Ayearforart #California #HighSierra #sunrise #Lake