Decent (portrait/indoor) flash for Sony A7
https://lemmy.world/post/36767878
Decent (portrait/indoor) flash for Sony A7 - Lemmy.World
Hiya! Any recommendations for a nice flash for the Sony A7 series? I currently
own an A7iii, but I’m debating an upgrade to the A7iv or A7v whenever it’s
released. I mostly shoot with my Sony 40mm G, Tamron 35-150mm, and Tamron
17-28mm. Links to good buying guides would be great, too! (not AI generated slop
recapping Amazon’s top 10) Budget is rather arbitrary as long as price/quality
is upheld.
Experience with LGPL dependencies?
https://lemmy.world/post/27046889
Licensing strategies - Lemmy.World
So I’m currently re-evaluating my startup company’s licensing policy. Things
have grown organically and it feels like a good time to set things up properly
and sustainably. We have a domain specific language with a fully fledged
compiler for which we would like to make (corporate/proprietary) adoption easy
but have this core and changes to it remain open: sounds like LGPL might fit the
bill for the library work behind this? Any other candidates? We want to promote
open sourcing any extensions or integrations of the language. We also maintain
our own analysis and visualization (VS Code) extensions and applications that
build on these libraries, but I’m a bit more hesitant here. There’s so much time
invested in this that we do not want this to be “up for grabs” so we’re thinking
of GPL or even AGPL here, but consider a dual licensing clause to redeem some
development hours if corporate parties want to incorporate that in their
product. Is that unreasonable?
Licensing strategies - Lemmy.World
I’m currently re-evaluating my startup company’s open source licensing strategy.
We’re currently the only contributor to our projects (yet) so we have some
freedom to change I believe. TLDR: is LGPL for core libraries and AGPL+dual
licensing (on request) for client applications a sensible strategy? Is dual
licensing sustainable or a big no-no? We have a domain specific language with a
fully fledged compiler for which we would like to make (other
product/external/corporate/proprietary) adoption easy but have this core and
changes to it remain open: sounds like LGPL might fit the bill for the core
library work? Any other license candidates? We want to promote open sourcing any
extensions or integrations of the language as well but regular GPL and dual
(paid) licensing seems a bridge too far to encourage adoption in other products.
We also maintain our own analysis and visualization (VS Code) extensions and
client apps/libs that build on these core libraries, but I’m a bit more hesitant
here. There’s so much time invested in all this that we do not want this to be
“up for grabs” without sharing alike so we’re thinking of GPL or even AGPL here,
but consider a dual licensing clause to redeem some development hours if
corporate parties want to incorporate our stuff in their proprietary product.
Community moderation vs censorship
https://lemmy.world/post/25085986
Community moderation vs censorship - Lemmy.World
Why is any informational discourse regarding anything not strictly OSI-style
open source immediately removed by moderators in this community? How can we
expect people to educate themselves through censorship instead of public
discussion? I’m looking for an open source licensing strategy for my own startup
company and discussing the do’s, don’ts or even perception of different licenses
and strategies seems highly important to the community to me. I could understand
if it was actively promoting something ‘bad’ or wouldn’t mind having clear tags
or disclaimers that underline what is or isn’t strictly OSI but it feels a bit
too rigorous right now 😕
Noodgevallen en beheer - Lemmy.World
Laat ik vooropstellen dat ik enorm blij ben dat er al een redelijk bevolkte
Nederlandse Lemmy instance bestaat. Maar met instances als deze of bijvoorbeeld
tchncs.de [http://tchncs.de] bekruipt mij toch altijd het gevoel dat het
risicovol is met één persoon als beheerder. Moet de instance dan ‘gewoon’
verlaten worden in de hoop dat een nieuwe opkomt als de beheerder uit beeld
raakt of wat dan ook? Hoort deze fase van instances gewoon bij het zijn van
‘early adopter’? Ik zou het heel vet vinden om een stichting of iets anders op
te richten of te sponsoren als die zich in zou zetten voor een NL rijtje
gefedereerde services met behoorlijke statuten die de gebruikers beschermen. Ik
betaal daar met liefde en plezier een (vrijwillige) subscriptie voor van een
paar € per jaar. Of bestaat dit al?