1
The door creaks open. Needs oiling.
(lemmy.world)
Only if we could know how much to save for tomorrow.
Tomatoes were only introduced to Italy in the 1500s (from the Americas) so i highly doubt they had tomatoes in Pompeii at that time. :)
This is /c/aviationdadjokes material.
Yeah. The longer we wait to make this decision as a community, more the cost of merging and the load on lemmy.ml.
do not
Do you know if communities can choose their own custom CSS?
I love(d?) that subreddit. Relatively good quality discussions compared to most of other programming subs on reddit.
The rust instance can federate with others so users can use the same account everywhere. The OP has an account on programmy.dev, you have one on lemmyrs.org, and I have mine on lemmy.world and yet we are all having a conversation on this thread without issues.
Owning the instance gives admin permissions to whomever is running the server but also the headache of maintaining uptime. If we move this community to programming.dev, the rust community would be “tenants” on a common instance. This option would be a no-brainer for smaller language communities (where my brainfuck enthusiasts at?), but if rust community decides to completely move to Lemmy, it might make sense to have a separate instance.
In terms of raw scaling for Lemmy and pure efficiency, AFAIK, fewer large instances is better than lots of smaller instances that federate with each other.
But the question is less about efficiency and more about trust. I’d rather have this community on programming.dev (first choice) or lemmyrs.org (equally great except for the fragmentation) depending on which admin the community is more comfortable with.
view more: next ›
lightsecond
joined 1 year ago
In my opinion this runs counter to the idea of federation; i wouldn’t use it.
You probably do intend to keep it running for ever, but if you can’t for whatever reason, all links created using this service become dead links. If this were client-side, maybe. But this needs a server to be running at lemmyverse.link and/or threadiverse.link. Imagine someone else gets hold of those domains. They can snoop every use.
I have multiple accounts and might want to choose based on what I’m researching. If it were on a client, it should be a widget, but this doesn’t allow me to switch that so easily.
I think the solution should be for all Lemmy clients to detect links when possible and open them up in-app and/or have browser plugins that can redirect requests on the user’s machine. These won’t cover all the cases that your service can, but i would still prefer that over all Lemmy links being resolved by a centralized service that can read your cookies.