proxy_media
boolean field to server.json
to true.strict_public_timelines
option introduced in the previous release now works correctly.It's not.
It's a stance OSI got by its sponsors https://opensource.org/sponsors
Meta in particular was allowed to cancel other teams' votes.
The issues have been reported by several people for months (here a recap https://discuss.opensource.org/t/list-of-unaddressed-issues-of-osaid-rc2/650 ) but OSI ignored them, silenced or censored those people.
See Julia Ferraioli's account of the co-design process: https://www.linkedin.com/posts/juliaferraioli_opensource-opensourceai-osi-activity-7256687721182605313-_wpd
If you feel disgusted as I do, here an initiative to restore (and _maybe_ improve) the OSD through public discussion and IETF rough consensus https://opensourcedefinition.org/wip/
@knowprose @sj Thanks for sharing this, it's good to know there's a sizable community that is unhappy with how OSAID got rolled out.
@sj @jaredwhite Through LinkedIn, I got invited to this discussion area regarding the topic... So I'm passing it along.
I haven't had enough contiguous time yet to chime in, but I will.
*Dusts off penguins and Gnus*
I wonder how much abstraction we need to program in C (or in Oberon without inheritance)...
ok, you can question the goals, actually. 😃
which concepts do you think they could not understand or memorize?
can we just omit them and still write useful programs (for them)
ok, you can question the goals, actually. 😃
which concepts do you think they could not understand or memorize?
can we just omit them and still write useful programs (for them)
ok, you can question the goals, actually. 😃
which concepts do you think they could not understand or memorize?
can we just omit them and still write useful programs (for them)
Actually C without _any_ allocation is quite simple and secure.