this post was submitted on 18 Jul 2023
3 points (100.0% liked)

Beehaw Support

2796 readers
6 users here now

Support and meta community for Beehaw. Ask your questions about the community, technical issues, and other such things here.

A brief FAQ for lurkers and new users can be found here.

Our September 2024 financial update is here.

For a refresher on our philosophy, see also What is Beehaw?, The spirit of the rules, and Beehaw is a Community

This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

if you can see this, it's up  

founded 2 years ago
MODERATORS
Zmodem@beehaw.org
Gaywallet@beehaw.org
alyaza@beehaw.org
Lionir@beehaw.org
Penguincoder@beehaw.org
remington@beehaw.org
3
Technology community disappeared? (beehaw.org)
submitted 1 year ago by ede@beehaw.org to c/support@beehaw.org
10 comments fedilink hide all child comments
 

I was engaged in a conversation in the Technology community and both my post and any content in the community disappeared. I can still get to the post, but am unsure what happened. I’ve posted a screenshot showing the Technology community without any content.

you are viewing a single comment's thread
view the rest of the comments
[–] ede@beehaw.org 2 points 1 year ago (1 children)

I still don’t see it. I checked three machines at this point. Thank you for checking.

[–] Penguincoder@beehaw.org 2 points 1 year ago (2 children)

I'll look into this. Could you DM so we can discuss? Or reach out on Discord/Matrix.

[–] ede@beehaw.org 2 points 1 year ago

@apis figured it out. I somehow blocked the community without realizing I had done so. Thank you for the support, it’s very much appreciated.

[–] Zephyrix@beehaw.org 0 points 1 year ago

I think this is due to a broken nginx (or whatever reverse proxy you're using) configuration.

Doing a GET request to https://beehaw.org/c/technology with the header

Accept: application/activity+json, application/ld+json; profile="https://www.w3.org/ns/activitystreams",application/json

is giving me an HTML page instead of the expected JSON.

For comparison, here's what the same query responds with for lemmy.world (shortened since it's quite a long response):

{
	"@context": [
		"https://www.w3.org/ns/activitystreams",
		"https://w3id.org/security/v1",
		{
			"lemmy": "https://join-lemmy.org/ns#",
			"litepub": "http://litepub.social/ns#",
			"pt": "https://joinpeertube.org/ns#",
			"sc": "http://schema.org/",
			"ChatMessage": "litepub:ChatMessage",
			"commentsEnabled": "pt:commentsEnabled",
			"sensitive": "as:sensitive",
			"matrixUserId": "lemmy:matrixUserId",
			"postingRestrictedToMods": "lemmy:postingRestrictedToMods",
			"removeData": "lemmy:removeData",
			"stickied": "lemmy:stickied",
			"moderators": {
				"@type": "@id",
				"@id": "lemmy:moderators"
			},
			"expires": "as:endTime",
			"distinguished": "lemmy:distinguished",
			"language": "sc:inLanguage",
			"identifier": "sc:identifier"
		}
	],
	"type": "Group",
	"id": "https://lemmy.world/c/technology"
}