Limit Objects to defined Avatars

Is it possible to change prims/objects only to individual avatars? I would like to limit views from prims to some avatars.
Or any other way. Is it possible to block the cameraview through prims?

Thanks for support!

other than mute for avatars, and large invisiprim walls to block out walls there really isn't a simple way to limit the view of other people / objects. (a custom built client MIGHT work, but I know of no one exploring the creation of such a feature)

Thanks for reply.
It occurred to me about a costum built client. Where textures are coded and only the costum client is equipped to encoded it. But I would like to find a simpler way.

if it's a privacy thing, the only way to get true privacy is to buy/rent a whole sim, and only allow certain people on it. but even that can be iffy, if it's close enough to another sim, sometimes it can be seen and cammed into from a distance

Thus, there is no way to define something completely privat?

well there is sort of ONE way... parcel media supports targeting individual av's with the media, it won't hide prims, but it could be used to hide textures so that only the targeted av sees it.

Sounds as a solution. Do you know how it works? It would solve my problem if only target av's can see textures right.

But there is no possibility of several parcels equal time to consider, because the av has to stay on the definied parcel to see the parcel media. But I want a solution where allowed av's can see more textures from one place.

well you could get a few textures into one parcel stream by combining them into one big image, and then using offsets of the media texture to divide it up in the avs vision.. but yes, they do have to be on the parcel to see it... it'd only support a few textures at a decent quality, but it's about the only guaranteed privacy you'll find.

a custom client could check the creator of a given texture and apply some kind of descrambler to to the image, but that would mean custom image uploads of scrambled textures so not very reuse friendly.

the system just isn't built in a way that would easily (or even effectively) support what you're after.