!lemmySilver
Just trying this out, don't mind me
You could give Bazzite a try! https://bazzite.gg/
I'm greatly enjoying their other flavors as well for my laptop and desktop rig.
Now that's a strapon if I've ever seen one. And it might actually get off if it goes flacid halfway 🤔
Oof, so much nostalgia!
Lost the game!
Before I forget: many thanks for your response! It's nice to discuss this.
That distinction is important indeed. I could always add a notice to the README to underline that for potential users.
I'm going to make a dependency map of our own libs and license the language tools and their dependencies as LGPL such that they can be relatively freely embedded in other products. The post-processing and analysis libs/applications will then be licensed under the AGPL (dual licensing). We had other libraries under the GPL before, but in the current landscape it seems wise to cover the hosted/embedded variations as well.
Whoa! That's huge, congrats!
Many, many thanks for your openness and all your efforts! The twisted joke would have been great fun as well 😂
Open sourcing Summit?
From what I understood, you didn't want to open-source Summit because you don't want to allocate your resources to managing issues and reviewing pull requests amongst other reasons (correct me if I'm wrong!). I don't know if you can disable Issues/PRs on GitHub, but I think it would give a lot of (potential) users peace of mind if the source code could be reviewed. As far as licensing goes, you could go quite stringent with an AGPL if that is a factor, to prevent closed-source clones.
Anyways, I find it sad to see that Summit often gets bashed in Lemmy application discussions for being "yet another proprietary app, no thanks".
That said, if setting up publishing actions or other packaging shenanigans is a hurdle, I'm sure there's people who would love to help.
Hmm, I don't know of many widespread (programming) languages with an AGPL-alike license, but would love to see examples! Wouldn't a language have a better chance of adoption with an easy to integrate licensed library?
As for some full featured visualization and analysis applications that accept the language's data format: those might be a good fit for AGPL as they generate valuable insights.
With non-core stuff I meant a tiny wrapper around some 2D data or some color palette management. I'm fine with MIT/Apache there and would consider LGPL to keep the landscape simpler.
Experience with LGPL dependencies?
Short version of a past post: I'm considering to license my startup's software under the LGPL license, which mostly concerns our "applied science" libraries. Does anybody have perspectives worth sharing on the usage/reception/dependency on LGPL libraries from a personal or company perspective? How often would it still be "blacklisted" like the GPL sometimes is?
Amongst other things the libraries do include tooling for a domain specific language (parser, compiler, language server). The reasoning would be that we would like to lower the barrier to integration of the methods and libraries versus GPL, but don't want proprietary (language) flavors popping up instead of open-sourced contributions somewhere. It might also somewhat prohibit larger parties from "overtaking" the project into something proprietary entirely.
Side note: our low-level elemental libraries are mostly MIT/Apache because these things aren't our core business and are mostly filling gaps where standard implementations
Try Summit, it's slick!
Can't seem tot buy it without paying for the EA subscription shite on Xbox so I'll wait.
Awesome! Thank you for your superb app and support!
Hi there! I had to reinstall the app because the app crashes when the homepage was set to "All subscribed" before the update. "Subscribed" and "All subscribed" are also missing from the left menu, but can be accessed from the top header menu after clicking the feed name. They work, but make the app crash on restart. I reset All subscribed as my default home feed in settings, but that reintroduced crashing on startup.
I pretty much only use the subscribed feed, so this is a huge bummer!
Reproduction update: cleared app storage, restarted app, logged in, set All subscribed as home feed, restarted app --> crash
Luckily, regular "Subscribed" seems to work fine, but is a bit hidden since the top bar community name menu has different options as opposed to the menu when swiping from the left.
Will be very sad if they continue down this slippery slope. I guess my last donation will stay just that 🫠
Those TF2 class introduction videos are still top tier. The drill sergeant in Meet the soldier or the pyro one spreading joy.. Ahh, good times!
While your point might seem fair, you simply cannot buy that car as 'simply a car as any other' if you have at least half an eyeball
Well, it's meant as an introductory paragraph. I think such a general paragraph should not go to those lengths since the vast majority won't be facing that issue. Most large instances that you would recommend for first timers are federated well enough that at least the civilised part of Lemmy is very accessible. I think that with:
- sensible defaults/suggestions
- easy to understand intro
- a help/link to a detailed article
you cover enough for users who can't be bothered, who want to be informed, and those who want to understand what's going on behind the scenes.
Yes, very much in favor of sensible defaults for first timers. Most frontends/apps support multiple accounts anyway so changing/adding more later on really shouldn't be a problem
I think they should stick to the "email provider" analogy. Whole paragraph should be something like:
The only thing you need to start interacting with the Fediverse is an account with one of the many providers, just like with email! Providers are freely available across the globe: pick one that suits your location or interests best! You can start browsing the content of nearly the entire Fediverse from whatever provider you choose. Don't worry, you can always create an account with a different provider later.
You could add a sentence or two about where to find sensible defaults or link an article that explains the more subtle things.
I think the emphasis on instances (and not naming them the more familiar providers) hinders adoption.
Someone's been binging 30Rock
Community moderation vs censorship
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
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 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?