this post was submitted on 12 Jun 2023
108 points (100.0% liked)
Technology
37708 readers
402 users here now
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Subcommunities on Beehaw:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
To see Lemmy content on kbin, just add the full address of the Lemmy instance to the end of the kbin URL. For example, https://kbin.social/m/[email protected] lets you see content from @[email protected] on https://kbin.social.
The other way round should also work (ie. to see kbin content on Lemmy), but for some reason it's not working on major Lemmy instances for me, even though they are federated to kbin.social and other kbin instances.
Someone said the cloudflare protection is breaking that ability
Thank you very much, I was trying to figure this out. This makes sense and seemed to work.