Searching yarn

Twts matching #http
Sort by: Newest, Oldest, Most Relevant
In-reply-to » Just a couple of shots from our trip to Bald Rock—finally got reception so I can share them!

Thank you, @prologic@twtxt.net, that looks really stunning! Seeing forests reaching beyond the horizon always amazes me. This does not exist around here. I also like those balancing rocks.

Keep ‘em coming. Looking forward to see more. But most importantly, enjoy your trip, mate! :-)

⤋ Read More
In-reply-to » It's blackbird time again! https://lyse.isobeef.org/amsel-2026-03-29/

I called it quits a bit earlier and enjoyed the sunny 19°C blue sky in nature. I just sat an entire hour on a bench (12) near a habitat (07) and enjoyed the sun rays and singing birds around me. When I returned, the batteries were almost drained. The sunset finished them off, so that I could not record Azabache’s concert shortly after. However, I saw that amazing bird this morning and got him on film. Enjoy!

https://lyse.isobeef.org/waldspaziergang-2026-04-08/

⤋ Read More
In-reply-to » I remembered to put the camera on my tripod. The neighbors yelling around messed up the audio a bit, though. I kinda saved most parts, but it could have been still better. When I was filming Azabache, a bluetit wanted to return to its nest somewhere next to me, I assume. It was shouting extremely loudly and immediately took off again to land on another roof ridge. It's the one in 24. I had to turn down the volume in the audio. :-D

@lyse@lyse.isobeef.org so adorable! Thank you for the video, I downloaded it. Azabache’s life is seemingly so pleasant, and the sing song, oh my! 🎶😍

⤋ Read More
In-reply-to » It's blackbird time again! https://lyse.isobeef.org/amsel-2026-03-29/

I remembered to put the camera on my tripod. The neighbors yelling around messed up the audio a bit, though. I kinda saved most parts, but it could have been still better. When I was filming Azabache, a bluetit wanted to return to its nest somewhere next to me, I assume. It was shouting extremely loudly and immediately took off again to land on another roof ridge. It’s the one in 24. I had to turn down the volume in the audio. :-D

https://lyse.isobeef.org/waldspaziergang-2026-04-07/

⤋ Read More

Via https://github.com/newsboat/newsboat/issues/3220#issuecomment-4198066671 I came across this nice selection on why not to use AI: https://github.com/Vxrpenter/AIMania/blob/main/WHY.md#why

This then lead me to the slopware list: https://codeberg.org/small-hack/open-slopware

Holy shit, there’s even more than I thought. :-O In addition to Vim, the following affects me more or less daily (but hopefully not my ancient versions): curl, VLC, ImageMagick, rsync, Python, systemd and even the Linux Kernel itself. Oh fuck me dead. :‘-(

⤋ Read More
In-reply-to » It's blackbird time again! https://lyse.isobeef.org/amsel-2026-03-29/

@lyse@lyse.isobeef.org easy come, easy go. They grow so fast! :-) Also, Azabache allows to be seeing when ready for it, you know, just like Gandalf “*a wizard is never late, nor is he early, he arrives precisely when he means to*”. :-D

⤋ Read More

What do the Gopher Troopers think of the following? The Gopher protocol is a nearly-forgotten network protocol from the early 1990s, designed to serve and navigate text-based menus and documents over the Internet. While it’s far less common than HTTP/HTTPS today, there are still some security risks associated with Gopher and Gopher space. Let’s break them down carefully: 1. Lack of Encryption Problem: Gopher was designed long before widespread use of SSL/TLS. All data—including credentials, file transfers, and menu selections—is transmitted in plaintext. Impact: Anyone intercepting traffic (e.g., via a network sniffer, public Wi-Fi, or a compromised router) can read sensitive information, including usernames and passwords. 2. No Authentication or Access Control Problem: Gopher servers rarely implement robust authentication; access control is usually limited or non-existent. Impact: Unauthorized users might browse sensitive directories or download private files, particularly if servers are misconfigured. 3. Server Software Vulnerabilities Problem: Modern OSes can still run legacy Gopher servers, but the software is often unmaintained. Impact: Old software may contain buffer overflows, directory traversal bugs, or command injection vulnerabilities that attackers could exploit. 4. Malicious Gopher Links Problem: Gopher menus can contain links that point to scripts or other servers, similar to hyperlinks in HTTP. A client following a malicious link could inadvertently: Download malware Access sensitive internal network resources (server-side request forgery) Impact: Could serve as a vector for attacks if a user opens content from untrusted sources. 5. Legacy Protocol Weaknesses Problem: Gopher lacks modern web security mechanisms like: Content security policies Same-origin policies Cross-site request forgery protection Impact: If Gopher is bridged to other services (like modern browsers via gateways), old vulnerabilities may be exposed. 6. Information Leakage Problem: Gopher servers often provide directory listings without restriction. Impact: Sensitive files, backup directories, and internal documents may be exposed unintentionally. 7. Bridging Risks Problem: Some modern browsers access Gopher via gateways (HTTP-to-Gopher proxies). These bridges may: Expose sensitive internal resources to the gateway Introduce logging or tracking that wouldn’t exist on pure Gopher Impact: Attacks could occur indirectly through insecure intermediaries. Key Takeaways Gopher is inherently insecure due to its design in a pre-HTTPS era. Main threats: eavesdropping, unauthorized access, malware delivery, and exploitation of unpatched server software. Safe practice: Use Gopher only in isolated, trusted environments, or through secure HTTP(S) gateways with proper sanitization.

⤋ Read More
In-reply-to » The original twt is unavailable. It may have been edited or deleted, or is from an unknown or muted feed.

The problem is, they jump hosts all the time.

Maybe it’s time to add automated blocking after all … God, I’m too lazy for that. 😞

⤋ Read More