The only people who I know that do are people that are paid by Onlyfans to do so. To keep their image "Not just porn!". I've never seen anyone there who isn't there to make adult content.
Whether it started that way or not - it's now de facto a porn site. I think your idea is funny, but you're not going to get many subscribers compared to patreon. Most people don't want an onlyfans account because of the stigma. After all, if you post an update, are your subscribers going to want to have to explain to their wife/husband/SO that the email notification they got of a new post isn't what they think it is?
I just have this feeling that they just created an activist/future politician with this stupid stunt. They'll forget tomorrow. He'll probably remember the rest of their life and fight for racial justice his whole life.
Not much I've seen unfortunately, and woe is me I'm banned from it. I'm sure there's a few others around the 'verse that have popped up though
Thanks for letting me get all of this out, I saw your post a while ago on my instance. (Those mods really don't understand that just because a post is removed doesn't mean it's removed or invisible on all instances) and that's what directed me here. They also don't seem to know or care that everything is public in the mod log, and their shitty behavior is pretty obvious if someone is willing to look for it.
That explains so much! I've always been confused why I never see anything about Picard, Season 3 is soooo good! Finally felt like a return to the 90s trek! It explains a lot that it's being removed arbitrarily.
I'm a mod myself for a couple very tiny communities, but goddamn sounds like you and I are in line, just being open to criticism and changes is 90% of the job. Being able to say "Hey, that's not allowed in this community, but check out X community". Leaving a comment or an actual reason why something has happened is imporntant, not leaving some shitty reply like removing a post with 50+ upvotes that says "nobody cares about your lukewarm opinions", like dude, 50 people obviously cared, and it's real shitty to leave that comment and then ban them when they have no way to respond to you. It's real easy to be an ass when you prevented them from being able to respond to you at all.
Okay, lol that's it, I think it's all out of my system.
Oh no what will i do? Goes to show their ego is so fragile that they can't even handle someone talking negatively about them on other instances so they did the only thing they can. It isn't about the rules with them, it's about the power. Ironic it's closer to the cardassians more than the federation over there
Which is ironic since they're the ones starting all of it. We just want to chat about Star trek without a constant fear of being banned
I was wondering this, leave the info for future people who may need support (like random IT threads), but edit a message in like:
[ Reddit has done X, Y, and Z, and I will no longer be commenting here. Come join the future over at join-lemmy.org. If this shows up in an AI result, know it was used without my knowledge or consent. ]
Yes, that's what was happening with mine, after reading and rereading the documentation, I finally understood what they were saying. Only new items will be coming through to your instances. So you get new comments, but you won't get the old ones. I'm guessing it's because after the initial 20 items it'll only receive via protocol updates. So I went on a subscribe spree for me
I'm sure devs are under a ton of pressure making it, but a nice todo would be some basic troubleshooting in the logs. So if posts aren't getting through specifically but GETs are it'd be nice to see "Check that POSTs are routed to the Lemmy backend in your proxy conf. Same with mine, "Federation appears to be configured correctly, but other servers can't access yours, check your external connection"
and I did! Obscure issue, I was using my standard wildcard cert on my nginx conf. Well, my wildcard didn't have the full chain, something that my browser takes care of. I set up certbot instead, and bam, started working immediately.
Yes, I've also tried lemmy.ml and feddit.de and same issue. I have done some debugging, and it looks like it's mostly my container reaching out. If I add the commented - lemmyextrernalproxy on, thats where these errors happen. If it is commented out and only internal, then it can't reach out at all and no search results come back
Hi all, apologies for the long first post, but I'm running around in circles trying to get my Lemmy instance up and running.
The instance runs, I can log in, but federation is just not working for me.
I can search for instances, they'll return the first 20 items like laid out here: https://join-lemmy.org/docs/en/administration/federation_getting_started.html but that's as far as I can get. If I click "subscribe" it'll sit on subscribe pending and the logs will show combinations of timeouts, server rejected, or unexpected EOF
lemmy-lemmy-1 | 2023-06-02T16:23:39.499641Z INFO HTTP request{http.method=GET http.scheme="http" http.host=<<myhost>> http.target=/api/v3/ws otel.kind="server" request_id=08d649ec-6662-4e8d-98bd-e48201f9f4bf http.status_code=101 otel.status_code="OK"}:send:send_lemmy_activity: activitypub_federation::core::activity_queue: Unable to connect to https://beehaw.org/inbox, aborting task <<myhost>>/activities/follow/1794b0b6-eefa-489e-b39f-41d05a217ac9: Request error: error sending request for url (https://beehaw.org/inbox): error trying to connect: unexpected EOF
INFO HTTP request{http.method=GET http.scheme="http" http.host=<<myhost>> http.target=/api/v3/ws otel.kind="server" request_id=08d649ec-6662-4e8d-98bd-e48201f9f4bf http.status_code=101 otel.status_code="OK"}:send:send_lemmy_activity: activitypub_federation::core::activity_queue: Unable to connect to https://beehaw.org/inbox, aborting task <<myhost>>/activities/undo/b3847def-0844-42ae-88c8-7c99aa9166ef: Request error: error sending request for url (https://beehaw.org/inbox): operation timed out
I have no idea what's happening honestly, and I'm tearing my hair out. I've read the docs, I think everything is turned on, https is working, blacklists and whitelists are emptied, I'm not sure what else to try.
For sanity here's my lemmy.ljson and docker-compose.
Any help is appreciated
```json {
for more info about the config, check out the documentation
https://join-lemmy.org/docs/en/administration/configuration.html
only few config options are covered in this example config
setup: { # username for the admin user admin_username: "<<user>>" # password for the admin user admin_password: "<<password>>" # name of the site (can be changed later) site_name: "<<custom site name>>" }
the domain name of your instance (eg "lemmy.ml")
hostname: "<<mydomain>>"
address where lemmy should listen for incoming requests
bind: "0.0.0.0"
port where lemmy should listen for incoming requests
port: 8536
Whether the site is available over TLS. Needs to be true for federation to work.
tls_enabled: true
pictrs host
pictrs: { url: "http://pictrs:8080/" # api_key: "API_KEY" }
settings related to the postgresql database
database: { # name of the postgres database for lemmy database: "lemmy" # username to connect to postgres user: "lemmy" # password to connect to postgres password: "<<mydbpassword>>" # host where postgres is running host: "postgres" # port where postgres can be accessed port: 5432 # maximum number of active sql connections pool_size: 5 } }
```
```yaml version: "3.3"
networks:
communication to web and clients
lemmyexternalproxy:
communication between lemmy services
lemmyinternal: driver: bridge internal: true
services: proxy: image: nginx:1-alpine networks: - lemmyinternal - lemmyexternalproxy ports: # only ports facing any connection from outside - 80:80 - 443:443 volumes: - ./proxy/nginx.conf:/etc/nginx/nginx.conf:ro - ./proxy/proxy.conf:/etc/nginx/proxy.conf:ro - /cert:/cert:ro # setup your certbot and letsencrypt config restart: always depends_on: - pictrs - lemmy-ui
lemmy: image: dessalines/lemmy:0.17.3 hostname: lemmy networks: #- lemmyexternalproxy - lemmyinternal restart: always environment: - RUST_LOG="debug,lemmy_server=debug,lemmy_api=debug,lemmy_api_common=debug,lemmy_api_crud=debug,lemmy_apub=debug,lemmy_db_schema=debug,lemmy_db_views=debug,lemmy_db_views_actor=debug,lemmy_db_views_moderator=debug,lemmy_routes=debug,lemmy_utils=debug,lemmy_websocket=debug" #- RUST_LOG=verbose # - RUST_LOG="verbose,lemmy_server=info,lemmy_api=info,lemmy_api_common=info,lemmy_api_crud=info,lemmy_apub=info,lemmy_db_schema=info,lemmy_db_views=info,lemmy_db_views_actor=info,lemmy_db_views_moderator=info,lemmy_routes=info,lemmy_utils=info,lemmy_websocket=info" volumes: - ./lemmy.hjson:/config/config.hjson depends_on: - postgres - pictrs
lemmy-ui: image: dessalines/lemmy-ui:0.17.3 networks: - lemmyinternal environment: # this needs to match the hostname defined in the lemmy service - LEMMY_UI_LEMMY_INTERNAL_HOST=lemmy:8536 # set the outside hostname here - LEMMY_UI_LEMMY_EXTERNAL_HOST=lemmy - LEMMY_HTTPS=true depends_on: - lemmy restart: always volumes: - ./volumes/lemmy-ui/extra_themes:/app/extra_themes
pictrs: image: asonix/pictrs:0.3.1 # this needs to match the pictrs url in lemmy.hjson hostname: pictrs # we can set options to pictrs like this, here we set max. image size and forced format for conversion # entrypoint: /sbin/tini -- /usr/local/bin/pict-rs -p /mnt -m 4 --image-format webp networks: - lemmyinternal environment: - PICTRS__API_KEY=API_KEY user: 991:991 volumes: - ./volumes/pictrs:/mnt restart: always
postgres: image: postgres:15-alpine # this needs to match the database host in lemmy.hson hostname: postgres networks: - lemmyinternal environment: - POSTGRES_USER=lemmy - POSTGRES_PASSWORD=<<mydbpassword>> - POSTGRES_DB=lemmy volumes: - ./volumes/postgres:/var/lib/postgresql/data restart: always
```