I’m reading this scratching my head going “If your unit tests need a database they ain’t a unit test”.
I’m reading this scratching my head going “If your unit tests need a database they ain’t a unit test”.
Thing is, a cross post is nothing special. It’s a) a post with an identical link, and b) a post with “cross posted from…” appended to the body content.
It is still just a post. Lemmy (and k/mbin) just attempt to mask the fact there are multiple of them.
I don’t know if it can be done any better though, ActivityPub has quite a few quirks.
On my Pixel I long press at the bottom and then press on the code. I think it’s called google lens or something.
It’s the multiple volumes that are throwing it.
You want to mount the drive at /media/HDD1:/media
or something like that and configure Radarr to use /media/movies
and /media/downloads
as it’s storage locations.
Hardlinks only work on the same volume, which technically they are, but the environment inside the container has no way of knowing that.
Very first line of the GitHub readme. As a support tool it’s mostly useless, endless similar or identical questions answered differently or not at all and none of it indexed by search engines for use on the web.
It’s an awful data silo / black hole that increases volunteer load.
Easily doable in docker using the network_mode: "service:VPN_CONTAINER"
configuration (assuming your VPN is running as a container)
It’s unfortunate that (at least on the Bluesky side) an attempt at following a person doesn’t result in them getting a DM asking for that to be ok.
Which means following a person on Bluesky is not possible unless they’ve already opted in.
All I want to do is follow a couple of authors or content creators but none of them know what bridgy.fed is :(
I’ve not used dockge so it may be great but at least for this case portainer puts all the stack (docker-compose) files on disk. It’s very easy to grab them if the app is unavailable.
I use a single Portainer service to manage 5 servers, 3 local and 2 VPS. I didn’t have to relearn anything beyond my management tool of choice (compose, swarm, k8s etc)
With a small amount of effort and the use of https://github.com/nanos/FediFetcher and https://github.com/g3rv4/GetMoarFediverse you can mitigate basically all those issues. It’s still not perfect by any means but it results in a perfectly usable single user instance.
The first populates the replies of the home timeline posts you see (as well as profiles of people it finds in those replies) and the second pulls down all the content from instances you select for your followed hashtags (choose mastodon.social and you can guarantee you’ll see most all posts with those tags)
“…prohibits repair stores from repairing components on the mainboard. Instead, the entire component must be replaced…”
A flagrant disregard for the costs of e-waste on the environment. What a surprise.
Aside from everyone who’s using flutter?
IIRC your data would live on your chosen pod server - which does not have to be a fediverse instance.
Privately operated ICBM’s. I can’t see how that’ll fly but I look forward to finding out.
Ah, well that is indeed unfortunate and realistically also a bit shit.
We use them quite extensively. They work great.
ActivityPub implementations generally don’t allow this.
This comment will, when I click ‘Reply’, be sent to your instance (dormi.zone), that instance should then run it’s filter/block checks on it and if it’s happy it will forward it onto the lemmy.ml instance for further disemination amongst the subscribers of the group.
If you were to have blocked me then my reply will appear on my instance only (which is admitedly tiny - at 1 user) and go no further. This kind of falls apart if I were to be on a bigger instance as more people would see the reply.
That said, Lemmy may not be doing that quite right as the whole Groups/Communities thing is sort of an extension of the main protocol. I hope it’s doing it the right way.
If buying isn’t owning then piracy isn’t stealing.
Didn’t even think 4k80 was generally available yet?
There’s a couple of caveats with it, but I think neither are worse than your proposed flow.
Hugo can be as simple as installing it, configuring a site with some yaml that points at a really available theme and writing your markdown content.
It gets admittedly more complex if you’re wanting to write your own theme though.
But I think this realistically applies to most all static site generators.