I dunno at what school this photo was taken, but in my day, it was not uncommon for students in dorms to have mini whiteboards on their doors so people could leave messages (often in the form of specific private body parts). Mind you, I went to school before everybody had iPhones.

What I believe we’re looking at here is a photo of somebody’s (presumably Joseph Silva’s) door with a mini whiteboard and someone’s (again presumably Joseph Silva’s) contact info, which happens to be a Lemmy user.

The key word here is Lemmy, which would explain why OP shared this photo on !fediverse@lemmy.world.

I started out with Memmy and was kinda meh about it. Not bad but not great. Then I found Voyager and never looked back. As a paid Apollo refugee, Voyager makes me almost forget that I’m on a different platform from the days of yore.

shared node in one of those image generation nets

You mean like AI Horde?

cross-posted

Minor nit pick, but did you know that Lemmy has actual cross posting functionality?

Either way, interesting study. This is the type of content that I Red er… Lemmy for, so thanks for posting. I use Voyager myself, being an Apollo refugee.

Yo dawg, I heard you like tests, so I got some tests for your tests so you can test while you test!

/community

Yes and no. Technically yes because the issue seems only to affect pixelfed.social; however, that happens to be the largest instance iirc. And hash tags are not federated, so one of the main features for discovery that is accessed from the landing page is unusable or broken (has been for months).

Meanwhile, people are out there talking and reading about this cool federated alternative to instagram called pixelfed, perhaps spending a few minutes browsing the site for the largest instance which also happens to have the word pixelfed in the URL, but as soon as they try interacting with it, they bounce off because they clicked on a link hoping to get more nature photos, but got an error instead. 🤷‍♂️

Hmm… that may be the case on some instances (e.g. pixelfed.social), but I know an account is not required on others because I’ve tested it on several instances without registering. The only one it breaks on is pixelfed.social, which unfortunately is also the largest instance.

But still good to know, thanks for pointing that out. It’s too bad the unauthenticated discovery is still broken, though.

It’s a cool concept with a lot of potential, but currently very buggy and incomplete. For example, basic functionality like hash tags need to be fixed and federated for it to be usable IMHO. It has piqued my interest, though, so I might sign up someday if the usability issues are ever addressed.

ability to follow hashtags

Are hash tags working for you? Whenever I click on a hash tag, it takes me to a missing page.

Except that the explore/discover pages aren’t federated, but otherwise, yeah.

Much respect for the creator of Pixelfed for their contributions to the fediverse and all for more fedi alternatives, but please fix basic functionality on Pixelfed first!

Does it work if you enable VRR via xorg config?

Confirmed VRR is enabled via the xorg config (terminal output below), but I’m still having the issue.

yo_scottie_oh@nobara ~]$ cat /usr/share/X11/xorg.conf.d/10-amdgpu.conf 
Section "OutputClass"
	Identifier "AMDgpu"
	MatchDriver "amdgpu"
	Driver "amdgpu"
	Option "HotplugDriver" "amdgpu"
EndSection

Section "Device"
     Identifier "AMD"
     Driver "amdgpu"
     Option "VariableRefresh" "true"
EndSection

Oddly enough, I just accidentally discovered that when I Alt+Tab out of the game, the monitor’s refresh rate matches the frame rate in game; however, as soon as I Alt+Tab back in so the game is the active window, the refresh rate goes back to the monitor’s native refresh rate. So in the Xorg session, VRR works sometimes, but not when Steam is the active window. Have you ever seen anything like this before?

Not sure if this video will play, but here’s what I mean. Look at the top left—the slightly larger FPS in the white box is my monitor’s overlay, and the smaller FPS under that is MangoHud. Notice how initially, my monitor’s refresh rate is fixed at 165 Hz, then as soon as I bring up the text document, my monitor’s refresh rate starts varying, and when I Alt+Tab back into the game, my monitor’s refresh rate goes back to fixed at 165 Hz again.

Which xorg driver are/were you using, amdgpu or modesetting?

I think amdgpu—does the terminal output confirm that? This is the first I’ve heard of modesetting.

So you’re looking for something like Subreddit Stats for Lemmy communities?

Do you happen to have subscriber data on !caps@lemmy.world?

beligerent god (sic)

You mean beneficent?

Right now hash tags on the largest pixelfed instance (pixelfed.social) are broken—clicking a hash tag in a photo’s caption takes the user to a missing page. Even on other instances where browsing by hash tag isn’t broken, they aren’t federated, so if you click #Amsterdam, you’ll only see other photos on the same (smaller) instance, and it’s not even obvious whether that’s working right because the post count will say one thing, but it’ll only show you like three or four photos.

Lots of potential, but it’s just not there yet.

I’ve been on Lemmy for a few months now and am really enjoying it. I think I’ll stay.

I’ve also been thinking about starting a Pixelfed account so I can share some photos I’ve taken recently. In my poking around the last few days, my first impression is that the bones are there, but it’s still rough around the edges. For example, clicking a hashtag in a photo caption to browse all photos with that hashtag is currently broken on the largest Pixelfed instance, and even on the smaller instances, browsing hashtags doesn’t appear to be federated, so there’s basically no way to discover photos of a certain hashtag or for others to discover my photos unless we are on the same instance, which seems to kind of defeat the purpose of moving to a federated service. Not that hash tags are the most important thing, but kind of a bummer from a discoverability standpoint. I may bite the bullet and sign up anyway, we’ll see.

Looks okay in my view. Tapped and opened the link in the Voyager app on iOS.

This is why we’re just not going to agree—you’re saying because the property owner does not live there, they should operate at a loss, which I disagree with.