home.social

#lighthearted — Public Fediverse posts

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

  1. How to Zigbeeize a cheap Xiaomi Bluetooth thermometer/hygrometer

    Warning: These instructions work for my exact type of thermometers I've got. You might have totally different result, including your thermometer getting bricked, so don't hold me liable for that (damages estimated at 6 dollars USA). is me making a post after all this time a recession indicator?

    blog.cysioland.pl/2026/04/03/h

  2. Biesentales 99-1 and 99-2 broadcasts are available for listening.
    "Romantically illbient" soundtracks & off-the-main-road hits dubbed with live impros by various people, hosted by @*_jayrope
    Good times, noisy & amused Berlin underground in 2000.
    Feel free to #boost and #reshare.

    Archive.org incl. download
    #^https://archive.org/details/biesentales-99
    #^https://archive.org/details/biesentales-99-2

    Mixcloud, (user-tracking applies, not downloadable)
    #^https://www.mixcloud.com/CashmereRadio/biesentales-99-1-aroma-la-citt%C3%A0-futura-pt-ii-hybrid-djlive-set-12112025/
    #^https://www.mixcloud.com/CashmereRadio/biesentales-99-2-aroma-la-citt%C3%A0-futura-pt-i-10122025/

    This is a hybrid dj/live set recorded at Aroma, Berlin, 2000, by yours truly and in two parts. Aroma was never an official event location or bar, and we've always meet to just hang out, drink, dance, and use a few cassettes and CDs fed into a loop machine/delay buffer to just start playing on top, if just on cocktail glasses :)

    Enjoy

    #fediradio @ExperimentalMusic group @Electronic Music #futurepop #glitch #noise #improvisation #lush #lighthearted #BerlinUnderground #2000s #soundtracks #illbient

  3. Biesentales 99-1 and 99-2 broadcasts are available for listening.
    "Romantically illbient" soundtracks & off-the-main-road hits dubbed with live impros by various people, hosted by @*_jayrope
    Good times, noisy & amused Berlin underground in 2000.
    Feel free to #boost and #reshare.

    Archive.org incl. download
    #^https://archive.org/details/biesentales-99
    #^https://archive.org/details/biesentales-99-2

    Mixcloud, (user-tracking applies, not downloadable)
    #^https://www.mixcloud.com/CashmereRadio/biesentales-99-1-aroma-la-citt%C3%A0-futura-pt-ii-hybrid-djlive-set-12112025/
    #^https://www.mixcloud.com/CashmereRadio/biesentales-99-2-aroma-la-citt%C3%A0-futura-pt-i-10122025/

    This is a hybrid dj/live set recorded at Aroma, Berlin, 2000, by yours truly and in two parts. Aroma was never an official event location or bar, and we've always meet to just hang out, drink, dance, and use a few cassettes and CDs fed into a loop machine/delay buffer to just start playing on top, if just on cocktail glasses :)

    Enjoy

    #fediradio @ExperimentalMusic group @Electronic Music #futurepop #glitch #noise #improvisation #lush #lighthearted #BerlinUnderground #2000s #soundtracks #illbient

  4. Biesentales 99-1 and 99-2 broadcasts are available for listening.
    "Romantically illbient" soundtracks & off-the-main-road hits dubbed with live impros by various people, hosted by @*_jayrope
    Good times, noisy & amused Berlin underground in 2000.
    Feel free to #boost and #reshare.

    Archive.org incl. download
    #^https://archive.org/details/biesentales-99
    #^https://archive.org/details/biesentales-99-2

    Mixcloud, (user-tracking applies, not downloadable)
    #^https://www.mixcloud.com/CashmereRadio/biesentales-99-1-aroma-la-citt%C3%A0-futura-pt-ii-hybrid-djlive-set-12112025/
    #^https://www.mixcloud.com/CashmereRadio/biesentales-99-2-aroma-la-citt%C3%A0-futura-pt-i-10122025/

    This is a hybrid dj/live set recorded at Aroma, Berlin, 2000, by yours truly and in two parts. Aroma was never an official event location or bar, and we've always meet to just hang out, drink, dance, and use a few cassettes and CDs fed into a loop machine/delay buffer to just start playing on top, if just on cocktail glasses :)

    Enjoy

    #fediradio @ExperimentalMusic group @Electronic Music #futurepop #glitch #noise #improvisation #lush #lighthearted #BerlinUnderground #2000s #soundtracks #illbient

  5. Biesentales 99-1 and 99-2 broadcasts are available for listening.
    "Romantically illbient" soundtracks & off-the-main-road hits dubbed with live impros by various people, hosted by @*_jayrope
    Good times, noisy & amused Berlin underground in 2000.
    Feel free to #boost and #reshare.

    Archive.org incl. download
    #^https://archive.org/details/biesentales-99
    #^https://archive.org/details/biesentales-99-2

    Mixcloud, (user-tracking applies, not downloadable)
    #^https://www.mixcloud.com/CashmereRadio/biesentales-99-1-aroma-la-citt%C3%A0-futura-pt-ii-hybrid-djlive-set-12112025/
    #^https://www.mixcloud.com/CashmereRadio/biesentales-99-2-aroma-la-citt%C3%A0-futura-pt-i-10122025/

    This is a hybrid dj/live set recorded at Aroma, Berlin, 2000, by yours truly and in two parts. Aroma was never an official event location or bar, and we've always meet to just hang out, drink, dance, and use a few cassettes and CDs fed into a loop machine/delay buffer to just start playing on top, if just on cocktail glasses :)

    Enjoy

    #fediradio @ExperimentalMusic group @Electronic Music #futurepop #glitch #noise #improvisation #lush #lighthearted #BerlinUnderground #2000s #soundtracks #illbient

  6. (poll for Jews only)

    We have Jew, and Jewess.

    Gender Neutral or Gender Queer Jews, what do you think about these?

    #Mazeldon #Lighthearted #GenderNeutral

  7. Wafrn guy interacted with us and one of these clowns went "OH LORD WE'VE BEEN FOUND" I hate this collective


    #🐱 #light-hearted #i-actually-love-all-of-my-headmates-very-much
  8. Barman woes on OVH

    So, due to a cascade of Barman’s errors and corrupted backups due to running out of backup space, I had to pretty much clear out my Barman backup storage.

    After resetting everything, however, I was not able to make a full backup, because Barman was not able to receive write-ahead logs from PostgreSQL.

    2025-06-04 22:00:21,209 [523687] barman.cli ERROR: [Errno 5] Input/output error: '/backup/barman/pg/wals/00000001000000CD/00000001000000CD00000009.tmp'
    See log file for more details.
    Traceback (most recent call last):
    File "/usr/lib/python3/dist-packages/barman/cli.py", line 2390, in main
    args.func(args)
    File "/usr/lib/python3/dist-packages/barman/cli.py", line 1600, in archive_wal
    server.archive_wal()
    File "/usr/lib/python3/dist-packages/barman/server.py", line 2651, in archive_wal
    self.backup_manager.archive_wal(verbose)
    File "/usr/lib/python3/dist-packages/barman/backup.py", line 847, in archive_wal
    archiver.archive(verbose)
    File "/usr/lib/python3/dist-packages/barman/wal_archiver.py", line 213, in archive
    self.archive_wal(compressor, wal_info)
    File "/usr/lib/python3/dist-packages/barman/wal_archiver.py", line 356, in archive_wal
    shutil.copystat(src_file, tmp_file)
    File "/usr/lib/python3.12/shutil.py", line 388, in copystat
    _copyxattr(src, dst, follow_symlinks=follow)
    File "/usr/lib/python3.12/shutil.py", line 338, in _copyxattr
    os.setxattr(dst, name, value, follow_symlinks=follow_symlinks)
    OSError: [Errno 5] Input/output error: '/backup/barman/pg/wals/00000001000000CD/00000001000000CD00000009.tmp'

    Input/output error? That’s odd, but the stacktrace tells us a lot, as from the function name (os.setxattr), we can deduce that it’s trying to set xattrs on our WAL files. The underlying storage for my backups is OVH’s Backup Storage, accessible over NFS. And NFS, for most of its life, was not able to support xattrs even if the underlying filesystem does. The support has been added to NFS 4.2, while OVH (still) uses 4.1.

    So, how to fix this?

    Initially, I thought of downgrading Barman, because things had worked before. But that did not help, and so I had to go digging into the source code (which was painful as I am not a Python guy).

    # Perform the real filesystem operation with the xlogdb lock taken.            # This makes the operation atomic from the xlogdb file POV            with self.server.xlogdb("a") as fxlogdb:                # If the content has changed, it means the file was either compressed                # or encrypted or both. In this case, we need to update its metadata                if content_changed:                    shutil.copystat(src_file, current_file)                    stat = os.stat(current_file)                    wal_info.size = stat.st_size

    So, if content_changed is true, we use copystat from shutil.py, which copies xattrs from the original file.

    # If the bits of the file has changed e.g. due to compression or encryption            content_changed = False            # Compress the file if not already compressed            if compressor and not wal_info.compression:                compressor.compress(src_file, tmp_file)                files_to_remove.append(current_file)                current_file = tmp_file                content_changed = True                wal_info.compression = compressor.compression            # Encrypt the file            if encryption:                encrypted_file = encryption.encrypt(current_file, dst_dir)                files_to_remove.append(current_file)                current_file = encrypted_file                wal_info.encryption = encryption.NAME                content_changed = True

    Ah, so therein lies the rub: Barman assumes that it needs to do this if the content is either being compressed or encrypted. And it just so happens that I’ve also enabled GZIP compression so as not to run out of space again. Well, we have to deal with this the old-fashioned way (by lowering the retention policy). After disabling compression, Barman was able to make backups again.

    Hope this helps someone, because it sure as fuck would’ve helped me.

    #Barman #lighthearted #NFS #NFSv4 #OVH #pgsql #PostgreSQL #SelfHosting

  9. Barman woes on OVH

    So, due to a cascade of Barman’s errors and corrupted backups due to running out of backup space, I had to pretty much clear out my Barman backup storage.

    After resetting everything, however, I was not able to make a full backup, because Barman was not able to receive write-ahead logs from PostgreSQL.

    2025-06-04 22:00:21,209 [523687] barman.cli ERROR: [Errno 5] Input/output error: '/backup/barman/pg/wals/00000001000000CD/00000001000000CD00000009.tmp'
    See log file for more details.
    Traceback (most recent call last):
    File "/usr/lib/python3/dist-packages/barman/cli.py", line 2390, in main
    args.func(args)
    File "/usr/lib/python3/dist-packages/barman/cli.py", line 1600, in archive_wal
    server.archive_wal()
    File "/usr/lib/python3/dist-packages/barman/server.py", line 2651, in archive_wal
    self.backup_manager.archive_wal(verbose)
    File "/usr/lib/python3/dist-packages/barman/backup.py", line 847, in archive_wal
    archiver.archive(verbose)
    File "/usr/lib/python3/dist-packages/barman/wal_archiver.py", line 213, in archive
    self.archive_wal(compressor, wal_info)
    File "/usr/lib/python3/dist-packages/barman/wal_archiver.py", line 356, in archive_wal
    shutil.copystat(src_file, tmp_file)
    File "/usr/lib/python3.12/shutil.py", line 388, in copystat
    _copyxattr(src, dst, follow_symlinks=follow)
    File "/usr/lib/python3.12/shutil.py", line 338, in _copyxattr
    os.setxattr(dst, name, value, follow_symlinks=follow_symlinks)
    OSError: [Errno 5] Input/output error: '/backup/barman/pg/wals/00000001000000CD/00000001000000CD00000009.tmp'

    Input/output error? That’s odd, but the stacktrace tells us a lot, as from the function name (os.setxattr), we can deduce that it’s trying to set xattrs on our WAL files. The underlying storage for my backups is OVH’s Backup Storage, accessible over NFS. And NFS, for most of its life, was not able to support xattrs even if the underlying filesystem does. The support has been added to NFS 4.2, while OVH (still) uses 4.1.

    So, how to fix this?

    Initially, I thought of downgrading Barman, because things had worked before. But that did not help, and so I had to go digging into the source code (which was painful as I am not a Python guy).

    # Perform the real filesystem operation with the xlogdb lock taken.            # This makes the operation atomic from the xlogdb file POV            with self.server.xlogdb("a") as fxlogdb:                # If the content has changed, it means the file was either compressed                # or encrypted or both. In this case, we need to update its metadata                if content_changed:                    shutil.copystat(src_file, current_file)                    stat = os.stat(current_file)                    wal_info.size = stat.st_size

    So, if content_changed is true, we use copystat from shutil.py, which copies xattrs from the original file.

    # If the bits of the file has changed e.g. due to compression or encryption            content_changed = False            # Compress the file if not already compressed            if compressor and not wal_info.compression:                compressor.compress(src_file, tmp_file)                files_to_remove.append(current_file)                current_file = tmp_file                content_changed = True                wal_info.compression = compressor.compression            # Encrypt the file            if encryption:                encrypted_file = encryption.encrypt(current_file, dst_dir)                files_to_remove.append(current_file)                current_file = encrypted_file                wal_info.encryption = encryption.NAME                content_changed = True

    Ah, so therein lies the rub: Barman assumes that it needs to do this if the content is either being compressed or encrypted. And it just so happens that I’ve also enabled GZIP compression so as not to run out of space again. Well, we have to deal with this the old-fashioned way (by lowering the retention policy). After disabling compression, Barman was able to make backups again.

    Hope this helps someone, because it sure as fuck would’ve helped me.

    #Barman #lighthearted #NFS #NFSv4 #OVH #pgsql #PostgreSQL #SelfHosting

  10. Barman woes on OVH

    So, due to a cascade of Barman’s errors and corrupted backups due to running out of backup space, I had to pretty much clear out my Barman backup storage.

    After resetting everything, however, I was not able to make a full backup, because Barman was not able to receive write-ahead logs from PostgreSQL.

    2025-06-04 22:00:21,209 [523687] barman.cli ERROR: [Errno 5] Input/output error: '/backup/barman/pg/wals/00000001000000CD/00000001000000CD00000009.tmp'
    See log file for more details.
    Traceback (most recent call last):
    File "/usr/lib/python3/dist-packages/barman/cli.py", line 2390, in main
    args.func(args)
    File "/usr/lib/python3/dist-packages/barman/cli.py", line 1600, in archive_wal
    server.archive_wal()
    File "/usr/lib/python3/dist-packages/barman/server.py", line 2651, in archive_wal
    self.backup_manager.archive_wal(verbose)
    File "/usr/lib/python3/dist-packages/barman/backup.py", line 847, in archive_wal
    archiver.archive(verbose)
    File "/usr/lib/python3/dist-packages/barman/wal_archiver.py", line 213, in archive
    self.archive_wal(compressor, wal_info)
    File "/usr/lib/python3/dist-packages/barman/wal_archiver.py", line 356, in archive_wal
    shutil.copystat(src_file, tmp_file)
    File "/usr/lib/python3.12/shutil.py", line 388, in copystat
    _copyxattr(src, dst, follow_symlinks=follow)
    File "/usr/lib/python3.12/shutil.py", line 338, in _copyxattr
    os.setxattr(dst, name, value, follow_symlinks=follow_symlinks)
    OSError: [Errno 5] Input/output error: '/backup/barman/pg/wals/00000001000000CD/00000001000000CD00000009.tmp'

    Input/output error? That’s odd, but the stacktrace tells us a lot, as from the function name (os.setxattr), we can deduce that it’s trying to set xattrs on our WAL files. The underlying storage for my backups is OVH’s Backup Storage, accessible over NFS. And NFS, for most of its life, was not able to support xattrs even if the underlying filesystem does. The support has been added to NFS 4.2, while OVH (still) uses 4.1.

    So, how to fix this?

    Initially, I thought of downgrading Barman, because things had worked before. But that did not help, and so I had to go digging into the source code (which was painful as I am not a Python guy).

    # Perform the real filesystem operation with the xlogdb lock taken.            # This makes the operation atomic from the xlogdb file POV            with self.server.xlogdb("a") as fxlogdb:                # If the content has changed, it means the file was either compressed                # or encrypted or both. In this case, we need to update its metadata                if content_changed:                    shutil.copystat(src_file, current_file)                    stat = os.stat(current_file)                    wal_info.size = stat.st_size

    So, if content_changed is true, we use copystat from shutil.py, which copies xattrs from the original file.

    # If the bits of the file has changed e.g. due to compression or encryption            content_changed = False            # Compress the file if not already compressed            if compressor and not wal_info.compression:                compressor.compress(src_file, tmp_file)                files_to_remove.append(current_file)                current_file = tmp_file                content_changed = True                wal_info.compression = compressor.compression            # Encrypt the file            if encryption:                encrypted_file = encryption.encrypt(current_file, dst_dir)                files_to_remove.append(current_file)                current_file = encrypted_file                wal_info.encryption = encryption.NAME                content_changed = True

    Ah, so therein lies the rub: Barman assumes that it needs to do this if the content is either being compressed or encrypted. And it just so happens that I’ve also enabled GZIP compression so as not to run out of space again. Well, we have to deal with this the old-fashioned way (by lowering the retention policy). After disabling compression, Barman was able to make backups again.

    Hope this helps someone, because it sure as fuck would’ve helped me.

    #Barman #lighthearted #NFS #NFSv4 #OVH #pgsql #PostgreSQL #SelfHosting

  11. Ah, #Texas, where the #laws are as bright as a solar panel at midnight. 🌙🔌 Clearly, the Lone Star State just unlocked the quantum secrets of sunlight storage or maybe they just mistook a flashlight for the Sun. 😂🤦‍♂️
    thehill.com/policy/equilibrium #SolarEnergy #QuantumHumor #LoneStarState #Lighthearted #HackerNews #ngated

  12. Ah, #Texas, where the #laws are as bright as a solar panel at midnight. 🌙🔌 Clearly, the Lone Star State just unlocked the quantum secrets of sunlight storage or maybe they just mistook a flashlight for the Sun. 😂🤦‍♂️
    thehill.com/policy/equilibrium #SolarEnergy #QuantumHumor #LoneStarState #Lighthearted #HackerNews #ngated

  13. Ah, #Texas, where the #laws are as bright as a solar panel at midnight. 🌙🔌 Clearly, the Lone Star State just unlocked the quantum secrets of sunlight storage or maybe they just mistook a flashlight for the Sun. 😂🤦‍♂️
    thehill.com/policy/equilibrium #SolarEnergy #QuantumHumor #LoneStarState #Lighthearted #HackerNews #ngated

  14. Ah, #Texas, where the #laws are as bright as a solar panel at midnight. 🌙🔌 Clearly, the Lone Star State just unlocked the quantum secrets of sunlight storage or maybe they just mistook a flashlight for the Sun. 😂🤦‍♂️
    thehill.com/policy/equilibrium #SolarEnergy #QuantumHumor #LoneStarState #Lighthearted #HackerNews #ngated

  15. Ridiculously late for Lunar New Year but I needed a fun little thing to ease myself back into digital art. 年年有鱼 (Have fish every year) is a common saying around New Years, as a wish for prosperity. And well, seals love fish.

    #LunarNewYear #ChineseNewYear #DigitalArt #Krita #Seal #Pinniped #Fish #MastoArt #Cartooning #Art #Lighthearted

  16. What Did the Baseball Glove Say to the Ball? Catch Ya Later! Remember, it's Important to Have a Good Sense of Humor and Enjoy the Simple Pleasures in Life. #HumorInLife #SimpleJoys #LightHearted #FunMoments #LaughterIsMedicine #EnjoyTheLittleThings #SmileMore

  17. What Did the Baseball Glove Say to the Ball? Catch Ya Later! Remember, it's Important to Have a Good Sense of Humor and Enjoy the Simple Pleasures in Life. #HumorInLife #SimpleJoys #LightHearted #FunMoments #LaughterIsMedicine #EnjoyTheLittleThings #SmileMore

  18. What Did the Baseball Glove Say to the Ball? Catch Ya Later! Remember, it's Important to Have a Good Sense of Humor and Enjoy the Simple Pleasures in Life. #HumorInLife #SimpleJoys #LightHearted #FunMoments #LaughterIsMedicine #EnjoyTheLittleThings #SmileMore

  19. What Did the Baseball Glove Say to the Ball? Catch Ya Later! Remember, it's Important to Have a Good Sense of Humor and Enjoy the Simple Pleasures in Life. #HumorInLife #SimpleJoys #LightHearted #FunMoments #LaughterIsMedicine #EnjoyTheLittleThings #SmileMore

  20. What Did the Baseball Glove Say to the Ball? Catch Ya Later! Remember, it's Important to Have a Good Sense of Humor and Enjoy the Simple Pleasures in Life. #HumorInLife #SimpleJoys #LightHearted #FunMoments #LaughterIsMedicine #EnjoyTheLittleThings #SmileMore

  21. 11 times the #signs at #Pride made us #laugh, #cry and #unite.

    Some of the messages are #lighthearted whilst others need to be #heard #loudandclear and this has been shown in #Prides gone by. Here we take a look at a handful of some of the best signs from over the years.

    The city's annual #Pride #celebrations return this weekend.

    #Women #Transgender #LGBTQ #LGBTQIA #UK #Liverpool #Pride #Representation #Culture liverpoolecho.co.uk/news/liver

  22. #StuffAlcea

    #KingdomHeartsII

    back when in 2006 when games were still #fun

    #Cheesy story, #lighthearted combat and a whole lot if #edgy #coat wearing people.

    Always good to revisit.

    1000 #Heartless is esp fun

  23. I'll be honest, I don't have 5 last games I've run, since I've basically got #dnd5e and #mutantsandmasterminds and that's it.

    For played, it's just been #dnd5e of late.

    So minor modification for me:

    Five games I'd like to run next:

    #vampirethemasquerade
    #changelingthedreaming
    #lighthearted
    #pathfinder2e
    #wraiththeoblivion

    Five games I'd like to play next:
    #wraiththeoblivion
    #vampirethemasquerade
    #changelingthedreaming
    #pathfinder2e
    #callofcthulhu