What am I misunderstanding here? Is MeetEcho actually caching SSO results and lying to users? :)
I don’t really know where you’re heading to, but I will resist the temptation of getting involved in such a useless discussion. I will rather just politely ask you not to attach any label to the Meetecho team that might even remotely recall anything that is close to a liar.
Thanks,
Simon
_\\|//_ ( O-O ) ~~~~~~~~~~~~~~~~~~~~~~o00~~(_)~~00o~~~~~~~~~~~~~~~~~~~~~~~~ Simon Pietro Romano Universita' di Napoli Federico II Computer Engineering Department Phone: +39 081 7683823 e-mail: spromano@xxxxxxxx <<Molti mi dicono che lo scoraggiamento è l'alibi degli idioti. Ci rifletto un istante; e mi scoraggio>>. Magritte. oooO ~~~~~~~~~~~~~~~~~~~~~~~( )~~~ Oooo~~~~~~~~~~~~~~~~~~~~~~~~~ \ ( ( ) \_) ) / (_/
What am I misunderstanding here? Is MeetEcho actually caching SSO results and lying to users? :)
--Richard
Henrik
>
> --Richard
>
>
>
>>
>> Henrik
>>
>>
>> >
>> >
>> > On Tue, Jul 28, 2020 at 1:30 AM Carsten Bormann <cabo@xxxxxxx> wrote:
>> >
>> >> On 2020-07-27, at 20:28, Richard Barnes <rlb@xxxxxx> wrote:
>> >> >
>> >> >>> We should be minimizing our dependence on customized features.
>> >> >
>> >> >> why? so we can be dependent on webex? pfui!
>> >> >
>> >> > On the contrary, the more special features we have, the more locked in
>> >> we are to the tools with those special features, and the less
>> flexibility
>> >> we have to adapt with the times / budgets / needs of the community.
>> >>
>> >> I would agree with the sentiment on anything that is not essential to
>> our
>> >> DNA.
>> >> We probably should not use specialized accounting software.
>> >> But running our internet-drafts repository on Typo3 (*), while it also
>> >> would get rid of dependencies on customized features, is not what we
>> should
>> >> do.
>> >>
>> >> Web meetings that are replacing the traditional IETF week are essential
>> to
>> >> our DNA.
>> >> Different from running an insurance company or anything else that has
>> >> cookie cutter meetings, these really should be based on situated
>> software
>> >> [1].
>> >> Fortunately that can be built on a standard: The Web + WebRTC.
>> >> (Unfortunately, implementations of our own dogfood aren’t fully cooked,
>> >> but that is a problem with any web-meeting software. Also, A/V
>> >> fundamentally is hard, most people have little education in this space,
>> and
>> >> a lot of garbage hardware gets in the way.)
>> >>
>> >> I think we are quite close to where we should be with meetecho.
>> >> We are maybe not doing the development in a sufficiently agile way.
>> >> Of course many reasons can be cited why that is hard to do right now,
>> but
>> >> we should strive for agility.
>> >> It is also not clear that we own what we develop; RFC 873 applies.
>> >>
>> >> Grüße, Carsten
>> >>
>> >> (*) I’m sorry, not everyone here has used Typo3, so that sentence may
>> not
>> >> invoke the horror it should.
>> >> [1]: https://en.wikipedia.org/wiki/Situational_application
>> >> (The renaming doesn’t get the point. Well, I hope you do.)
>> >>
>> >>
>> >
>>
>>
>
|
