Frequently Asked Questions
Are you the official Pixelflut organization?
No! We are merely a team of Pixelflut enthusiasts. Among us are many influential people with lots of experience running Pixelflut, writing servers, and advancing the protocol and its applications. We are open to other members and contributors, especially if you have Pixelflut experience.
If you see a random Pixelflut server in the wild, it is possible that one of us is running it. However, that’s not a given.
I want to host a Pixelflut event and use a *.pixelflut.org domain!
Great! Contact Eloy or kleines Filmröllchen and they will set up subdomain records. Please also specify for how long your event runs, so we can remove the addresses again afterwards. If you have some other neat idea for a subdomain, please tell us!
When is the Pixelflut RFC going to be published?
There is no strict timeline. It all depends on how much time we have, how much feedback we get from the IETF, and how much capacity they have to move our proposal forward. Of course, there is also no guarantee that Pixelflut will even make it to an RFC, even in a “lower-tier” form (e.g. April Fools RFC).
My server/client doesn’t agree with the RFC!
Please tell us about it! We try to cover all existing behaviors in the standard, so that all implementations which exist today are automatically spec-compliant. However, we definitely don’t agree with all edge case behaviors. If your behavior is reasonable and/or widespread, we will definitely consider adding it to the specification.