New Jersey lawmaker warns mystery drones may originate from Iranian 'mothership': 'Should be shot down'
New Jersey lawmaker warns mystery drones may originate from Iranian 'mothership': 'Should be shot down'
Rep. Jeff Van Drew, R-N.J., cited high-level sources while telling Fox News that mystery drones seen flying over New Jersey could belong to Iran.Taylor Penley (Fox News)
New Jersey lawmaker warns mystery drones may originate from Iranian 'mothership': 'Should be shot down'
New Jersey lawmaker warns mystery drones may originate from Iranian 'mothership': 'Should be shot down'
Rep. Jeff Van Drew, R-N.J., cited high-level sources while telling Fox News that mystery drones seen flying over New Jersey could belong to Iran.Taylor Penley (Fox News)
True confessions time. I’ve been using ChromeOS to run Webdancers since 2015. By switching to Linux, I’m divesting myself of one small piece of my reliance on Google. Plus, I like to tinker with technology and that 13.5” Chromebook screen was getting a little hard on my old eyes.
PeerTube mobile app: discover videos while caring for your attention | JoinPeerTube
PeerTube mobile app: discover videos while caring for your attention | JoinPeerTube
Today, at Framasoft (bonjour!), we publish the very first version of the PeerTube Mobile app for android and iOS. A lot of care went into its concepti...JoinPeerTube
like this
realcaseyrollins, Badabinski and Endymion_Mallorn like this.
like this
Fitik likes this.
Floyd Mayweather attacked by vicious mob in London over support for Israel
Floyd Mayweather attacked by vicious mob in London over support for Israel
Boxing legend Floyd Mayweather was attacked by a vicious mob in London over his support of Israel and the Jewish people, according to witnesses. Mayweather, 47, was out shopping in London’s s…Isabel Keane (New York Post)
Chicago Sports Network-Marquee merger a possibility amid Comcast dispute
Chicago Sports Network-Marquee merger a possibility amid Comcast dispute
Chicago Sports Network and Marquee Sports Network are reportedly discussing a merger amid current disputes with Comcast.Drew Lerner (Awful Announcing)
Chicago Sports Network-Marquee merger a possibility amid Comcast dispute
Chicago Sports Network-Marquee merger a possibility amid Comcast dispute
Chicago Sports Network and Marquee Sports Network are reportedly discussing a merger amid current disputes with Comcast.Drew Lerner (Awful Announcing)
Hovrättsdom för skjutningar i Västberga och Tullinge. Svea hovrätt har dömt tre personer och fastställt tingsrättens fällande domar vad gäller deras inblandning i dödandet av tre personer och försök att döda sju personer.
Linux, openSUSE ready for Everyday Users
Linux, openSUSE ready for Everyday Users
Most people don’t give much thought to their operating system, but with Windows 10 support ending in October 2025, many will start searching for alternatives...openSUSE News
like this
Dessalines likes this.
reshared this
Linux reshared this.
On the other hand I think it's important to mention those things we don't have or can't ever (or who knows when) have, because the companies behind those products don't care at all for the platform, or care about in a negative way, several of those are used by "everyday users" and I'm sure it can be a deal breaker for them.
I guess it's a decent campaign to cater to those looking at their options with the incoming end of Windows support at least
Most people don’t give much thought to their operating system, but with Windows 10 support ending in October 2025, many will start searching for alternatives...
I predict most of them are going to waste a ton of money and buy a Window 11 device. Or waste a shit-ton of money and buy a Apple device. Or just say "fuck it" and keep Windows 10 (that's what my mom will surely do. I stopped caring, as my dad still wants to use his even older Windows 8 shitbox and my mom 100% agrees to this).
I mean, I get MS Office part but do normal people use Adobe stuff (aside from Acrobat)? As I see, normal people don't even know how to use Photoshop. The ones who can use Adobe products can use Linux as well without a hassle in my opinion. However, a change requires to relearn things. Probably that's the reason people don't seek a change, unless they feel a little adventurous.
If it ain't broke, don't fix it! Hopefully, Microsoft will break that cycle.
I think your Adobe comment isn't quite right. I have two family members who are professional photographers and use Photoshop; Photoshop is so important to their workflow they can't give it up just to use Linux. They thus stick with Windows (though one's work had them using Macs for a bit, so they see it as acceptable).
In contrast, although I sometimes used Photoshop in hobbies (a euphemism for memes), I never used any features so specific to Photoshop that I couldn't just replace it with a combination of Inkscape and GIMP.
I think the truth is as much as I hate Adobe, Photoshop is the best at what it does right now compared to competitors; GIMP 3.0 has a dismal UI and a weaker feature set, and the latter is largely true of a lot of the web-based editors as well.
I approached this as they are more techie than a regular user, so they can learn Linux faster if they want. Otherwise, it's their job and they are not a regular user. It's the same for MS Office too. If it's related to someone else's job, it's most likely irreplaceable. However MS Office is not a must for people who just want to write or do some spreadsheet.
Basically I exclude jobs from "everyday users".
Well, it's true that Photoshop has no real competitor, at least in the FOSS world. Otherwise we wouldn't have this conversation. :)
Latest Tumbleweed snapshot has a Mesa bug that causes 50% chance of black screen after login. A few weeks before that Plymouth was broken causing >1 minute boot times. To solve these issues users need to learn how to rollback updates from command line, so it's certainly not a good replacement for Windows.
I know it's rolling release distro but you can't claim "it's rolling release so bugs are expected and it's your fault for using it" and "it's betest and stablest system ever, everyone should use it" at the same time.
like this
Sickday likes this.
forums.opensuse.org/t/snapshot…
bugzilla.opensuse.org/show_bug…
forums.opensuse.org/t/after-to…
bugzilla.suse.com/show_bug.cgi…
gitlab.freedesktop.org/mesa/me…
Not all hardware seems to be affected (at lest in case of second issue). I have a AMD GPU though and I hit both of them.
Sickday likes this.
I also have AMD and do updates regularly and didn't have this issue, but I think the problem is pretty apparent and has been for quite some time. Packman repository should not be used by non-knowledgeable users! I am not exactly sure what that means for daily use, but as seen here it creates issues if you are not aware what an update actually does or just press "yes, yes, yes" to all questions in an update process.
In regards to plymouth I have no clue, but it seems this should be easily manageable by booting into a previous snapshot?
like this
Sickday likes this.
The second something doesn’t work as expected, even a minor thing, they’ll be at a complete loss about how to even investigate the issue, let alone correct it.
In the majority of cases, this is no different from Windows users on Windows.
I also sometimes (but often enough, including a time this week) hear people discuss to not install updates because of this and that.
but then if I think about it, I have trained myself too to this:
- I avoid updates to my smart tv, because I know with facts that they'll enshittify it, including patching in admin access (was not obtained by a no-interaction attack), flooding it with ads and even more tracking, and even more preinstalled apps and their own tracking. this applies to any "smart" appliences
- I am cautious with android updates, because they sometimes break things with no way back, not even a real way to do backups. besides that, major version updates always reset some settings including to not connect automatically to any random ISP's cellular network. versions starting with 8 also introduced many new arbitrary limitations out of the user's control that cannot be reverted
- I've seen many apps on the play store get enshittified, but sometimes f-droid apps to make changes that I would wish they rather didn't do
- windows updates breaking expected and unexpected things just as well
- linux is fragile regarding updates, though at times an immediate reboot solves it (when the issue is caused by incompatibility between the the on-disk and in-memory versions of the programs and program libraries)
TV I agree, my LG updated and now streaming video is broken.
For android phone GrapheneOS.
I haven't found Linux to be fragile. I think that is distro dependent.
I'm on same OpenSUSE (with version upgrades) since 2017. Every update has been fine, only time it was an issue is when nVidia driver got ahead of the kernel for a few days. But OpenSUSE you just choose the previous snapshot.
My wife's laptops is NixOS for maybe 3 years now, no issues.
Excited for Venus providing vulkan on guests.
Does anyone know how long it will take to reach mainstream distros like Ubuntu?
What the EU’s new software legislation means for developers
What the EU’s new software legislation means for developers - The GitHub Blog
The EU Cyber Resilience Act will introduce new cybersecurity requirements for software released in the EU. Learn what it means for your open source projects and what GitHub is doing to ensure the law will be a net win for open source maintainers.Felix Reda (The GitHub Blog)
like this
Dessalines likes this.
reshared this
Open Source reshared this.
Going to come out swinging for MSFT
github provides it's runners generously for free!
They have not banned me, which is a charm point
Gitlab, on the other hand! Going to whine about that forever
Gitlab deletes your account suddenly without recourse or offers a means to communicate with them to resolve issues civilly.
Listen here Stallman, pedo associate Gates is my hero!
Thank you github for not banning me ... hopefully not maybe ... yet
That big bold Thank you didn't hurt one bit
Try it on for a change!
Oh shiat! You read it?? LOL
Oh man i had to wipe away some tears
Now i need to wash my face
First: IANAL, EU law is complicated. This is my understanding as of now:
TL;DR: The EU Cyber Resilience Act (CRA) aims to enhance cybersecurity standards for products with digital elements. It introduces mandatory requirements for manufacturers and retailers to ensure cybersecurity throughout a product's lifecycle. The CRA excludes open-source software developers unless their software is used commercially as part of a "product with digital elements".
would lemmy be regulated by CRA?
Lemmy, as an open-source project, would likely not be directly regulated by the CRA. The Act specifically excludes open-source developers from its scope unless their software is used commercially.
Whaz about lemmy instances?
Lemmy instances might be regulated by the CRA if they are operated commercially as part of a "product with digital Elements". (Is there a pay for access instance or hosting as a service for lemmy? I am not aware of one.) However, since most instances are run non-commercially or for personal use, they would likely fall outside the CRA's scope.
Is there a difference if there is a fee or a recurrent donations?
Yes:
- A fee is typically a mandatory payment for a service or product, e.g. a feature locked behind a paywall.
- A recurring donation is a voluntary, regular contribution to support an organization or cause, often without receiving goods or services in return.
The key distinction lies in the obligation attached to the payment. Fees come with an expectation of receiving something in return, while donations are given freely without such expectations.
it's free as in go pound sand if you aren't going to fund maintainers
it doesn't force them to do anything until devs refuse to work for any company that doesn't.
i'm with you on agplv3+. The copyright recognition document comes before the resume.
Can you post a link.
Not familar with it, but will read it if you point me in the right direction
Here are some links:-
1. FUTO's Source-First Licence
2. IRL usage of Source-First Licence
3. A criticism of Source-First licence & FUTO
Have fun
I read all 3.
The critic has been tricked. He is naive nice person. And therein lies the rub. He is dwelling on rebutalling the bullshit not realizing it's purpose is to distract away from real issues.
He's argued twice based on nostalgia rather than on legal merits.
People may have legitimate reasons to want different terms in an open source license. The critic rejects this.
If the critic has nothing to add to the conversation, he should go pound sand. The adults are capable of ripping systems apart and understand how to pieces fit back together and can customizing them without deviating from FOSS and OSD philosophy.
Go with aGPLv3. FUTOs nonsense nonpoints don't help in the least.
Real issues like pay only in Monero to the maintainer without any KYC. Not in encumbered methods requiring our time and risk of not being able to receive the funds. No NPOs. No middlemen that take cut.
Devs needs to unionize or form gangs. Society is currently telling us to get a job rather than maintain the packages world+dog relies upon. That's malicious, suicidal, has real consequences, and thus should be our #1 political issue. And we have to change society's focus by causing a rukcus, not submitting more resumes to create more web sites and smartphone apps or cloud services. Which is just purposefully pushing us towards a job creation program rather than a means to maintain world+dog's tech base.
There should be a systematic way for companies to pay towards those maintaining their tech stack. Lacking this, the companies can just say they are confused on how to go about paying devs. I can see their POV. That infrastructure needs to exist.
None of these points, violate open source philosophy one bit.
None of these points require yet another license. It's more about what direction tech community has to take moving forward.
Well, if I understand things correctly, it may address a part of this issue indirectly: corps are responsible of what they use. If a part is open source they also have the opportunity to fix the problem themselves.
Looks very nice to me.
Wait? Are we pretending the corps are actually the FOSS devs?
A Corp dev, aka a FOSS dev forced into societal job creation servitude making throw away smartphone apps, web sites, and now AI models.
Gets paid to not be a productive person. Is essential what a societal job creation program is. Actually accomplishing anything is a random flaw and not the intent of employing devs.
The alternative would be to fund the dev to concentrate on maintenance efforts of their repos which the entire world depends on.
And if you don't believe me, just explain one thing. What's the pip-tools maintainer up to? Cuz it's definitely not focused on pip-tools maintenance
Would definitely be interested to check in daily to watch what he's doing. Can throw parties to watch some of the most influential and important people on the planet do the equivalent of digging ditches, refilling them, then doing it again.
They literally went don't care "Git is good enough" they're literally talentless monkeys
There is efforts to make the issues and PRs forkable as well. There is some folks jumping ship. Haven't researched the new platforms like codeberg
I wasn't talking about Github, I was talking about GIT itself;
Look at these Three:
1. Fossil
2. Pijul
3. Darcs
The last 2 are Patch-Based & 2 is basically a modernized-version of 3, eventhough 3 is still being maintained to this day & 1 is a fully-fledged Github-in-a-box
Oh boy I can't wait for the negative comments about it's obviois flaws, so let's hear it
Have read thru the Fossil web site. Fossil and git are nothing alike. Fossil is not Github in a box. That's misleading.
It's ok to place the key/value pairs merkle tree into an sqllite database AND NOT change the philosophy away from what we are used to with git.
Fossil makes me more sold on git. I want the PRs, i want to be able to rebase. I want to be able to fork projects away from it's parent.
Fossil needs to rewrite if it wants to attract git users. My main thing is portability of PRs and Issues. So when fork a project, the PRs and Issues are also forked. When the original author disappears would be nice to not have to rename the repo, while losing the PRs and Issues.
No. The FOSS dev would turn around and tell the entire world to go pound sand
The devs are under no obligations to do squat. Which includes responding to any EU requests.
If anyone has a problem with a FOSS project, they are welcome to fork the repo and maintain it themselves. And then send love letters back and forth to the EU.
If anyone is sent a request by the EU, i'm here to help. Some ideas to include in a response.
Shouldn't EU be focusing on Ukraine and throwing their males into a meat grinder?
EU does not have free speech. Why take them seriously? Why have any expectations of them?
MSFT please send all that love and support by all the bitcoin you are not buying
thank you
-- package maintainers
I'm so surprised to read a Microsoft article written by a former member of the European Parliament from the Pirate Party, even moreso as the president of the lobbying arm of Microsoft.
I was interested in knowing what are the duties of the software providers under the regulation, more than hiw they don't apply to hobbyists, I keep searching for other articles that explain it.
Vi måste ta till vara på det positiva. Den gångna veckan föll Assads mycket brutala och hårdföra diktatur. Det är en positiv utveckling. Innan dess stoppade folket i Sydkorea en statskupp. Ukraina står emot en mycket starkare angripare dag efter dag, vecka efter vecka, månad efter månad. Det är nåt att glädjas åt.
Perf Support For 2,048 CPU Cores Is Becoming Not Enough - Patches Bump Kernel Limit
Perf Support For 2,048 CPU Cores Is Becoming Not Enough - Patches Bump Kernel Limit
Currently the Linux kernel's 'perf' performance monitoring subsystem has a limit on 2,048 CPU cores for its CPU map that is set by the MAX_NR_CPUS valuewww.phoronix.com
reshared this
Linux reshared this.
Systemd v257 released
- The --purge switch of systemd-tmpfiles (which was added in v256) has been reworked: it will now only apply to tmpfiles.d/ lines marked with the new "$" flag. This is an incompatible change, and means any tmpfiles.d/ files which shall be used together with --purge need to be updated accordingly. This change has been made to make it harder to accidentally delete too many files when using --purge incorrectly.
- The systemd-creds 'cat' verb now expects base64-encoded encrypted credentials as input, for consistency with the 'decrypt' verb and the LoadCredentialEncrypted= service setting. Previously it could only read raw, unencoded binary data.
- Support for automatic flushing of the nscd user/group database caches has been dropped.
- The FileDescriptorName= setting for socket units is now honored by Accept=yes sockets too, where it was previously silently ignored and "connection" was used unconditionally.
- systemd-logind now always obeys block inhibitor locks, where previously it ignored locks taken by the caller or when the caller was root. A privileged caller can always close the other sessions, remove the inhibitor locks, or use --force or --check-inhibitors=no to ignore the inhibitors. This change thus doesn't affect security, since everything that was possible before at a given privilege level is still possible, but it should make the inhibitor logic easier to use and understand, and also help avoiding accidental reboots and shutdowns. New 'block-weak' inhibitor modes were added, if taken they will make the inhibitor lock work as in the previous versions. Inhibitor locks can also be taken by remote users (subject to polkit policy).
- systemd-nspawn will now mount the unified cgroup hierarchy into a container if no systemd installation is found in a container's root filesystem. $SYSTEMD_NSPAWN_UNIFIED_HIERARCHY=0 can be used to override this behavior.
- /dev/disk/by-id/nvme-* block device symlinks without an NVMe namespace identifier are now fixed to namespace 1 of the device. If no namespace 1 exists for a device no such symlink is created. Previously, these symlinks would point to an unspecified namespace, and thus not be strictly stable references to multi-namespace NVMe devices. These un-namespaced symlinks are mostly obsolete, users and applications should always use the ones with encoded namespace information instead. This change should not affect too many systems, because most NVMe devices only know a namespace 1 by default.
- Support for cgroup v1 ('legacy' and 'hybrid' hierarchies) is now considered obsolete and systemd by default will ignore configuration that enables them. To forcibly reenable cgroup v1 support, SYSTEMD_CGROUP_ENABLE_LEGACY_FORCE=1 must additionally be set on the kernel command line.
reshared this
Linux reshared this.
I'd just like to interject for a moment. What you're refering to as systemd, is in fact, systemd/Linux, or as I've recently taken to calling it, systemd plus Linux. Linux is not an operating system unto itself, but rather another free component of a fully functioning systemd system made useful by the systemd services, journald and vital system components comprising a full OS as defined by Poettering.
Many computer users run a modified version of systemd every day, without realizing it. Through a peculiar turn of events, the version of systemd which is widely used today is often called Linux, and many of its users are not aware that it is basically the systemd init service, developed by Lennart Poettering.
There really is a Linux, and these people are using it, but it is just a part of the system they use. Linux is the kernel: the program in the system that allocates the machine's resources to the other programs that you run. The kernel is an essential part of an operating system, but useless by itself; it can only function in the context of a complete init system. Linux is normally used in combination with systemd: the whole system is basically systemd with Linux added, or systemd/Linux. All the so-called Linux distributions are really distributions of systemd/Linux!
All the so-called Linux distributions are really distributions of systemd/Linux!
but are they really? how about distros without systemd what would you call those OpenRC/Linux? systemd is indeed a giant intricate project,which is why some people don't like it or are against it,but all its components are working alongside the Linux kernel, without which there wouldn't be a need for systemd. I would say it's rather Linux with systemd,as systemd is optional.
edit: useless autocorrect
realcaseyrollins
in reply to realcaseyrollins • • •