The article refers to the iPhone app’s ”recent” release, which was 10 years ago.
HorseFD
It actually doesn’t run in the original Doom engine. It’s a “limit removing” WAD, meaning it doesn’t use any additional features but removes static limits: https://doomwiki.org/wiki/Static_limits
As long as they keep all the historical stuff available.
Debian is really easy to install now. It used to be much harder back in the day.
Good luck!
0.18 gives us a feed that doesn’t auto refresh and moves the comment collapse button to its rightful place to the left of the username.
I'm not knowledgeable enough on the software to respond to these claims, but the great thing about open source software is that you can raise these as issue on Github and they can be fixed.
I ended up using your images and it's working great. Currently playing around with 0.18.0-rc.5
I tried again on a new server, and I'm still getting the same error. It may be related to this:
https://github.com/LemmyNet/lemmy/issues/3235
I see the same references to email_verified_body and email_verified_subject
I'm gonna jack it up to the highest performance and see if it eats into my first month's free credit.
I've just given the script a go and it seems to have failed
=> => transferring context: 23.07MB 0.2s
=> [lemmy lemmy 2/6] RUN apt-get update && apt-get -y install --no-install-recommends postgresql-client libc6 libssl1.1 ca-certificates && rm -rf /var/lib/apt/lists/* 18.7s
=> [lemmy builder 2/7] RUN apt-get update && apt-get -y install --no-install-recommends libssl-dev pkg-config libpq-dev git && rm -rf /var/lib/apt/lists/* 14.7s
=> [lemmy lemmy 3/6] RUN addgroup --gid 1000 lemmy 0.5s
=> [lemmy lemmy 4/6] RUN useradd --no-create-home --shell /bin/sh --uid 1000 --gid 1000 lemmy 0.4s
=> [lemmy builder 3/7] WORKDIR /app 0.0s
=> [lemmy builder 4/7] COPY ./ ./ 0.2s
=> [lemmy builder 5/7] RUN echo "pub const VERSION: &str = "$(git describe --tag)";" > "crates/utils/src/version.rs" 0.2s
=> ERROR [lemmy builder 6/7] RUN cargo build --release 399.8s
Altough the building timer is still running
[+] Building 761.3s (15/18)
Is there somewhere I can access logs to see what happened?
Edit: Managed to screenshot the error prior to it disappearing
I'll have a look at this and let you know how I go. Does this work on different distros? E.g. Ubuntu/Debian, Centos, etc? The official Ansible script is Ubuntu only (possibly other apt-based distros).
I’ve been using Mlem and it’s really good. Everyone else has mentioned Voyager so I’m gonna give that a try too.