IanTwenty

One of the newswire articles is a great read

https://blog.colinbreck.com/i-dont-want-to-read-what-you-didnt-write/

Perhaps the laziest and most offensive use of AI writing I have seen: I had someone use AI to summarize my comments on their proposal as their response to me! Thanks! I couldn’t have said it better myself!

So if I understand: hosters will be able to provide the proof at a time/schedule of their choosing. On actual servers a simpler, automated cert renew process without the need for them to hold nameserver API credentials.

Say that new authelia exploit looks like one fail2ban already recognises or relies on timing/brute-force then you’re covered even before a patch is available.

Here’s a real authelia vuln:

https://app.opencve.io/cve/CVE-2026-47203

allowing an attacker to circumvent login throttling or account lockouts by simply altering the case of their credentials.

I think fail2ban would help protect authelia here?

Firewalling containers’ outbound access seems to be rare but another powerful layer of protection

You’ve made a great start. How much further you go depends on your needs and threat model.

Rsync is ok as a start but there are dedicated backup tools that will give you access to your files at any point in time. This is important if you delete a file and later need it back after an rsync has already run and deleted it remotely too.

Rsync will not encrypt your backups. If a burglar takes your Pi will they have easy access to all your files too?

With rsync+ssh you are also vulnerable to either yourself (more likely) or a rogue process on your own machine deleting the files over ssh (e.g. ransomware attack).

The answer to that is append-only backups. A backup tool like restic has a backend you can host that does exactly this:

The --append-only mode allows creation of new backups but prevents deletion and modification of existing backups. This can be useful when backing up systems that have a potential of being hacked.

https://github.com/restic/rest-server

Take a look at restic to see what else you gain from switching to a dedicated tool versus rsync:

https://github.com/restic/restic#design-principles

There are others too such as borg.

I’m not familiar with Pikapods but Monica v4 has trouble with notifications. First you need to ensure it’s been configured right to even send a test email, this can be triggered with a command if you have access:

php artisan monica:test-email

Various Monica environment variables must be set to configure this, it should be in the docs somewhere if not I can fish my config out for you.

Even once that’s working you’ll need Monica to run its regular jobs for sending notifications, there’s config for that too. Finally the code has bugs and will often miss reminders in my experience. There are some open bugs still on this and I guess the devs have moved onto their rewritten version (chandler):

https://github.com/monicahq/monica/issues/5681

F-droid themselves gave an update in April:

https://f-droid.org/en/2026/04/03/twif.html

If you’ve been holding off updating Syncthing-Fork we have two pieces of news for you. First, the original dev continues to collaborate still, we know this was a pain point back then. Second, we’ve just added BasicSync, A simple app for running Syncthing, which just controls Syncthing’s running behaviour as hands off as possible, while the original service hums in the background.

So it seems since the handover things have settled but there is also a new fork which takes a more bare-bones approach.

From the github if you were wondering:

Free, open-source, self-hosted wardrobe organizer. Catalog clothes, build outfits, PWA. Docker one-liner deploy.

Hello

Somebody developed a Home Assistant integration for monitoring and managing sourdough starters

The danger being raised with the licensing is that you can’t license something if you’re not considered to be the author. There are growing examples of courts and lawmakers determining AI output to be public domain:

The US Supreme Court recently refused to reconsider Thaler v. Perlmutter, in which the plaintiff sought to overturn a lower court decision that he could not copyright an AI-generated image. This is an area of ongoing concern among the defenders of copyleft because many open source projects incorporate some level of AI assistance. It’s unclear how much AI involvement in coding would dilute the human contribution to the extent that a court would disallow a copyright claim.

https://www.theregister.com/2026/03/06/ai_kills_software_licensing/

This is an evolving, global situation and hard to know what to do right now. I think what you’ve got is fine though - you’ve made it clear your intention is to license with AGPL. It’s just that depending on the jurisdiction it might be public domain instead.

This is another reason to be clear about the use of AI in the README so your users can make an informed decision.

Don’t encrypt the drive, encrypt the backups and put your keepassdb alongside. Use restic or similar that encrypts backups.

The contention is that Mattermost say it’s licensed under AGPL but then they add conditions which are incompatible with that license. So it seems they want to give appearance of AGPL but not give the actual rights that come with it. So therefore it’s not AGPL.

Presumably that can’t handle things that the app adds like run conditions for wifi/mobile data though? I realise some may not care about that as much.

Thank you for introducing me to FairScan! Great app. I have a scanner but being able to snap stuff on the go is so much quicker.

MarkStack looks ideal for publishing docs for family

https://github.com/KineticEnforcer/MarkStack

Fast, minimal static site generator that transforms markdown into searchable documentation sites. Built to run anywhere, even on a Raspberry Pi.

Check the app’s own docs first, there is something here about automating backups:

https://docs.frappe.io/erpnext/user/manual/en/download-backup

The EFF have a page on this, setting out the threats:

https://www.eff.org/wp/unintended-consequences-16-years-under-dmca

…which is mostly a link to:

https://www.eff.org/files/2014/09/16/unintendedconsequences2014.pdf

…whose summary reads as follows.

The “anti-­‐circumvention” provisions of the Digital Millennium Copyright Act (“DMCA”), codified in section 1201 of the Copyright Act, have not been used as Congress envisioned. The law was ostensibly intended to stop copyright infringers from defeating anti-­‐piracy protections added to copyrighted works.[1] In practice, the anti-­‐circumvention provisions have been used to stifle a wide array of legitimate activities. As a result, the DMCA has become a serious threat to several important public policy priorities:

The DMCA Chills Free Expression and Scientific Research.

Experience with section 1201 demonstrates that it is being used to stifle free speech and scientific research. The lawsuit against 2600 magazine, threats against Princeton Professor Edward Felten’s team of researchers, and prosecution of Russian programmer Dmitry Sklyarov have chilled the legitimate activities of journalists, publishers, scientists, students, programmers, and members of the public.

The DMCA Jeopardizes Fair Use.

By banning all acts of circumvention, and all technologies and tools that can be used for circumvention, the DMCA grants to copyright owners the power to unilaterally eliminate the public’s fair use rights. Already, the movie industry’s use of encryption on DVDs has curtailed consumers’ ability to make legitimate, personal-­‐use copies of movies they have purchased.

The DMCA Impedes Competition and Innovation.

Rather than focusing on pirates, some have wielded the DMCA to hinder legitimate competitors. For example, the DMCA has been used to block aftermarket competition in laser printer toner cartridges, garage door openers, videogame console accessories, and computer maintenance1 services. Similarly, Apple has used the DMCA to tie its iPhone devices to Apple’s own software and services.

This thread adds some context but not easy to draw any conclusions yet:

Update on the project

They link to Chandler (monica vNext) which is an now an archived repo however I think dev work has moved to main branch in Monica repo? So possibly misunderstanding…