Nice

The “All” Feed Syndrome

Has anyone else noticed how painfully similar the “All” feed looks across different Lemmy instances? It’s like we’re browsing the same curated content, just with different window dressings. The posts, upvotes, and discussions feel increasingly uniform - a far cry from the diverse, decentralized dream we signed up for.

It’s called All for a reason?!

I doubt it, but fingers crossed.

ESPHome is the gift that keeps giving. When you get around to building your smart speaker, please detail it with regular posts so we can live vicariously through you.

Bitwarden overall is great project. But the lack of oversight on the clients is baffling. Why hire a team that has no interest in open source?

I’ve seen alias pop up a few times of late, I’ll continue to keep an eye open.

I dunno then. Sorry, wish I could help.

Run

docker image prune -af
docker volume prune -af

Downvote for what? What part is wrong?

Regarding SMTP:

SMTP (Simple Mail Transfer Protocol) is a foundational technology for email, but it has some limitations. Here are some ways it could be improved:

• Security: SMTP was designed in a time of less pervasive security threats. It lacks built-in encryption and authentication mechanisms, making it vulnerable to eavesdropping, spoofing, and spam. While extensions like TLS/SSL and authentication methods exist, they are not universally implemented or enforced.

• Efficiency: SMTP is a “chatty” protocol, meaning it involves multiple back-and-forth exchanges between the client and server. This can lead to latency and increased resource consumption, especially for large emails or bulk sending.
• Deliverability: SMTP doesn’t have mechanisms to guarantee email delivery. Emails can get lost, delayed, or filtered as spam. While techniques like SPF, DKIM, and DMARC help, they are not foolproof.
• Features: SMTP is primarily designed for sending emails. It lacks features for managing email content, tracking delivery status, or handling complex email workflows. Possible Improvements:
• Mandatory Encryption: Enforcing TLS/SSL encryption for all SMTP connections would protect email content from interception.
• Stronger Authentication: Implementing more robust authentication mechanisms would prevent spoofing and ensure that emails originate from legitimate senders.
• Enhanced Deliverability: Developing mechanisms to track email delivery, provide feedback on delivery failures, and reduce spam filtering would improve deliverability.
• More Efficient Communication: Exploring alternative protocols or extensions that reduce the “chattiness” of SMTP could improve efficiency.
• Integration with other technologies: Integrating SMTP with other technologies like REST APIs or message queues could enable more complex email workflows and features.

It’s important to note that some of these improvements are already being addressed through extensions and best practices. However, there is still room for improvement in making SMTP a more secure, efficient, and reliable technology.

That said, it looks like Delta Chat doesn’t actually use SMTP, having scanned through the website. Though I’m honestly unsure either way as it was only a scan.

Never mind:

Delta Chat doesn’t use its own proprietary protocol. Instead, it cleverly leverages the existing email infrastructure for message delivery. Here’s how it works:

• Core Protocol: IMAP/SMTP - Delta Chat primarily uses the standard Internet Message Access Protocol (IMAP) for receiving messages and Simple Mail Transfer Protocol (SMTP) for sending them. These are the same protocols your regular email client uses.
• Encryption: Autocrypt & OpenPGP - To ensure secure and private communication, Delta Chat implements end-to-end encryption using the Autocrypt standard and the OpenPGP standard. This means your messages are encrypted in such a way that only the intended recipient can decrypt and read them.
• Secure Key Exchange: SecureJoin - Delta Chat also utilizes the SecureJoin protocol for secure key exchange. This helps to prevent man-in-the-middle attacks and ensures that only authorized parties can establish secure communication. In essence, Delta Chat works by:
• Sending encrypted messages as emails: When you send a message in Delta Chat, it’s actually sent as an encrypted email to the recipient’s email address.
• Receiving encrypted messages as emails: Delta Chat constantly checks your email inbox for new encrypted emails that are meant for you.

• Decrypting and displaying messages: When a new encrypted email arrives, Delta Chat decrypts it and displays it to you in the chat interface. This approach has several advantages:

• Decentralization: No central server is required to store your messages, making it more resistant to censorship and single points of failure.
• Openness: It leverages existing email infrastructure, making it interoperable with any email provider.
• Security: End-to-end encryption ensures that your messages remain private and secure.

If you’re interested in learning more about the technical details, you can check out the cryptographic analysis of Delta Chat available on the Cryptology ePrint Archive: https://eprint.iacr.org/2024/918

Because delta chat is using an open protocol (email)

So not an instant messaging protocol but rather a technology that the whole world would do differently if they could go back in time?

This is really cool, thanks for making this.

Edit: And most people who claim that they never saw something from BBC on YouTube or heard it somewhere are lying. Let’s be real

Yeah, but hardly any

This is a tough one! Since we don’t have concrete numbers, any guess is going to be very broad. But, based on the information we have, here’s a very rough stab at it:

I’d guess that BBC content likely accounts for somewhere between 1% to 5% of the total video views on YouTube in the UK. Here’s my reasoning:

• YouTube’s sheer size: YouTube is absolutely massive. The amount of video uploaded every minute is staggering. Even if the BBC has millions of views, it’s still a drop in the ocean.
• Global vs. UK: While BBC content is popular in the UK, it doesn’t have the same global appeal as some of the biggest YouTube channels.
• Niche focus: The BBC’s YouTube presence, while strong in certain areas like news and music, isn’t trying to compete with the general entertainment that dominates YouTube. Important Caveats:
• This is a VERY rough guess. It could be higher or lower.
• “Content” is hard to define. This guess assumes we’re talking about official BBC uploads, not fan clips or anything like that.
• Viewing habits change. What people watch on YouTube is constantly evolving, so this is a snapshot in time.

Ultimately, without more data, it’s impossible to be more precise. But hopefully, this gives you a general sense of where BBC content might fit in the vast landscape of YouTube.

Obviously that’s asking AI to guesstimate. But there’s a bunch of channels people watch more than the BBC on YouTube, should we pay them too?

That’s bloody fantastic

Keep them separate

If you want to rip the video and host it on your personal server, I’ll happily edit the link.

Haven’t both of these launched already? Seems like this should be a gofundme rather than a Kickstarter

Yeah, to fix that I’ve had to employ the Redirector add-on. Slightly annoying but no big deal.

Docker and very straightforward. I would argue it’s easier to set up than using their installation script.

Just installed SearXNG the other day and have been loving my little private instance.

Don’t be afraid, just mention it