Whoof. The burn.
Glad to see some people understand how much more problematic Trump is than anything that Harris would be doing.
Beehaw alt of @melody@lemmy.one
@fwygon on discord
Whoof. The burn.
Glad to see some people understand how much more problematic Trump is than anything that Harris would be doing.
No.
It is hard to have both; but not impossible. You can still be privacy friendly without sacrificing necessary functionality.
It will require that the “provider” of such a dataset constantly scrub, sanitize and remove data that would cause privacy hazards as quickly as reasonably possible however. That in and of itself is a technical challenge; though not impossible.
Ideally there’s not a whole lot of data that needs to be kept.
Legitimately all that needs to be stored is a few things:
and things they MUST NOT STORE OR SHARE like:
I like that he is being decisive about it. I wouldn’t be surprised to learn that the feature was only being delayed because of internal project politics or quirky policies that normally make sense, but don’t in this specific scenario.
I’m not being harsh; they bungled that initial transition badly too; despite it being a Google action.
Unfortunately they left a lot of users in the lurch when they left the Play Store as well and that too left a bad taste. It’s not exactly easy to migrate across versions and packages and software differ wildly as they allowed both versions to do their own thing without relabeling them so you could run them side-by-side.
I don’t blame them for Google’s actions; but I do blame them for how they handled it.
You might be confusing my transition into a rant against Google as blaming Termux.
I stopped using Termux in general because of this inanity where they moved off and stopped supporting the Play Store Version; now this happens where they’re unable to keep things from conflicting across the different APK sources?
Yikes. Seems like a good time to continue staying away from Termux and not recommending it.
It’s a shame since I really love the concept of the app; but each increment of Android has been rough on it and I can’t imagine it being useful with Google being stupid about their policies.
…Unfortunately they’re often quick to blame apps they dislike for problems in the ecosystem, and they often directly attack them through nerfing APIs and system calls that the apps tend to use; which I think is absolutely a dogshit thing to do.
Please, stop enshittifying our phones Google.
Even a progression from “Closed Source” to “Source Available” is nice progress I think.
If we assume that the License is not restrictive we may be able to fork Winamp into a codebase that might actually be Fully Open Source Software and track changes of the upstream as we need.
The largest barrier for me in FLOSS and FOSS applications is simply a lack of GUI tools for what is considered to be “Advanced” functions.
Just because I can do it on linux doesn’t mean it’s easy or intuitive. Unfortunately a lot of FOSS and FLOSS applications are, of necessity, extremely limited in what tasks they are targeting. Frequently you cannot rely on the “alternative” to have a relied upon function or feature until deep in it’s lifecycle; when finally enough people have complained and the feature is implemented.
Sometimes a feature is never implemented due to an entirely shifted paradigm in the way the program is implemented and the feature is “impossible” or “inconsistent with xyz”.
One example of this is the number of GUIs and frontends written for ffmpeg; many of which simply are lazy GUI implementations of what the ffmpeg CLI binary itself will helpfully print out in the console when you ask it for help with the correct switch(es). Many are even less thought out than this and will often unhelpfully provide an obtuse box at the bottom for custom commands you wish to feed to the program…which is great if you know the command(s); but make using the GUI unhelpful when compared to just firing up a CLI and reading the output and figuring out the correct command for exactly what you want it to do.
Keep in mind; I am not at all uncomfortable with using CLI interfaces; I just expect that a GUI doesn’t force me to fallback, or become so unusable that I am forced to fall back on an original CLI tool because I cannot possibly discern why it failed to work
Frequently things that would be simply be an option buried deeply in the GUI menus only and are otherwise fairly simple are relegated as being only possible within a CLI interface; and I find that reality quite infuriating most often…as the limitations of a CLI oftentimes make the task I am trying to complete far less simple than it really should have been.
Mastodon, for example, would have far better moderation tools than lemmy. As for your concerns with “Adding more moderation hurdles”, genuinely I feel recruiting more mods before and while you spin up a service is fine. That may mean you take time to pick them out and train them right. That’s fine. But I don’t think moderation challenges are insurmountable.
This. I like Beehaw and I respect it’s nature. I even maintain an account here just to separate my more boisterous posting personality from the one that I feel safer in expressing on Beehaw. While I do external-post from my other account; that’s usually to respond to either Beehaw users not behaving in a way I feel is consistent with Beehaw values or to address others from external instances.
But I don’t want to see Beehaw closing it’s doors to the fediverse. If your staff team is getting swamped, you’re getting overwhelmed as admins, etc…then find more staff. You literally have the hugest pool of nice people right here on Beehaw, and I’m sure everyone who regularly posts here would likely be highly skilled at moderating somewhere on Beehaw if needed. Most of the time, Beehaw does not attract nasty people, and the hard work of the moderation done here shows.
Spread the load. Don’t defederate or give up on Fediverse. Invest in mental health buffs for your moderation team as needed if necessary!
I’d rather Beehaw didn’t leave Lemmy outright; but I can hardly fault anyone for looking into other alternatives and spinning them up alongside the current Lemmy instance, getting that new thing up and thriving and then slowly migrating away from giving Lemmy so much attention.
Personally I think a little fiscal conservation would be wise at this point.
Costs can, and do eventually, rise. Hardware fails, and other things can happen as a surprise; and I’d rather that Beehaw not be insolvent when those things happen.
While I get the wish to do fun things to enhance the community; I think we need to be keeping an eye on things too. A few bad months where users are squeezed and unable to contribute could also severely impact Beehaw; particularly in and around monthly costs. At no point should Beehaw admins be paying out-of-pocket for things if Beehaw itself as an organization has the funds to properly pay things.
If we do genuinely have too much funding in excess; examining how we could expand Beehaw or make it better is another way you can responsibly re-invest the funds into making Beehaw better.
Additional servers/services might be neat; things like:
Of course such things could also require additional staff on hand, so I understand that you might want to entice someone to help manage these extra things first.
Unpaid internships really do need to be abolished.
yeah no, you’re missing the point.
What Trump did was a gross abuse of power.
To be fair; this ruling is a result of Trump packing the SCOTUS, not something Biden himself did.
Not saying this wasn’t a Democratic party failing; they let Trump win in the first place during all that kerfuffle about Hillary.
But I do think we have to consider the context.
I don’t agree with the assessment of the OP or the original blog article. Grayjay is Open Source software.
It is, however, NOT FREE SOFTWARE and I do know that organizations like the FSF and OSI do not consider it to be free.
The free status of this software was never misrepresented by Louis Rossman. He blatantly explains that there is a cost to this software and that the license is how he plans to enforce his means of collecting this fee on the honor system.
He also outlines how he cannot; and will not…stop anyone from forking this software and basically removing the payment bits of the code and just redistributing it under a different name. I strongly recommend someone does that…and maybe license that work under a much more unrestrictive free license that FLOSS-Only users might find more palatable.
I get that nobody wants or needs to trust Louis to keep his word. He’s gotta run a business at some point…and distributing this software this way on the honor system might not pan out quite the same way he hopes it will. I do hope that at the point where he and his compatriots choose to stop maintaining the application; that they do immediately retcon this restrictive license; and re-release it under a new, free, and unrestrictive Open Source Software license.
If this is true; this is probably going to be a very shocking revelation to some people.
I don’t know how much treason this man needs to commit to get convicted; but I hope he does get punished for something.
Do not put words into my mouth. I already clarified my position to make clear that it applies to this specific instance
I genuinely hope this works out and can be replicated across the world. Diabetes is quite a problem for some; and most importantly; it’s something you can’t really easily prevent from occurring if you’re moderately predisposed to it.