I understand where you're coming from when you look at the games with the most marketing, but we also live in the age of Minecraft, not to mention the countless games and genres it inspired. The stuff you're looking for is out there.
However, that will always take you to the lemmy.world website, which if you are a user of lemmy.one (for example) you don't want - you won't be able to comment or post there. If you use a relative path:
It tells the browser to go to that location on whatever server you are currently on. As noted elsewhere, this doesn't work on kbin because they chose to use /m instead of /c. I expect that one or both of Lemmy & Kbin will automatically convert URLs in the future, and will ultimately support the [email protected] form.
edit: Note that the "@lemmy.world" is optional when you are on lemmy.world, but it is the part that will get you to the right place if you use the link on another instance.
shrug I play mostly single-player RPGs and similarly story-heavy games, so while the mechanics are different and the graphics much prettier, the structure is the same as it's been for the past 30+ years: Follow the story to get anywhere, or just wander around in your current area if you want to grind.
They are only really useful for getting an instance to federate an off instance community- you paste that form in the search box, and usually a few minutes later you can access the community.
If you want to have a link to a community, use just ‘/c/[email protected]’ - even if the instance is the one you are on. That way it will work wherever you are logged in. example is a link to ‘/c/[email protected]’
I haven’t found a way to link posts or comments that are instance portable- if anyone knows of a way, I’d love to hear it.
This is one reason I don't use Kbin - it seems to have pointlessly chosen its own terminology just to distinguish itself from Lemmy which makes it less useful.
That way it will work wherever you are logged in. example is a link to ‘/c/[email protected]’
Yeah, those don't work from kbin. None of the links I've found in c/newcommunities works for me. Am patiently waiting for whatever the problem is to be resolved.
You’re not doing it right. There’s absolutely a reason why enterprise linux works with a version that’s more-or-less locked in place (but for security updates, like a maintenance fork). You need to understand the value you’ve been overlooking.
ten years of a stable platform. Because, yeah, it’s not this week’s release with the glitter, but it’s also not a moving target of broken suck you have to constantly chase, and you can actually do dev.
dependencies are figured out
updates are trivial when security stuff comes out. Honestly – yum+cron is so stable and reliable, and the compatibility is part of the guarantee; so you - and your customers - don’t have to worry or - please god no - delay updates to gauge risk. Since updates are 99% of the work to avoid exploits, this goes from ‘huge risk’ to ‘no-brainer’. And you don’t have to worry that your dev environment is non-trivial to replicate on the daily.
your requirements for your software becomes ‘EL7’; maybe ‘EL7+EPEL7’ or so. Your installation process becomes ‘add repo RPM which pulls in other repo RPMs. yum install’ , and you’re already onto mere config work.
validating the install isn’t ‘did you install this ream of apps from this particular week in time, then run some wget|sh bullshit? Now run this other set of commands to confirm your installation’ – but in our case is just ‘rpm -qa|egrep’ or even an snmpwalk.
not working? Give me your one config file and your rpm-qa and we’ll replicate here trivially and find out why. (I didn’t work in support, but I liaised with them a bunch in the security work, and that was common practice) Tossing 4 lines and a <<EOF construct into a vagrant config is just so easy, now, and gives the entire machine to play with.
As someone who used to dev a notable app in the past, cross-distro problems alone made so many of the fringe OSes impossible to support, and so we didn’t. EL was the backbone because we respected what we had.
I just can’t figure out why this-week’s-glitter is more important than losing the install/support/update/validate burden by choosing a stable platform to work within. Life’s too short to support dependency hell or struggle just to replicate a failing setup in your lab for testing. Do you just not support customers?
While you avoid risky files, like .exe/.cmd/.bat/.vbs etc, you should be safe, in the past Soulseek was known as music source, now it’s used also for some other stuff like softwares, books, movies & tv shows.
I think that the nature of a wiki is inherently centralised. You want a central, curated wiki, not one that has a thousand different versions, each of which needs to be mixed together, and checked. Otherwise, you’ll have quite the time dealing with conflicts and things.
But the upside of a wiki is that it can be self-hosted. If a current wiki isn’t good enough, you are able to host your own, and work from that instead. Issue is that it’s not great if you’re technically inclined, and it’s a lot easier to manage a wiki that someone else hosts, tying it all the way back to a single central service.
I think that the nature of a wiki is inherently centralised. You want a central, curated wiki, not one that has a thousand different versions, each of which needs to be mixed together, and checked. Otherwise, you'll have quite the time dealing with conflicts and things.
But the upside of a wiki is that it can be self-hosted. If a current wiki isn't good enough, you are able to host your own, and work from that instead. Issue is that it's not great if you're technically inclined, and it's a lot easier to host/manage a wiki that someone else hosts, tying it all the way back to a single central service.
I'm pretty sure Lemmy has been designed specifically so it can't me monetized. If you try to place ads people can just switch to another instance. If you try to split off from the fediverse I'm pretty sure there's enough data on other instances in order to clone your server along with its content (and mind that you don't own the copyright for posts made by users).
I think it's more than just "not for profit" - there was actual effort to make this platform as difficult to monetize as possible (probably as a lesson learned from Reddit lol). Let's begin with the code - it's under AGPL, which means you can't set up a public Lemmy instance without making its code public. This prevents you from creating an improved version and keeping it to yourself to gain an advantage over other instances. Second, the fediverse means that it's less likely for a single instance to become so big that it can unfederate itself without consequences, and while you're federated you can't really place ads - people would just view your community on another instance.
kbin.life
Active