![User banner](http://rakka.au/static/pics/rin_good_end.png)
![zergling_man](http://rakka.au/static/pics/Aya%20Grin.png?format=webp&thumbnail=64)
Shitposting at the speed of light. I have the power of God and anime on my side. ... That should probably be a pop song or something.
What does that actually do? What's the consequence of setting it to 10,000?
I have a zip of flash games about 3tb. And I think that's after it cut "offensive content".
You executed the file. Not the OS' fault.
Are you executing the files you download?
"There is no such thing as a dangerous file, only bad operating systems."
Under some circumstances it gets called fedilink instead, and sets it as the page's title. I don't know what those circumstances are but I do know lynx meets them.
ikr >Rance on the same level as Saya
It is an object, we are divine beings. Never forget this.
Get a headstart on robot discrimination.
spare.botegirl.parts
Anime girls cute
The webfe is broken, I'll disable it later.
I check applications every 2-3 days, and email isn't configured yet.
There aren't any communities yet because I haven't added that to clemmy yet. Don't make me disable community creation for non-admins.
Markdown sucks.
Sort by date uploaded ascending. Also, nyaa.si.
🍿
I signed up for training yesterday. When they haven't got back to me in a month this will be even funnier.
There is a disturbingly large number of people that haven't figured out how much ubuntu sucks.
How do I figure out which parts of a guide should be followed and which ones shouldn't? If ignoring a part makes the guide work better then it's a bad guide and you should find a better one.ツ
I haven't gotten it to work yet so I disagree. If you
systemctl start nginx
, can you accesslocalhost:80
? If so, success, you've run nginx. Very simple.
I've played G2. I see.
Also: curse of 3
It's just that ubuntu, and everything in the debian family, sucks massive ass, and few people acknowledge it.
It doesn't tell you to actually run nginx, it assumes it will automatically run when installed. I don't know why, that sounds like dumb behaviour even if it were correct. You are right about the guides being trash.
I recommend getting used to package manager (apt, dpkg) and system daemon/init system (systemd - accessed via systemctl) and then ignoring that guide. Installing and running nginx isn't complex enough to warrant a guide; installing packages and running services, in general, are just. Configuring nginx, however... If you know the concepts, it's pretty easy. The concepts are hard.
Look in /etc/nginx/nginx.conf, it probably include
s ./sites-available/*.conf, look in there for ssl_certificate
(_key
) that mentions that fullchain.pem, remove/comment(#
) and restart nginx.
It may still bitch about not having a cert for ssl, in which case take that out of the listen
directives too.
putty
That's your problem. Putty does keys differently to normal ssh.
ansible
docker
.
So, why can't you install lemmy? I'm going to assume you're using ubuntu. If you are willing to swap to arch (which I think DO offers), I recommend it. Get an AUR helper installed (a bit of hassle, I like trizen) and install lemmy from AUR. You'll need to bump the commit unless you like 0.17.3. I'll be doing that tonight so I can post relevant bits. If not, post errors.
Or just keep doing containers so you can have weird and wonderful errors like no dns.
Have you played Grandia 2? How do they compare?
resolve_object
I'm not 100% certain that's the cause, but my testing so far suggests it's probably that. Basically if you have a URL that doesn't point to the original resource, but some copy of it on another instance, it won't resolve. So far I've only tested that on a third instance, but from my experience with the same bug on pleroma, this will occur even if you do it on the resource's origin instance. (fse post referred to from poa.st can't be resolved on fse.) As example: https://lemmy.perthchat.org/api/v3/resolve_object?q=https://lemmy.ml/post/472799. It's possible that this is actually just a federation block, but https://beehaw.org/post/125367/comment/32382 also fails, (and fetching that post works,) which I'm pretty sure isn't.