Limeey

A neighbor I was close with recently died and their family asked if I would take the plants, of course I said yes, but 2 of them I know very little about.

I think they might be the same plant at different life stages? Can anyone help me ID these?

I'm looking for security cameras that will integrate with my home server and nas. I want ones that record to my nas without some BS subscription service, and ideally run FOSS server logic I can deploy on my server. I've got one camera now that sorta does what I want, except the software isn't FOSS and I've been unable to add the features that are missing.

My ideal requirements are:

• Good camera quality
• Direct powered (no battery)
• Connects via wifi to my network
• Records to remote nas (no cloud "subscription" requirement)
• Highly configurable via FOSS software
• Monitoring software runs on server with local web access
• QOL features like 2-way audio, audio recording, motion sensing, night vision, etc.

Does anyone have suggestions that meat what I'm looking for or close?

I'm helping with a highly federated instance, I'm trying to track down an error but the logs are rolling over roughly every hour after being flooded with apub warnings.

{"log":"\u001b[2m2023-07-17T00:50:07.309563Z\u001b[0m \u001b[33m WARN\u001b[0m \u001b[2mactivitypub_federation::activity_queue\u001b[0m\u001b[2m:\u001b[0m Queueing activity https://**********/activities/announce/4e5ea7d8-5d06-4c35-8c83-843484ba59b9 to https://**********/inbox for retry after connection failure: Request error: error sending request for url (https://********/inbox): error trying to connect: error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:ssl/statem/statem_clnt.c:1919: (Hostname mismatch).  Sleeping for 60s and trying again\n","stream":"stdout","time":"2023-07-17T00:50:07.309720924Z"}

I assume these are due to sites being offline or otherwise inactive. Looking at the database I see that we have hundreds of instances that haven't received an update in over a month now. How can I stop these from flooding out logs so I can find actual errors.

Can I just remove the problem instances from the instance table? Would that stop the activity pub requests? It seems like we're sending them to reach the inbox, which is failing for various reasons.

I put this together based on another very similar script (attributed, of course) I found on beehaw that forces external links to open in a new tab. Should work on every Lemmy instance by checking the header. While it uses http*://*/* as the match, it only executes any logic if the isLemmy check returns true.

Honestly, this has improved my desktop experience significantly, it was killing me before.

Hope it helps, feedback/suggestions/contributions welcome!

git link: https://github.com/Djones4822/GM-Lemmy-newTab

I switched from notebook to labs recently and I'm missing how the notebook name is displayed in notebooks. it seems like the only way to know which notebook I'm in now is through the tab, but if I have multiple tabs open it compresses them.

Is there any extension or something that will display the notebook name (and make it easily editable) like in notebooks?

On desktop my lemmy is formatted like it's a mobile site with like 70% of the space left as gutters left and right of the feed... can I make them not like this and look more like old reddit?