Ginevra Di Marco - Kaleidoscope (2025)
Ginevra Di Marco - Kaleidoscope (2025)
di Luca Cremonesi Dopo cinque anni, Ginevra Di Marco torna in sala d’incisione per “Kaleidoscope”, un lavoro nato a seguito di un’importante...Silvano Bottaro (Blogger)
Bob Dylan - Tempest (2012)
Palestinians left 'without shelter and water' as settlers empty West Bank village
cross-posted from: feddit.org/post/15373488
A few excerpts:
That night, the settlers moved from home to home forcing families out at gun point.Resident Aliya Mlihat immediately rang the police, who were slow to respond. When border police and three military jeeps arrived on the scene, they did nothing to stop the onslaught, even facilitating the raids on people's homes.
Mlihat recalled that "the expressions on the soldiers' faces revealed satisfaction - even joy - as if they were endorsing the settlers' actions".
In one photo taken by Mlihat, settlers can be seen lounging in chairs and grinning alongside soldiers in fatigues.
The attack was led by sanctioned Israeli settler Zohar Sabah, who had set up the new outpost. According to Mlihat, Sabah stormed the area armed with an M16 rifle, shouting at residents to "flee to Jordan".
Israeli rights group Stop the Wall reported that settlers pitched a tent in the middle of the village, hooking it up to running water from a nearby outpost. They then proceeded to expand the outpost, forcing the 125 residents to flee to the industrial zone of Beitunia, where they do not have access to water or electricity.
"It involves just a couple of people setting up an outpost, herding their own flocks on the community's traditional grazing land, taking over access to water resources, stealing sheep, intimidating the community and preventing them from having access to all the natural resources around them.
"And then we'll see this escalation of violent attacks, often at night. This is what we're seeing now, just copy-paste, replicated all across the area east of Ramallah."
"It means that the two-state solution that the international community purports to support will no longer be viable, or is not viable if there's no Palestinian presence in large parts of the West Bank."
Low emphasised that despite frequent visits by diplomats to imperilled Palestinian villages in the West Bank, the international community is doing little to prevent their displacement.
Palestinians left 'without shelter and water' as settlers empty West Bank village
On Thursday evening, Israeli settlers erected a tent just metres away from a Palestinian Bedouin village in the Al-Mu'arrajat area in the occupied West Bank's Jordan Valley.Katherine Hearst (Middle East Eye)
Daily Kos is moving to WordPress
Daily Kos is moving to WordPress
For most of its existence, Daily Kos has run on custom-built publishing platforms. That might’ve made sense a decade or two ago, but now it’s expensive, outdated, and difficult to maintain. ...Daily Kos
Hebron locals denounce sheikhs' plan to declare independence and recognise Israel - Locals dismiss Wall Street Journal report about 'Hebron sheikhs' plan to sever ties with Palestinian Authority
Hebron locals denounce sheikhs' plan to declare independence and recognise Israel
Palestinian residents of the occupied West Bank city of Hebron have disavowed a proposal by five purported local "sheikhs" to sever ties with the Palestinian Authority (PA) and establish an "emirate of Hebron" which would recognise the state of Israe…MEE staff (Middle East Eye)
Rozaŭtuno likes this.
Airbus okays use of ‘Taxibot’ to tow planes to the runway
Airbus okays use of ‘Taxibot’ to tow planes to the runway
: Airlines get the chance to cool their jets rather than burn fuel on the groundSimon Sharwood (The Register)
Fairphone 6 Teardown: Proof Phones Don’t Have to Be Disposable - Scored 10 out of 10 on ifixit repairability scale.
Remember when you could pop open a phone, swap the battery, and keep going? Fairphone remembers. Their latest release, the Fairphone 6, feels like a nostalgic nod to sanity, with plenty of modern upgrades.This is a phone that puts people and planet before profits. Sure, it doesn’t have the camera chops to take on a flagship, and USB-2 feels a bit retro in 2025, but what it lacks in bragging rights, it makes up for in staying power.
Fairphone 6 Teardown: Proof Phones Don’t Have to Be Disposable
In a world full of glued-together gadgets designed for obsolescence, the Fairphone 6 earns a well-deserved 10 out of 10 on our repairability scale.Elizabeth Chamberlain (iFixit)
The other winner in New York’s mayoral contest: ranked-choice voting
The other winner in New York’s mayoral contest: ranked-choice voting
Voters want more choice at the polls and more issue-driven campaigns. In the Democratic primary, they got bothDavid Daley (The Guardian)
Missile fired from Gaza hits Israel's Kibbutz Nirim
Missile fired from Gaza hits Israel's Kibbutz Nirim
TEHRAN, Jul. 07 (MNA) – A missile launched from Gaza struck the occupied Nirim area on Sunday, dealing material damage and landing in a neighborhood still recovering from the 2023 Al-Aqsa Flood operation, Israeli media reported.Mehr News Agency
geneva_convenience likes this.
Israel launches extensive airstrikes on Lebanon
Israel launches extensive airstrikes on Lebanon
TEHRAN, Jul. 07 (MNA) – Israeli warplanes pounded several regions across Lebanon in a wave of intense airstrikes on Monday, targeting areas from southern Sidon to eastern Baalbek, Lebanese media reported.Mehr News Agency
TikTok’s ‘ban’ problem could end soon with a new app and a sale
TikTok’s ‘ban’ problem could end soon with a new app and a sale
The TikTok app could reportedly get replaced by a new one for iPhone, Android and other platforms in the US on September 5th to satisfy the divest-or-ban law.Richard Lawler (The Verge)
War Now Indefinitely Sustainable, as New Reports Prove Russian Armor Production Has Finally Reached Equilibrium
First, on the team that did the research: it was done by Conflict Intelligence Team (CIT), which is a kind of open-source think tank formed by Russian dissident Ruslan Leviev back in the early part of the Donbass conflict and Syrian war of the 2014-2015 era. He is wanted by Russian authorities, and as such his team’s findings are obviously done through a pro-Western and pro-Ukrainian slant—which is what makes them all-the-more interesting, given the conclusions made.
How Many Т-90M Tanks does Russia Produce? CIT Research
Russia’s full-scale war against Ukraine, launched in February 2022 as a blitzkrieg-style operation, had by the year’s end devolved into...Teletype
Il retrofuturismo visionario del centro conferenze creato sul confine acquatico della vecchia Kyoto - Il blog di Jacopo Ranieri
Il retrofuturismo visionario del centro conferenze creato sul confine acquatico della vecchia Kyoto - Il blog di Jacopo Ranieri
All’inizio del dicembre 1997 i rappresentanti di un larga parte dei paesi industrializzati al mondo (e non solo) fecero l’ingresso nella grande sala trapezoidale sotto un gigantesco disco illuminato, alludente all’astro del mattino, in cui le lettera…Jacopo (Il blog di Jacopo Ranieri)
“I made a digital legacy prompt vault — and it might outlive me.”
Hey everyone,
I've been building a concept for digital afterlife tools. This is a personal, creative, and AI-driven legacy builder.
Includes:
– 600 prompts
– PDF + TXT
– AI twin design
– Voice preservation
– Digital memory kit
Would love to hear what you think. It’s here: misbah4.gumroad.com/l/vkeznd?l…
Do you think this idea has a future?
600 Prompt to Preserve Your Voice Beyond Time
🕯️ 600 AI-crafted prompts to preserve your voice, values, and memories — even after you're gone.Not just a prompt pack. A digital legacy vault. Create messages for the future, build your AI twin, and echo forever.Gumroad
Windows 11 finally overtakes Windows 10
We're number 1! Windows 11 finally overtakes Windows 10
: Three months to go until support ends, and Microsoft's flagship operating system squeaks past its predecessorRichard Speed (The Register)
Texas lawmakers failed to pass a bill to improve local flood warning systems this year
Bill to boost disaster warning systems died in Legislature
A GOP state lawmaker who represents Kerr County says he likely would vote differently now on House Bill 13, which would have established a grant program for counties to build new emergency communication infrastructure.Terri Langford (The Texas Tribune)
Get me out of here. I already use FOSS*, tell me what license to use and I can also do testing (both bug reports and medical/biomech stuff).
I know, probably not even close to a real option. Same as it ever was.
* Godot, Blender, Krita, Linux etc
How the hell did we get here?
How the hell did we get here?
Explaining the Right is a weekly series that looks at what the right wing is currently obsessing over, how it influences politics—and why you need to know. It’s been a tumultuous 6 months with ...Daily Kos
Daily Kos is moving to WordPress
Daily Kos is moving to WordPress
For most of its existence, Daily Kos has run on custom-built publishing platforms. That might’ve made sense a decade or two ago, but now it’s expensive, outdated, and difficult to maintain. ...Daily Kos
'Exactly What We Would Expect': Climate Scientists Weigh in on Deadly Texas Flooding
'Exactly What We Would Expect': Climate Scientists Weigh in on Deadly Texas Flooding
"It's not a question of whether climate change played a role—it's only a question of how much," said one expert.brett-wilkins (Common Dreams)
AI Utopia, AI Apocalypse, and AI Reality: If we can’t build an equitable, sustainable society on our own, it’s pointless to hope that a machine that can’t think straight will do it for us.
AI Utopia, AI Apocalypse, and AI Reality
If we can’t build an equitable, sustainable society on our own, it’s pointless to hope that a machine that can’t think straight will do it for us.richard-heinberg (Common Dreams)
AI Utopia, AI Apocalypse, and AI Reality: If we can’t build an equitable, sustainable society on our own, it’s pointless to hope that a machine that can’t think straight will do it for us.
AI Utopia, AI Apocalypse, and AI Reality
If we can’t build an equitable, sustainable society on our own, it’s pointless to hope that a machine that can’t think straight will do it for us.richard-heinberg (Common Dreams)
Healy Pass Trail Banff National Park, AB
A wonderful hike that spends half of it’s time rising among expansive meadows, seasonally filled with glacier lilies. It begins at the Sunshine village ski resort and maintains a steady uphill throughout the majority of the hike, increasing as you reach the pass. Access to multiple different trails along route.
Looking back into the meadow from near the top of Healy Pass. Glacier lilies dot the lamdscape while The Monarch (right) and the various mountains nearby Mt Jimmie Simpson hang on to the last of their snow.
A thin snowpatch remains at the top of Healy pass as you look towards the Monarch with an unnamed seasonal pond in the bowl below.
Looking back from the top of Healy Pass towards Mt Jimmy Simpson. Various small ponds may be seen in the valley with the trees below. Smoke from the east made it a little hazy.
FundMECFS likes this.
"I Smell and See Burned Bodies All the Time": Israeli Soldier Commits Suicide After Taking Part in Gaza Genocide and Lebanon War
Occupied Palestine (Quds News Network)- A 24-year-old Israeli soldier living in occupied Safad, called Daniel Edri, set himself on fire yesterday. His burned body was found inside his car in a forest near Safad. Edri had served in both the Gaza Strip and Lebanon during his reserve duty.
The soldier’s mother said: “He told me he had seen horrors and said, ‘Mom, I constantly smell the burned bodies and see them everywhere.'”
btw
who is Jeff Goldberg?
pbs.org/weta/washingtonweek/ab…
Jeffrey Goldberg
Jeffrey Goldberg joined The Atlantic in 2007 as a national correspondent and in 2016 was named the magazine’s 15th editor in chief.Washington Week with The Atlantic
Unlocking the Legacy of the Honda Acty Across Four Generations
For more than four decades, the Honda Acty was a quiet workhorse in Japan’s landscape — effortlessly maneuvering through rice fields, mountain roads, and crowded city alleys. Compact, capable, and cleverly engineered, the Acty became a symbol of efficiency in motion.
In this post, we unlock the legacy of the Honda Acty, exploring all four generations of this iconic kei truck and the lasting impact it left on both Japanese industry and global car culture.
🔑 What Made the Acty Special?
The Acty was Honda’s answer to Japan’s unique kei vehicle regulations — strict rules on size, weight, and engine displacement meant for creating ultra-compact, fuel-efficient vehicles. But the Acty stood out not just because it followed the rules — it maximized them.
“Acty” = Activity — Named to reflect its purpose: getting work done.
Designed for urban agility, rural reliability, and mechanical simplicity.
Used by everyone from delivery drivers to farmers, firefighters to outdoor enthusiasts.
🚙 1st Generation (1977–1988): Simple, Strong, and Surprisingly Capable
Engine: 545cc EH SOHC 2-cylinder
Layout: Mid-engine, rear-wheel drive
Top Traits: Lightweight, easy to repair, great visibility
The original Acty focused purely on function. Its mid-engine setup offered a balanced load and excellent maneuverability — ideal for narrow streets and tight job sites. No luxury here — just a steel cabin, flat bed, and bulletproof simplicity.
Legacy Highlight:
The 1st-gen Acty cemented Honda’s place in the kei truck market and earned a reputation for reliability that persists to this day.
🛞 2nd Generation (1988–1999): Power and Possibility
Engine: 547cc → upgraded to 656cc E07A
New Features:
4WD availability
5-speed manual and 3-speed auto options
Special Editions: Attack, Crawler, Street
This generation expanded the Acty’s reach. Now available in 4WD, with improved torque and gearing, the Acty could climb hills, navigate snow, and even hit trails. The “Attack” version became a favorite among off-roaders thanks to its low-range gearbox.
Legacy Highlight:
The 2nd-gen Acty is still sought after in the import market for its blend of old-school simplicity and real-world utility.
🛡️ 3rd Generation (1999–2009): Smart Utility Meets Safety
Engine: 656cc E07Z (fuel-injected)
Features:
Airbags, ABS, and optional power steering
More refined suspension
Better cabin ergonomics
As kei regulations tightened, the 3rd-gen Acty adapted. It retained its work-ready bones but added enough comfort for daily drivers and delivery crews. It struck a perfect balance: just modern enough to be convenient, still simple enough to be reliable.
Legacy Highlight:
It made the Acty more accessible to a wider range of users, from tradespeople to kei van enthusiasts.
🚦 4th Generation (2009–2021): The Final Evolution
Engine: 656cc E07Z (~44 hp)
Chassis Codes: HA8 (2WD) / HA9 (4WD)
Upgrades:
Dual airbags
Compact 1.9-meter wheelbase
2018 “Spirit Colour Style” tribute to the Honda T360
Honda’s last Acty generation focused on refinement. It was quieter, safer, and easier to drive — but still very much a kei truck. It wasn’t flashy. It didn’t need to be. It just worked, until the very end.
Legacy Highlight:
The 4th-gen Acty bowed out gracefully, leaving behind a 44-year legacy as one of Japan’s greatest micro-utility vehicles.
🌍 Global Impact: Why the Acty Still Matters
Imported worldwide for off-road use, farm work, or JDM collecting
Customizable: Lift kits, camper builds, street mods
Affordable and efficient, with parts support still strong for most generations
A cult icon in the kei car and microtruck communities
Even after production ended in 2021, the Honda Acty continues to thrive — thanks to its durable design, timeless form, and the global love for practical vehicles that refuse to quit.
🏁 Final Thoughts: A Kei-Sized Legend
Unlocking the legacy of the Honda Acty isn’t just about engines or model years — it’s about how a tiny truck became a giant in everyday usefulness. Across its four generations, the Acty evolved with the times, but never lost sight of what mattered: doing more with less.
Whether you’re restoring a vintage 1st-gen, off-roading in a 2nd-gen “Attack,” or commuting in a clean 4th-gen van, you’re part of a legacy built on reliability, adaptability, and good old-fashioned Honda engineering.
Honda Acty Mini Truck - Overview – Generations, Specifications, & Key Features
At Oiwa Garage, we specialize in the customization and enhancement of Honda Acty mini trucks, transforming these compact yet powerful vehicles into unique, performance-oriented machines....Oiwa Garage
Unlocking the Legacy of the Honda Acty Across Four Generations
For more than four decades, the Honda Acty was a quiet workhorse in Japan’s landscape — effortlessly maneuvering through rice fields, mountain roads, and crowded city alleys. Compact, capable, and cleverly engineered, the Acty became a symbol of efficiency in motion.
In this post, we unlock the legacy of the Honda Acty, exploring all four generations of this iconic kei truck and the lasting impact it left on both Japanese industry and global car culture.
🔑 What Made the Acty Special?
The Acty was Honda’s answer to Japan’s unique kei vehicle regulations — strict rules on size, weight, and engine displacement meant for creating ultra-compact, fuel-efficient vehicles. But the Acty stood out not just because it followed the rules — it maximized them.
“Acty” = Activity — Named to reflect its purpose: getting work done.
Designed for urban agility, rural reliability, and mechanical simplicity.
Used by everyone from delivery drivers to farmers, firefighters to outdoor enthusiasts.
🚙 1st Generation (1977–1988): Simple, Strong, and Surprisingly Capable
Engine: 545cc EH SOHC 2-cylinder
Layout: Mid-engine, rear-wheel drive
Top Traits: Lightweight, easy to repair, great visibility
The original Acty focused purely on function. Its mid-engine setup offered a balanced load and excellent maneuverability — ideal for narrow streets and tight job sites. No luxury here — just a steel cabin, flat bed, and bulletproof simplicity.
Legacy Highlight:
The 1st-gen Acty cemented Honda’s place in the kei truck market and earned a reputation for reliability that persists to this day.
🛞 2nd Generation (1988–1999): Power and Possibility
Engine: 547cc → upgraded to 656cc E07A
New Features:
4WD availability
5-speed manual and 3-speed auto options
Special Editions: Attack, Crawler, Street
This generation expanded the Acty’s reach. Now available in 4WD, with improved torque and gearing, the Acty could climb hills, navigate snow, and even hit trails. The “Attack” version became a favorite among off-roaders thanks to its low-range gearbox.
Legacy Highlight:
The 2nd-gen Acty is still sought after in the import market for its blend of old-school simplicity and real-world utility.
🛡️ 3rd Generation (1999–2009): Smart Utility Meets Safety
Engine: 656cc E07Z (fuel-injected)
Features:
Airbags, ABS, and optional power steering
More refined suspension
Better cabin ergonomics
As kei regulations tightened, the 3rd-gen Acty adapted. It retained its work-ready bones but added enough comfort for daily drivers and delivery crews. It struck a perfect balance: just modern enough to be convenient, still simple enough to be reliable.
Legacy Highlight:
It made the Acty more accessible to a wider range of users, from tradespeople to kei van enthusiasts.
🚦 4th Generation (2009–2021): The Final Evolution
Engine: 656cc E07Z (~44 hp)
Chassis Codes: HA8 (2WD) / HA9 (4WD)
Upgrades:
Dual airbags
Compact 1.9-meter wheelbase
2018 “Spirit Colour Style” tribute to the Honda T360
Honda’s last Acty generation focused on refinement. It was quieter, safer, and easier to drive — but still very much a kei truck. It wasn’t flashy. It didn’t need to be. It just worked, until the very end.
Legacy Highlight:
The 4th-gen Acty bowed out gracefully, leaving behind a 44-year legacy as one of Japan’s greatest micro-utility vehicles.
🌍 Global Impact: Why the Acty Still Matters
Imported worldwide for off-road use, farm work, or JDM collecting
Customizable: Lift kits, camper builds, street mods
Affordable and efficient, with parts support still strong for most generations
A cult icon in the kei car and microtruck communities
Even after production ended in 2021, the Honda Acty continues to thrive — thanks to its durable design, timeless form, and the global love for practical vehicles that refuse to quit.
🏁 Final Thoughts: A Kei-Sized Legend
Unlocking the legacy of the Honda Acty isn’t just about engines or model years — it’s about how a tiny truck became a giant in everyday usefulness. Across its four generations, the Acty evolved with the times, but never lost sight of what mattered: doing more with less.
Whether you’re restoring a vintage 1st-gen, off-roading in a 2nd-gen “Attack,” or commuting in a clean 4th-gen van, you’re part of a legacy built on reliability, adaptability, and good old-fashioned Honda engineering.
Honda Acty Mini Truck - Overview – Generations, Specifications, & Key Features
At Oiwa Garage, we specialize in the customization and enhancement of Honda Acty mini trucks, transforming these compact yet powerful vehicles into unique, performance-oriented machines....Oiwa Garage
TikTok’s Escape Plan May Be a Brand New App
TikTok's Escape Plan May Be a Brand New App
With a September deadline looming, a new report says TikTok is building a replacement app for its 170 million American users as part of a sale to an Oracle led group.Luc Olinga (Gizmodo)
Honda Acty 1.0 to 4.0: The Full Generational Breakdown
From its debut in the late 1970s to its final production run in 2021, the Honda Acty has been one of Japan’s most trusted kei-class utility trucks. Built for tight spaces, light loads, and daily reliability, the Acty has earned a loyal following in Japan — and increasingly, around the world.
In this post, we present a full “version-by-version” breakdown of the Honda Acty — from 1.0 to 4.0 — showing how this mini truck evolved across four generations, while staying true to its mission: compact practicality with a work-ready attitude.
🚛 Acty 1.0 – The Original (1977–1988)
🔧 Overview:
Engine: 545cc EH SOHC 2-cylinder
Drive Layout: Mid-engine, RWD
Body Styles: Truck and van
Transmission: 4-speed manual
Top Speed: ~90 km/h (~56 mph)
The first-gen Acty was a true utility-first kei truck. Introduced in 1977, it emphasized simple engineering, cargo efficiency, and a narrow body — perfect for Japan’s urban and rural roads.
⭐ Highlights:
Flat cargo bed with a low loading height
Rugged and incredibly reliable
No frills — just a tough little worker
⚙️ Acty 2.0 – Power & Versatility (1988–1999)
🔧 Overview:
Engine: 547cc E05A → later 656cc E07A
Drive Options: 2WD / 4WD
Transmissions: 5-speed manual or 3-speed auto
Notable Variants: Attack (off-road), Street (van), Crawler (6-wheel)
The second generation brought major upgrades: a more powerful engine, optional 4WD, and the addition of trims tailored to different environments — including the legendary Acty Attack, built for rough terrain with low gearing and diff lock.
⭐ Highlights:
Introduction of 4WD and auto transmission
Larger engine with better reliability
Most collectible generation among enthusiasts
🛡️ Acty 3.0 – The Safe Workhorse (1999–2009)
🔧 Overview:
Engine: 656cc E07Z (fuel-injected)
Chassis Codes: HA6/HA7 (truck), HH5/HH6 (van)
Safety: Dual airbags, optional ABS
Comfort: Better seats, optional A/C & power steering
The 3rd-gen Acty entered the modern kei era, focused on driver comfort and safety without abandoning its utilitarian roots. It retained the same engine displacement but adopted fuel injection for smoother performance and efficiency.
⭐ Highlights:
Safer and more comfortable for daily driving
Still rugged and highly customizable
A great balance of old-school simplicity with modern touches
🚦 Acty 4.0 – The Final Evolution (2009–2021)
🔧 Overview:
Engine: 656cc E07Z, ~44 hp
Chassis Codes: HA8 (2WD), HA9 (4WD)
Wheelbase: Ultra-short 1.9 meters
Upgrades: Dual airbags, ABS, quieter cabin
The final generation was the most refined. It retained much of the tried-and-tested engineering while adding modern safety, noise reduction, and a tighter turning radius. Unfortunately, it was also the last — Honda ceased production in April 2021 due to rising compliance costs.
⭐ Highlights:
Peak maneuverability for city use
Still available in 4WD
2018 special edition honored Honda’s T360 heritage
📊 Acty Generational Comparison Table
Gen Years Engine Layout Key Features
1.0 1977–1988 545cc EH Mid-engine RWD Lightweight, reliable, no-frills
2.0 1988–1999 547→656cc E07A Mid-engine RWD/4WD Attack & Crawler variants, more power
3.0 1999–2009 656cc E07Z Mid-engine RWD/4WD Fuel injection, safety features, better ride
4.0 2009–2021 656cc E07Z Mid-engine RWD/4WD ABS, airbags, compact wheelbase, modernized
🏁 Final Thoughts: A Legacy in Four Acts
From 1.0 to 4.0, the Honda Acty tells a story of thoughtful, incremental improvement. While kei trucks may look simple from the outside, the Acty is a masterclass in efficient engineering. Whether you’re hauling lumber, navigating a mountain trail, or just enjoying a slice of JDM life — there's a generation of Acty built for you.
Would you like me to turn this into a downloadable buyer’s guide, or add import tips for each generation?
Honda Acty Mini Truck - Overview – Generations, Specifications, & Key Features
At Oiwa Garage, we specialize in the customization and enhancement of Honda Acty mini trucks, transforming these compact yet powerful vehicles into unique, performance-oriented machines....Oiwa Garage
Stop killing games and the industry response
My blog, where I attempt to collect my thoughts and share the occasional interesting topic with others
TikTok to Launch US-Only App Ahead of Potential Ownership Change
TikTok to Launch US-Only App Ahead of Potential Ownership Change - The Mac Observer
TikTok will launch a US-only app on September 5 as part of a sale deal aimed at addressing national security concerns.Rajat Saini (The Mac Observer)
‘Improved’ Grok criticizes Democrats and Hollywood’s ‘Jewish executives’
‘Improved’ Grok criticizes Democrats and Hollywood’s ‘Jewish executives’ | TechCrunch
On Friday morning, Elon Musk declared, “We have improved @Grok significantly. You should notice a difference when you ask Grok questions.”Anthony Ha (TechCrunch)
FundMECFS likes this.
Whistleblower: Huawei cloned and renamed Qwen and DeepSeek models, claimed as own
A now-deleted report by HonestAGI on GitHub showed a high number of similarities between Huawei’s Pangu and Qwen 2.5.
Decrypted Generative Model safety files for Apple Intelligence containing filters
Decrypted Generative Model safety files for Apple Intelligence containing filters - BlueFalconHD/apple_generative_model_safety_decrypted
France | Paris reopens River Seine to public swimming after century-long ban
About 1,000 swimmers a day will be allowed to use three bathing sites after €1.4bn clean-up programme
Archived version: archive.is/newest/theguardian.…
Disclaimer: The article linked is from a single source with a single perspective. Make sure to cross-check information against multiple sources to get a comprehensive view on the situation.
Carlos Solís
in reply to shrewdcat • • •Linux reshared this.
Luca
in reply to Carlos Solís • • •Looks like it does? Or at least could?
unix.stackexchange.com/questio…
I've never seen one so far though
trevor (he/they)
in reply to Carlos Solís • • •I've packaged a CLI that I made as a flatpak. It works just fine. Nothing weird was required to make it work.
The only thing is that if you want to use a CLI flatpak, you probably want to set an alias in your shell to make running it easier.
I'm not sure why more CLIs aren't offered as flatpaks. Maybe because static linking them is so easy? I know people focus on flatpak sandboxing as a primary benefit, but I can't help but think of static linking was easier for bigger applications, it wouldn't be needed as much.
like this
Carlos Solís likes this.
brianary
in reply to shrewdcat • • •Linux reshared this.
eta
in reply to brianary • • •Linux reshared this.
Damage
in reply to eta • • •brianary
in reply to eta • • •eta
in reply to brianary • • •brianary
in reply to eta • • •eta
in reply to brianary • • •brianary
in reply to eta • • •paequ2
in reply to brianary • • •I used Flatpak Zoom for all my job interviews recently. Camera and mic worked flawlessly.
brianary
in reply to paequ2 • • •Allero
in reply to paequ2 • • •Axum
in reply to shrewdcat • • •Flatpaks are good, especially compared to snap.
The future is atomic OS's like silverblue, which will make heavy use of things like flatpak.
Yozul
in reply to Axum • • •HayadSont
in reply to Yozul • • •As it stands, I kinda agree. But I truly wonder to what extent we might be able to close the current gap.
SpaceNoodle
in reply to Axum • • •Libra00
in reply to SpaceNoodle • • •qt0x40490FDB
in reply to Libra00 • • •ℍ𝕂-𝟞𝟝
in reply to Libra00 • • •SatyrSack
in reply to Libra00 • • •aksdb
in reply to SatyrSack • • •SpaceNoodle
in reply to Libra00 • • •HayadSont
in reply to SpaceNoodle • • •~~> plus sudden updates that nuke active applications.~~
~~This is not what's supposed to happen. If an app installed through flatpak is active while it's receiving an update, then the update is not supposed to affect the running application until it's closed/restarted.~~
Edit: Somehow I didn't realize the concern was raised against Snap and not Flatpak.
Joël de Bruijn
in reply to HayadSont • • •HayadSont
in reply to Joël de Bruijn • • •SpaceNoodle
in reply to HayadSont • • •HayadSont
in reply to SpaceNoodle • • •aksdb
in reply to HayadSont • • •First_Thunder
in reply to Libra00 • • •Caveman
in reply to Axum • • •Snap is not all bad if you're on a Ubuntu based distro, I just don't like the way it's pushed and that it comes from Ubuntu mostly. Startup time is a major issue for me also, but all in all it works.
I'm still sitting on the fence, heavily prefer flatpak but when Ubuntu is going to package nvidia drivers in a snap it's a thing I'm up for trying.
My understanding is that if I'm on Ubuntu and the snap uses the same underlying Ubuntu version as my distro it should be fast but I haven't seen it.
olenko
in reply to Axum • • •Axum
in reply to olenko • • •lordnikon
in reply to shrewdcat • • •katy ✨
in reply to shrewdcat • • •muzzle
in reply to katy ✨ • • •Snot Flickerman
in reply to muzzle • • •Yozul
in reply to muzzle • • •muzzle
in reply to Yozul • • •Yozul
in reply to muzzle • • •RedSnt 👓♂️🖥️
in reply to muzzle • • •MotoAsh
in reply to RedSnt 👓♂️🖥️ • • •Thorned_Rose
in reply to MotoAsh • • •muzzle
in reply to RedSnt 👓♂️🖥️ • • •comfy
in reply to muzzle • • •HayadSont
in reply to comfy • • •flatpak uninstall --unusedright after uninstalling a flatpak. I don't get why it doesn't do this automatically. Granted, some distro package managers (used to) operate somewhat similarly in that they required theautoremoveoption.comfy
in reply to HayadSont • • •flatpak uninstall --unusedand it didn't remove these ones. So there's something odd going on there. My guess is maybe Mint manually installed them through the driver manager program? That's a wild guess, I don't know how it works.comfy
in reply to katy ✨ • • •ZWQbpkzl [none/use name]
in reply to shrewdcat • • •IDK why you're being so rage baity. Its easy to avoid flatpaks if you dont like them. Only thing I've ever found as an obstacle was adding the binaries to my PATH so I can launch it with dmenu_run. Otherwise my package manager works well enough.
Bonus points: Write a PKGBUILD that installs flatpaks to /opt and symlink out binaries as needed.
shrewdcat
in reply to ZWQbpkzl [none/use name] • • •ZWQbpkzl [none/use name]
in reply to shrewdcat • • •anarchoilluminati [comrade/them]
in reply to ZWQbpkzl [none/use name] • • •Well, I heard that people who use flatpacks are libs. True?
Sorry, I just think it's funny that Linux users get so defensive about this stuff. You really felt insulted by this?
ZWQbpkzl [none/use name]
in reply to anarchoilluminati [comrade/them] • • •Horse {they/them}
in reply to shrewdcat • • •shrewdcat
in reply to Horse {they/them} • • •Ephera
in reply to Horse {they/them} • • •cmgvd3lw
in reply to shrewdcat • • •NotSteve_
in reply to shrewdcat • • •I love installing things from the CLI and prefer to only do it that way but Linux needs a single click install method for applications if it’s ever going to become a mainstream OS. The average person just wants to Google a program, hit download and install. If not that then they want to use a mobile-like App Store.
Flatpak is kind of perfect at achieving both those things
SpaceNoodle
in reply to NotSteve_ • • •NotSteve_
in reply to SpaceNoodle • • •Oh 100% but have you tried to explain how to use one to a computer novice? Like yes, the answer is usually “they should just…” but novice users will never. With flatpak, they get an experience similar to how MacOS works and a bit like how .exes work and it Just Works™️
Edit: like I’ve had trouble showing people how to use the GNOME App Store which could not be any more simple. Anyone who has been convinced to install Linux already feels way out of their element so making everything feel as natural as possible is essential (and I mean, flatpaks are awesome anyway)
Ziglin (it/they)
in reply to NotSteve_ • • •Caveman
in reply to Ziglin (it/they) • • •Ziglin (it/they)
in reply to Caveman • • •Caveman
in reply to Ziglin (it/they) • • •Ziglin (it/they)
in reply to Caveman • • •BCsven
in reply to NotSteve_ • • •OpenSUSE has OneClick install for RPMs. en.opensuse.org/openSUSE:One_C…
Edit: and if you happen to download an rpm, you just double click it in the filemanager (or single click if that is your setting) and it launces the install GUI.
Its similar to how MSI file install looks...just next next finish kind of thing
openSUSE:One Click Install - openSUSE Wiki
en.opensuse.orgNotSteve_
in reply to BCsven • • •thingsiplay
in reply to NotSteve_ • • •BCsven
in reply to NotSteve_ • • •NotSteve_
in reply to BCsven • • •m532
in reply to NotSteve_ • • •Just go to the package manager, type in the name of the program, install.
That's easier than on windows: go to the browser, search for the program, avoid the ads, search for the download button, follow the install wizard, avoid the toolbar
corsicanguppy
in reply to shrewdcat • • •Former OS security here (I worked at an OS vendor who sold an OS or two and my job involved keeping it secure).
Fuck no.
Sorry if that makes you downvote, but it doesn't make them safer.
giacomo
in reply to corsicanguppy • • •HayadSont
in reply to corsicanguppy • • •zarenki
in reply to HayadSont • • •A few reasons security people can have to hesitate on Flatpak:
By a typical home user's perspective this probably seems like nothing; in terms of security you're still usually better off with Flatpak than installing random AUR packages, adding random PPA repos, using AppImage programs, installing a bunch of Steam games, blindly building an unfamiliar project you cloned from github, or running bash scripts you find online. But in many contexts none of that is acceptable.
eta
in reply to zarenki • • •MotoAsh
in reply to eta • • •I mean, they added "bash scripts you find online", which are only a problem if you don't look them over or cannot understand them first... Their post is very much cemented in the paranoid camp of security.
Not that they're wrong. That's the big thing about security once you go deep enough: the computer has to work for someone, and being able to execute much at all opens up some avenues of abuse. Like securing a web based service. It has to work for someone, so of course everything is still vulnerable at some point. Usually when private keys or passwords are compromised if they're doing things remotely correctly, but they're still technically vulnerable at some point.
zarenki
in reply to MotoAsh • • •The parent comment mentions working on security for a paid OS, so looking at the perspective of something like the users of RHEL and SUSE: supply chain "paranoia" absolutely does matter a lot to enterprise users, many of which are bound by contract to specific security standards (especially when governments are involved). I noted that concerns at that level are rather meaningless to home users.
On a personal system, people generally do whatever they need to in order to get the software they want. Those things I listed are very common options for installing software outside of your distro's repos, and all of them offer less inherent vetting than Flathub while also tampering with your system more substantially. Though most of them at least use system libraries.
I would honestly expect that the vast majority of people who see installation steps including
curl [...] | sh(so common that even reputable projects like cargo/rust recommend it) simply run the command as-is without checking the downloaded script, and likewise do the same even if it'ssudo sh. That can still be more or less fine if you trust the vendor/host, its SSL certificate, and your ability to type/copy the domain without error. Even if you look at the script, that might not get you far if it happens to be a self-extracting one unless you also check its payload.Installation - The Cargo Book
doc.rust-lang.orgMotoAsh
in reply to zarenki • • •D_Air1
in reply to shrewdcat • • •I used them for some things, but other things still don't work quite right. Take Steam for example. I do love flatpaks for testing out apps, things with really finicky dependencies, or pinning a specific version of a software that I want to continue to work in the future. However, for most things, Arch + AUR just covers all my needs without any hiccups.
To me flatpaks are sort of like NixOS. All the benefits they provide aren't something I need on a daily basis. Rolling back works just fine 99% of the time with
downgrade. I already have system backups. Despite what some articles might insist, things don't just break all the time. I'm not running untrusted software.Basically no solution is perfect, but they don't need to be. If the benefits I gain can be recreated through other methods without the tradeoffs they introduce, then I will go with that. Of course, that isn't to say they don't have their place, but sometimes I feel like some people think that "being designed from the ground up" to handle certain use cases is always better than whatever "cobbled together" thing we currently have and that isn't always the case. I'm specifically quoting those two phrases because these are the exact phrases you will hear projects using to justify their existence. In fact, I would go so far as to say that some people have outright confused modularity for "cobbled together".
One last example I want to make is that I make use of projects like the fish shell and helix editor. In these cases, I find the features they introduce to be worth the tradeoffs and work better because of being designed "from the ground up" to do what they do. However, I don't make use of immutable systems, containers such as docker, or say filesystems such as btrfs. The features they provide are not useful enough to me compared to the problems they introduce.
thingsiplay
in reply to shrewdcat • • •Flatpak have their own set of issues. One thing is, that Flatpak applications do not integrate that easily and perfect like a native package. Either rights are to given, you need to know what rights are needed and how to set it up. Theming can be an issue, because it uses its own libraries in the Flatpak eco system instead your current distributions theme and desktop environment.
But on the other hand, they have actually a permission system and are a little bit sandbox compared to normal applications. Packages often are distributed quickly and are up to date directly from the developers, and usually are not installed with root rights.
I'm pretty much a CLI guy as well and prefer native packages (Arch based, plus the AUR). But I also use Flatpaks for various reasons, alongside with AppImages.
Drunk & Root
in reply to shrewdcat • • •Mordikan
in reply to shrewdcat • • •eta
in reply to Mordikan • • •Mordikan
in reply to eta • • •atzanteol
in reply to shrewdcat • • •m532
in reply to atzanteol • • •Write name of program
Enter
☂️-
in reply to shrewdcat • • •the_wiz
in reply to shrewdcat • • •buwho
in reply to shrewdcat • • •BrianTheeBiscuiteer
in reply to shrewdcat • • •Uairhahs
in reply to BrianTheeBiscuiteer • • •Unlix86
in reply to BrianTheeBiscuiteer • • •data1701d (He/Him)
in reply to shrewdcat • • •I'd take a well-maintained native package for my distro over a Flatpak, but sometimes, a Flatpak is just the the easiest way to get the latest version of an application working on Debian without too much tinkering - not always no tinkering, but better than nothing.
This is especially true of GIMP - Flatpak GIMP + Resynthesizer feels like the easiest way to experience GIMP these days. Same with OBS - although I have to weather the Flatpak directory structure, plugins otherwise feel easier to get working than the native package. The bundled runtimes are somewhat annoying, but I'm also not exactly hurting for storage at the moment - I could probaby do to put more of my 2 TB main SSD to use.
I usually just manage Flatpaks from the terminal, though I often have to refresh myself on application URLs. I somewhat wish one could set nicknames so they need not remember the full name.
sovietknuckles [she/her]
in reply to shrewdcat • • •underscores
in reply to sovietknuckles [she/her] • • •Me pretty much only ever using arch Linux: "what the fuck is a flatpak"
I once had to install Firefox into wsl (Ubuntu) and I wanted the kms on the spot.
But maybe it's not that bad for newer people to get started with Linux.
Allero
in reply to sovietknuckles [she/her] • • •Dessalines
in reply to Allero • • •Horse {they/them}
in reply to Dessalines • • •Dessalines
in reply to Horse {they/them} • • •Horse {they/them}
in reply to Dessalines • • •the weirdest one was ghostwriter from the official repos, for some reason one day the preview window showed heavily corrupted output and tinkering with it on and off for a week did nothing, including a complete purge and reinstall of the program
the flatpak was the only version of it that worked after that
Allero
in reply to Dessalines • • •chicken
in reply to shrewdcat • • •Default_Defect
in reply to shrewdcat • • •Jankatarch
in reply to Default_Defect • • •brax
in reply to Default_Defect • • •gravitas_deficiency
in reply to Default_Defect • • •It’s extremely context-dependent.
If we’re talking about enterprise-grade, five-nines reliability: I want the absolute simplest, bare-bones, stripped down, optimized infra I can get my hands on.
If we’re talking about my homelab or whatever else non-critical system: I’m gonna fuck around and play with whatever I feel like.
Ferk
in reply to Default_Defect • • •You are mixing different ideas of freedom.
Software freedom is not the same as freedom of choice of software.
You don't need Linux to have choices of what software to use, you have that in most (all?) proprietary systems, in some you might even have more choices than in Linux.. even if it includes proprietary software.
This is analogous to how being a free person (not a slave) is not the same as having freedom to choose who to work for, even if some of them are slavers (ie. having freedom to choose your master).
Lettuce eat lettuce
in reply to shrewdcat • • •Flatpaks are pretty great for getting the latest software without having to have a cutting edge rolling release distro or installing special repos and making sure stuff doesn't break down the line.
I use Flatpaks for my software that I need the latest and greatest version of, and my distros native package for CLI apps and older software that I don't care about being super up to date.
My updater script handles all of it in one action anyways, so no biggie on that either.
Flatpaks are the best all-in-one solution when compared to Appimages or Snaps imo.
m532
in reply to Lettuce eat lettuce • • •Oh, that explains why they're completely bloated & useless to me. Arch btw
The_Grinch [he/him]
in reply to shrewdcat • • •You should only install a flatpak if the program is not available for your OS, or if the native version doesn't work for some reason.
Ardens
in reply to shrewdcat • • •juipeltje
in reply to shrewdcat • • •Korhaka
in reply to shrewdcat • • •Commiunism
in reply to shrewdcat • • •Allero
in reply to shrewdcat • • •Certainly a fan, and I don't understand the hate towards it.
Flatpaks are my preferred way of installing Linux apps, unless it is a system package, or something that genuinely requires extensive permissions like a VPN client, or something many other apps depend on like Wine.
The commonly cited issues with Flatpaks are:
What you gain for it? Everything.
Alternatives?
AppImages don't need an installation, so they are nice to see what the program is about. But for other uses, they are garbage-tier. Somehow they manage both not to integrate with the system and not be sandboxed, you need manual intervention or additional tools to at least update them/add to application menu, and ultimately, they depend on one file somewhere. This is extremely unreliable and one should likely never use AppImages for anything but "use and delete".
Snaps...aside from all the controversy about Snap Store being proprietary and Ubuntu shoving snaps down people's throats, they were just never originally developed with desktop applications in mind. As a result, Snaps are commonly so much slower and bulkier that it actually starts getting very noticeable. Permissions are also way less detailed, meaning you can't set apps up with minimum permissions for your use case.
This all leaves us with one King:
And it is Flatpak.
brax
in reply to Allero • • •Flatpaks, appimages, snaps, etc: why download dependencies once when you can download them every time and bloat your system? Also, heaving to list installed flatpaks and run them is dumb too, why aren't they proper executables? "flatpak run com.thisIsDumb.fuckinEh" instead of just ./fuckinEh
No thanks. I'll stick to repos and manually compiling software before I seek out a flatpak or the like.
This shit is why hobbies and things should be gatekept. Just look at how shit PC design is these days. Now they're coming after the OS.
Allero
in reply to brax • • •As I said, dependencies typically don't take that much space. We're not in the '80s, I can spare some megabytes to ensure my system runs smoothly and is managed well.
As per naming, I agree, but barely anyone uses command line to install Flatpaks, as they are primarily meant for desktop use. In GUI, Flatpaks are shown as any other package, and all it takes is to push "Install" button.
If you want to enjoy your chad geeky Linux, you still can. Go for CachyOS, or anything more obscure, never to use Flatpaks again. At the same time, let others use what is good and convenient to them.
Eyck_of_denesle
in reply to Allero • • •Jakeroxs
in reply to Eyck_of_denesle • • •Allero
in reply to Eyck_of_denesle • • •Please clarify, what option do you mean? Flatpaks are supported on any Linux system, it doesn't matter what distro or hardware. Or if you mean sparing some megabytes - typically yes as well. The smallest amount of memory I've seen on a laptop is 32gb, and typically it's no less than 250gb.
If it's not present in you distributions' app store, you can either enable it somewhere or download another app manager like Discover, GNOME Software, or pamac if you're on Arch.
If installation of some app incurs a few gbs of downloads, it is likely that your system updates packages alongside installing your app. Typical Flatpak app takes 10-150 megabytes.
Eyck_of_denesle
in reply to Allero • • •Allero
in reply to Eyck_of_denesle • • •nitrolife
in reply to Allero • • •I've been working on Linux for 15 years now and I perfectly remember the origin of many concepts. If you look at it through time, what would it be like:
1. We can build applications with external dependencies or a single binary, what should we choose?
2. The community is abandoning a single binary due to the increased weight of applications and memory consumption and libraries problems
3. Dependency hell is coming
...
4. Snap, flatpack, appimage and other strange solutions are inventing something, which are essentially a single binary, but with an overlay (if the developer has hands from the right place, which is often not the case)
5. Someone on lemmy says that he literally doesn't care if the application is built in a single binary, consumes extra memory and have libraries problems. Just close all permissions for that application...
Well, all I can say about this is just assemble a single binary for all applications, stop doing nonsense with a flatpack/snap/etc.
UPD: or if you really want to break all the conventions, just use nixos. You don't need snap/flatpack/etc.
Allero
in reply to nitrolife • • •I don't mind other solutions, as long as they have the key features Flatpak offers, namely:
* Being open-source
* Having app permission system
* Having bundled dependencies
* Integrating decently with the system
Times are changing, and memory constraints for most programs are generally not relevant anymore.
grinka
in reply to nitrolife • • •Papamousse
in reply to nitrolife • • •JustEnoughDucks
in reply to Allero • • •The few things I don't like about flatpaks (which become a problem on atomic distros that use almost all flatpak by design):
But besides those small things, it seem great to me.
Allero
in reply to JustEnoughDucks • • •arsCynic
in reply to Allero • • •Eyck_of_denesle
in reply to Allero • • •Allero
in reply to Eyck_of_denesle • • •It would take 1,01gb
Dependencies typically take 5-80 megabytes of space.
Eyck_of_denesle
in reply to Allero • • •Allero
in reply to Eyck_of_denesle • • •Huh?
Either it did something it shouldn't, or the system updated Nvidia drivers every time for no apparent reason. I have an Nvidia GPU, running proprietary drivers, and haven't ever witnessed anything of the kind.
frozenspinach
in reply to Allero • • •Allero
in reply to frozenspinach • • •Wow that's actually big difference, thanks for bringing it up!
Good news, though, is that you are free to install Gimp as a native package, and use Flatpaks for the rest.
j0rge
in reply to Allero • • •Install GNU Image Manipulation Program on Linux | Flathub
Flathubm532
in reply to shrewdcat • • •Idk how, but one time I tried installing something as a flatpak and it took like 300+MB and a very long time. I figured something was wrong, found a way to install it normally and it took like 10MB and installed quickly. Idk what went wrong, but I'll never touch this garbage again
Edit: oh they're not for arch. Maybe they should have told me before the 300mb slog
zeca
in reply to m532 • • •m532
in reply to zeca • • •HexesofVexes
in reply to shrewdcat • • •Honestly, I am a little scarred from snap.
Otherwise I'm agnostic on flatpaks - I've used a couple and they're ok? They just remind me of old windows games that dump all their libraries in a folder with them.
On a modern system the extra space and loss of optimisation is ok, but on older hardware or when you're really trying to push your system to run something it technically shouldn't, I can see it being an issue.
ter_maxima
in reply to shrewdcat • • •I've heard Flatpaks aren't great at CLI tools, is that true ?
As a Nix user, I'm glad Flatpaks exist for other people, but I only ever use them when a package is not available from Nix directly. Seeing as Nix is literally the biggest package manager out there, it's a pretty rare occurrence.
pineapple
in reply to ter_maxima • • •trevor (he/they)
in reply to ter_maxima • • •I posted this in another thread, but reposting here because a lot of people, including myself up until very recently, were under that impression:
I've packaged a CLI that I made as a flatpak. It works just fine. Nothing weird was required to make it work.
The only thing is that if you want to use a CLI flatpak, you probably want to set an alias in your shell to make running it easier.
I'm not sure why more CLIs aren't offered as flatpaks. Maybe because static linking them is so easy? I know people focus on flatpak sandboxing as a primary benefit, but I can't help but think that if static linking was easier for bigger applications, it wouldn't be needed as much.
BudgetBandit
in reply to shrewdcat • • •pineapple
in reply to shrewdcat • • •I am definitely a fan. A lot of people say that flatpaks are bad because of sandboxing but I haven't seemed to have any issues with it.
Although I do try to use dnf when a dnf package is available (I use fedora)
Bjarne
in reply to shrewdcat • • •iit: nerds unable to comprehend that building a piece of software from source in not something every person can do.
EDIT: or doesn’t want to do
𝕛𝕨𝕞-𝕕𝕖𝕧
in reply to Bjarne • • •one of my least favorite things about arch and other rolling distros is that yay/pacman will try and recompile shit like electron/chromium from source every few days unless you give it very specific instructions not to - which is annoying as shit bc compiling the entirety of chrome from source takes hours even with decent hardware.
granted, i fucking hate google products too but if you’re doing any web dev it’s necessary sometimes.
idk im definitely willing to admit i might be the idiot here. managing your packages with pacman might just be routine to some people. to me arch is the epitome of classic bad UX in an open source project. it’s like they got too focused on being cmatrix-style terminal nerds and forgot to make their software efficiently useable outside of 5 very specific people’s workflows. it’s not even the terminal usage that is bad about arch. plenty of things are focused on that and… don’t do it shittily? idk…
edit: yes to all the arch fanboy’s points in response to me. i used to be super into arch and am aware of the fact that this isn’t explicit behavior but to act like it doesn’t happen in a typical arch user experience is disingenuous. i also disagree with the take that arch doesn’t endorse this outright with its design philosophy, bc it does. the comparison of the AUR to other, similar things like PPAs doesn’t land for me bc PPAs aren’t integrated into the ecosystem nearly as much as AUR is with arch. you can’t tell people to just grab the binaries or not use AUR whenever it’s convenient to blame the user, when arch explicitly endorses a philosophy amicable to self-compilation and also heavily uses the AUR even in their own arch-wiki tutorials for fairly basic use cases. arch wants to have its cake and eat it too and be a great DIY build it yourself toolkit while also catering to daily driver use and more generalist users. don’t get me wrong, it’s the best attempt at such a thing i’ve seen - but at a certain point you have to ask if the premise makes sense anymore. in the case of arch, it doesn’t and it causes several facets of the ecosystem to flounder from a user perspective. the arch community’s habit of shouting “skill issue” at people when they point out legitimate issues with the design philosophy bugs the fuck out of me. this whole OS is a camel.
ahoneybun
in reply to 𝕛𝕨𝕞-𝕕𝕖𝕧 • • •Jhex
in reply to 𝕛𝕨𝕞-𝕕𝕖𝕧 • • •𝕛𝕨𝕞-𝕕𝕖𝕧
in reply to Jhex • • •is garuda like endeavorOS or manjaro where it’s technically still an arch-based rolling release distro but the OS maintainers hold packages from upstream mainline arch?
i don’t hate that model, it’s more fun to use as an end user for sure, but i feel like it kind of defeats the point of arch’s entire ethos lmao.
Spectrism
in reply to 𝕛𝕨𝕞-𝕕𝕖𝕧 • • •𝕛𝕨𝕞-𝕕𝕖𝕧
in reply to Spectrism • • •sometimes you’re working with particular releases or builds that don’t, but like i said i might be the idiot lol.
i like the concept of arch. i don’t like the way i need to come up with a new solution for how im managing my packages virtually every few days that often requires novel information. shit, half the time you boot up an arch system if you have sufficient # of packages there is 9/10 times a conflict when trying to just update things naively. like i said it’s cool on paper and im sure once you use it as a daily driver for awhile it just becomes routine but it’s more the principle of the user experience and its design philosophy that i think might be poor.
arch is for techies in the middle of the bell curve imo… people on the left and the right, when it comes to something as simple as managing all my packages and versions, want something that just works^TM^ - unless i specifically want to fuck with the minutiae.
Feyd
in reply to 𝕛𝕨𝕞-𝕕𝕖𝕧 • • •Sounds like AUR problems. IMO using AUR helpers that tie AUR packages to your full system update command is a trap. AUR never professed to be a stable repository (in fact it's the opposite). AUR has a place, but it should be used sparingly and thoughtfully.
𝕛𝕨𝕞-𝕕𝕖𝕧
in reply to Feyd • • •Feyd
in reply to 𝕛𝕨𝕞-𝕕𝕖𝕧 • • •The wiki article :
- specifically says that packages are not thoroughly vetted
- does not recommend using yay or another AUR helper (which is the primary thing I recommend against)
- has a frequently asked question section that is fairly technical and should indicate that it is not for the faint of heart
The aur helper wiki has a fun red disclaimer at the top that no one reads
Arch User Repository - ArchWiki
wiki.archlinux.org𝕛𝕨𝕞-𝕕𝕖𝕧
in reply to Feyd • • •you (rhetorical you, not you) can recommend not using the AUR officially all you want. it doesn’t mean anything if a large number of tasks the average user is going to do require AUR packages. i’m kind of drunk rn but i’ll go find specific pages of the wiki that demonstrate what i’m talking about, i stg this isn’t nothing. the core system itself can entirely be managed with pacman, yes, but the average user is going to be doing a lot more than just that. there is a certain discord in the messaging of arch as a whole.
this is exactly my point. arch can either be a nuts and bolts distro or it can be made for normies. it can’t be both.
Feyd
in reply to 𝕛𝕨𝕞-𝕕𝕖𝕧 • • •elo13
in reply to 𝕛𝕨𝕞-𝕕𝕖𝕧 • • •You keep saying this but can you give any concrete examples? I don't recall coming across anything like this.
ayaya
in reply to 𝕛𝕨𝕞-𝕕𝕖𝕧 • • •All of the normal Arch packages are pre-built, so the only way you'd be compiling things that often is if you installed a large amount of things from the AUR. Make sure you get the bin versions instead of git versions.
The
google-chromeandchromiumpackages are already a binaries so my guess is you needungoogled-chromium-bin. You can also use the Chaotic AUR repo to get pre-built binaries of a lot of the most common AUR packages. But ideally you should avoid using the AUR when it's not necessary.While using the AUR is common, it's a bit frustrating you are blaming Arch for your experience. If you only use pacman you would never compile anything, or have very many conflicts. It's like if you added 20 different PPAs on Ubuntu and then complained about the problems that arose from that.
frozenspinach
in reply to 𝕛𝕨𝕞-𝕕𝕖𝕧 • • •My understanding is that constantly triggering compiling like that shouldn't be happening in any typical arch + pacman situation. But it can happen in AUR. If it does, I think it's a special case where you should be squinting and figuring out what's going on and stopping the behavior; it's by no means philosophically endorsed as the usual case scenario for packages on arch.
There's certainly stuff about Arch that's Different(TM) but nothing about the package manager process is especially different from, say, apt-get or rpm in most cases.
𝕛𝕨𝕞-𝕕𝕖𝕧
in reply to frozenspinach • • •saying it can happen in the AUR feels disingenuous to me when you consider how integrated the AUR is to the arch ecosystem. this is a genuine complaint from a user perspective and is an issue with the design philosophy imo. it is a special case but it’s so frequent as to be annoying, is my point.
not sure why everyone is replying like i’m unaware and totally ignoring the actual grievance i have. im very well aware of pacman and yay’s intended behaviors, i just think they’re shit in some cases. idk if people who say this have never tried to daily drive arch before or something but the AUR is absolutely not optional unless you want to constantly hand roll your own shit. see my edit to the original comment.
frozenspinach
in reply to 𝕛𝕨𝕞-𝕕𝕖𝕧 • • •Feyd did a pretty good job of outlining the AUR disclaimers in a different comment so I won't do that here. It's true that Arch won't stop you from shooting yourself in the foot, but again it's nuts to claim that routine compiling is the usual case for all rolling distros and belies your claim that you're familiar with usual case experience. There's absolutely no routine experience where you're regularly compiling.
I've used debian and apt-get most of my life, I've used arch on a pinetab 2 for about 6 months, regularly playing with pacman and yay and someone who's never met me is saying I'm a fanboy for being familiar with linux package management. 🤷♂️
berno
in reply to Bjarne • • •frozenspinach
in reply to Bjarne • • •huh? Using package managers almost never involves compiling. It's there as a capability, but the point is to distribute pre-compiled packages and skip that step in the vast majority of cases.
I Cast Fist
in reply to shrewdcat • • •Sunsetting Cursed Terminal Emulation
ArcanBluewing
in reply to shrewdcat • • •I have used rpms, AppImages, Flatpaks, and source. I have even used a snap or two when I had no other choice.
If you can't work with them all, can you even say you Linux Bro?
AnIntenseMoist
in reply to Bluewing • • •Diplomjodler
in reply to Bluewing • • •Bluewing
in reply to Diplomjodler • • •berno
in reply to shrewdcat • • •Flatpaks suck
Ubuntu has turned to dogshit
𝕛𝕨𝕞-𝕕𝕖𝕧
in reply to berno • • •i agree ubuntu is corpo drivel now but flatpaks are actually quite useful for some applications.
the sandboxing is nice to not have to setup manually for every little thing, and i say that as someone who avoids flatpaks generally.
sometimes you just wanna get things up and running, not everything needs to be a unix circlejerk.
eta
in reply to berno • • •relic4322
in reply to shrewdcat • • •never tried flatpak, snaps were so bad as to never consider non-native installs or just use docker instances when I need to run something weird. so dunno.
whats the use case for a flatpak exactly? maybe im not the target audience???
squaresinger
in reply to relic4322 • • •folaht
in reply to relic4322 • • •zazous
in reply to shrewdcat • • •make
make install
0x0
in reply to zazous • • •&&?lemmyknow
in reply to shrewdcat • • •Flatfire
in reply to lemmyknow • • •𝘋𝘪𝘳𝘬
in reply to shrewdcat • • •Flatpaks are great for situations where installing software is unnecessary complex or complicated.
I have Steam installed for some games, and since this is a 32 bits application it would install a metric shit-don of 32 bit dependencies I do not use for anything else except Steam, so I use the Flatpak version.
Or Kdenlive for video editing. Kdenlive is the only KDE software I use but when installing it, it feels like due to dependencies I also get pretty much all of the KDE desktop’s applications I do not need nor use nor want on my machine. So Flatpak it is.
And then there is software like OBS, which is known for being borderline unusable when not using the only officially supported way to use it on Linux outside of Ubuntu – which is Flatpak.
dropped_packet
in reply to 𝘋𝘪𝘳𝘬 • • •This is the main benefit. However, i'm finding the software I use requires less dependencies and libraries these days.
I barely even use flatpaks anymore. Almost everything is in official repos. I couldn't tell you the last time I had a dependency conflict.
Limonene
in reply to 𝘋𝘪𝘳𝘬 • • •Obin
in reply to 𝘋𝘪𝘳𝘬 • • •That's my main use for flatpaks too. Add to that any and all closed source software, because you can't trust that without a sandbox around it.
Recently I've moved from using flatpak for electron apps and instead have a single flatpak ungoogled chromium instance I use for PWAs.
thingsiplay
in reply to 𝘋𝘪𝘳𝘬 • • •But why is that? I mean just because it is packaged by someone else does not mean its unusable. So its not the package formats issue, but your distribution packaging it wrong. Right? In installed the Flatpak version, because they developers recommended it to me. I'm not sure why the Archlinux package should be unusable (and I don't want to mess around with it, because I don't know what part is unusable).
𝘋𝘪𝘳𝘬
in reply to thingsiplay • • •Because the OBS developers say so.
And since I’m not on Ubuntu, I use the Flatpak version to get OBS as intended bey the OBS developers.
Exactly. Most distributions fail hard when it comes to packaging OBS correctly. The OBS devs even threatened to sue Fedora over this.
gitlab.com/fedora/sigs/flatpak…
Broken OBS Studio Flatpak presented as official package (#39) · Issues · Fedora / Special Interest Groups (SIGs) / Fedora Flatpak SIG / Fedora Flatpaks · GitLab
GitLabthingsiplay
in reply to 𝘋𝘪𝘳𝘬 • • •The quoted image does not say so, they do not say the native packaging from your distribution is borderline unusable. That judgement was added by YOU. The devs just state the package on Archlinux is not officially supported, without making a judgement (at least in the quoted image).
As for the Fedora issue, that is a completely different thing. That is also Flatpak, so its not the package format itself the issue. Fedora did package the application in Flatpak their own way and presented it as the official product. That is a complete different issue! That has nothing to do with Archlinux packaging their own native format. Archlinux never said or presented it as the official package either and it does not look like the official Flatpak version.
So where does the developers say that anything that is not their official Flatpak package is "borderline unusable"?
𝘋𝘪𝘳𝘬
in reply to thingsiplay • • •It does exactly say so. Flatpak is the only supported and official method of installation when you’re not using Ubuntu.
Exactly. And the Flatpak version from Fedora was unusable.
They don’t. It’s just unsupported.
Crozekiel
in reply to 𝘋𝘪𝘳𝘬 • • •shapis
in reply to shrewdcat • • •frostphunk
Unknown parent • • •NauticalNoodle
in reply to shrewdcat • • •I spent my time fighting AppImages until Canonical started to force Snap on me. I hated Snap so bad it forced me to switch distros. Now I appreciate Flatpak as a result and I don't find AppImages all that bad, either. Also, I haven't found myself in dependency-hell nor have I crashed my distro from unofficial Repos in well over a decade.
-It's a long way of saying It works for me and it's not Snap.
db2
in reply to NauticalNoodle • • •Appimages are ok, bloated but ok. Unless a library inside is old and won't work.
Flatpak is annoying and I don't like it at all, so I don't use it. Easy solution.
Fuck snap though.
MangoCats
in reply to NauticalNoodle • • •T Jedi
in reply to shrewdcat • • •About the image: The joke's on you, I install my flatpaks via the terminal.
I've started using flatpaks more after starting using Bazzite and I liked them more than I expected. As a dev, I still need my work tools to be native, but most of my other needs are well covered by flatpaks.
Tip: Flatseal is a great config manager for flatpaks' permissions.
Outwit1294
in reply to T Jedi • • •T Jedi
in reply to Outwit1294 • • •It is mostly trial and error. I use it mostly to set envvars.
As an example, I add the ~/.themes folder and the GTK_THEME to allow some apps to get the themes I downloaded.
Outwit1294
in reply to T Jedi • • •Oh, so flatpaks cannot automatically get system themes?
If it is trial and error, is it really useful for a normal user?
T Jedi
in reply to Outwit1294 • • •System themes, probably most of them work. But most of them don't bother watching the user themes or icons folder.
I don't think Flatseal is that useful for the majority of users, no. But it is a good tool to have in mind when the need arises.
Outwit1294
in reply to T Jedi • • •Why do you think it is not useful?
I replaced Firefox system package with Flatpak because I think browser is the most used and vulnerable thing in my system. And the size seemed reasonable.
I did not replace Thunderbird because its size is almost 10 times.
DanWolfstone
in reply to Outwit1294 • • •Outwit1294
in reply to DanWolfstone • • •hallettj
in reply to T Jedi • • •Ferk
in reply to hallettj • • •Installing them is not difficult. It's the same as any other flatpak.
The problem is when running them (actually, when running any flatpak, not just CLI tools) you need to type out the whole backwards domain thingy that flatpaks use as identifier, instead of having a proper typical and simple executable name like they would have if they were installed normally.
I end up adding either symlinks or aliases for all my flatpaks because of this reason. After doing that it's ok.. but it's just an extra step that's annoying and that the flatpak devs have no interest on fixing apparently.
Andrzej3K [none/use name]
in reply to shrewdcat • • •The_Walkening [none/use name]
in reply to shrewdcat • • •I like the idea of them because I don't like dealing with dependencies changing and breaking stuff and I don't really care too much about disk space in the context of non-game desktop apps, as I don't tend to install lots of them.
That being said I absolutely hate that permissions are all over the place and flatpak doesn't ship a GUI to manage them by default, nor do you get any indication as to what permissions a program has until you try some functionality (like filesystem or camera access) only to find out it doesn't work out of the box.
hperrin
in reply to shrewdcat • • •ShinkanTrain
in reply to shrewdcat • • •Limonene
in reply to shrewdcat • • •I've never heard anyone say that Flatpaks could result in losing access to the terminal.
My only problem with Flatpaks are the lack of digital signature, neither from the repository nor the uploader. Other major package managers do use digital signatures, and Flatpaks should too.
buttnugget
in reply to Limonene • • •Obin
in reply to Limonene • • •Nah, it's the same as with systemd, docker, immutable distros etc. Some people just don't appreciate the added complexity for features they don't need/use and prefer to opt out. Then the advocates come, take not using their favorite software as a personal insult and make up straw-men to ridicule and argue against. Then the less enlightened of those opting out will get defensive and let themselves get dragged into the argument. 90% that's the way these flame wars get started and not the other way around.
For the record, I use flatpak on all my desktops, it's great, and all of the other mentioned things in some capacity, but I get why someone might want to not use them. Let's not make software choice a tribalism thing please. Love thy neighbor as thyself, unless they use Windows, in which case, kill the bastard. /s
- YouTube
youtu.beDessalines
in reply to shrewdcat • • •Can someone explain why flatpak isn't necessary for distros that have proper OS dependency management like Arch-based distros or Nix?
Seems like flatpak is solving a problem for OS's that don't have proper dependency management.
BlameTheAntifa
in reply to Dessalines • • •Dessalines
in reply to BlameTheAntifa • • •frozenspinach
in reply to Dessalines • • •Also pretty much everywhere you're using flatpaks (or snaps or...), you are doing it on top of a Linux system that's still getting its core system updates via traditional dependency management. And flatpaks, despite trying not to, make assumptions about your kernel, your glibc version, architecture, ability to access parts of your filesystem or your devices, that can break things, and doesn't bother to track it.
And the closer you get you tracking that stuff (like Snap tries to), you hilariously just get back to where you started, with traditional dependency management that already exists and has existed for decades.
BlameTheAntifa
in reply to Dessalines • • •machinya [it/its, fae/faer]
in reply to Dessalines • • •main selling points are isolation and having the latest version directly from developers without having to wait for your distro to package/update it.
both are debatable since they are not as good as promoted (isolation doesn't always work correctly and it's a mess to configure it once you use anything different than the more mainstream distros) or goes against the historical preference (using bundled everything instead of cooperating with your distro packages and trusting every individual over trusting your distro as a whole) but having the latest version on any distro without having to wait is a popular need so they gained traction quite fast. this might make little sense for rolling release distros (arch, nix) but it's helpful if you have a stable base (years old debian) but need the latest feature on an specific application or have to use very specific libraries that are not packaged on the main distro and would require complex upgrades
ipkpjersi
in reply to shrewdcat • • •I'm not a huge fan of Flatpaks, they're a lot harder to distribute offline versus something like AppImage. Seriously, you have to like create an offline repository, then create a bundle, and it's like 6 or 7 steps, it's honestly kind of ridiculous lol but other than that they seem fine, and they're easy enough to update (but so are apt packages)
I know some people may say "oh why do you need that", but Linux has taught me that my computer is my own, and I should be able to use it the way I want to. I shouldn't have to fight with my package manager to get it to do what I want. So I guess you could say, no I'm not really a fan of Flatpaks.
Personally, I didn't mind Snaps, but I'm getting kind of really fed up with especially for-profit companies etc so I don't like Snap that much now either.
Apt packages are nice, but the more of them you have installed, especially if you're using Ubuntu-based distros and have lots of PPAs, the more annoying upgrading your distro version can be because of all the dependencies and cross-dependencies.
AppImage tends to just work for me, as long as it's not compiled with a newer libc-bin version than the distro I'm currently using has, and I really enjoy that it's just one file I can copy and run pretty much anywhere.
Crozekiel
in reply to ipkpjersi • • •Ferk
in reply to Crozekiel • • •Yes, Flatpak is overall a better approach when compared to AppImages, since being dependent on a known runtime ensures the program will run whenever the runtime is available.
What I wish they would add is a way to run the flatpak in a portable way. Because as it stands, AppImages is the only option for that. Flatpak doesn't really allow to have a portable installation in a pendrive, for example. At the moment there's no replacement for AppImage in such use cases, which is a pity.
But there's no fundamental technical design roadblock in flatpak that would prevent it from supporting this in the future, imho. theoretically one could create a program that mounts the flatpak file into a ramfs layered with the runtime and run it.
ipkpjersi
in reply to Crozekiel • • •Crozekiel
in reply to ipkpjersi • • •I don't actually know if it is a Wayland issue - most of those forum posts are like 3 years old... And I have definitely used these same AppImages in the past on Wayland without issue. I think the AppImages are expecting some specific dependency to be installed on my system that is no longer installed due to updates. (which I thought was counter to the entire point of an AppImage? I thought it was supposed to be kinda like Flatpak where it has it's dependencies in the image? Maybe I just misunderstood AppImage...)
To give you some hope, my Distro switched to Wayland as default a little over a year ago (i think) and I have not been running into problems (outside this AppImage problem, if it is indeed a Wayland issue, which I cannot confirm or deny).
kadaverin0
in reply to shrewdcat • • •frozenspinach
in reply to kadaverin0 • • •sunzu2
in reply to frozenspinach • • •All of this is true and precisely zero normies care about any of it.
The fact that I can put my ~~idiots~~ family on any modern distro and tell them to use the app store alone makes flatpaks king of the app management
AndrewZabar
in reply to shrewdcat • • •MangoCats
in reply to AndrewZabar • • •AndrewZabar
in reply to MangoCats • • •MangoCats
in reply to AndrewZabar • • •I view the delays during launch and the extra time spent during updates as a "load on the system."
Also, it entirely depends on your deployment environment. I develop system images that go out on thousands of devices deployed in "Cybersecuity Sensitive" environments, meaning: we have to document what's on the system and justify when anything in the SBOM (list of every software package installed on the machine) is identified as having any applicable CVEs... soooo.... keeping old versions of software anywhere on the machine is a problem (significant additional documentation load) for those security audits. Don't argue with logic, these are our customers and they have established their own procedures, so if we want their money, we will provide them with the documentation they demand, and that documentation is simplest when EVERYTHING on the system has ALL the latest patches.
The most secure systems are those that don't do anything at all. You can't hack a brick.
AndrewZabar
in reply to MangoCats • • •MangoCats
in reply to AndrewZabar • • •machinya [it/its, fae/faer]
in reply to shrewdcat • • •i mostly use them for proprietary stuff or for software that is incredible painful to package (mostly electron apps). i will probably never use them for anything that actually matters but i also use rolling release distros everywhere so latest release is never too far. for testing latest version of any software i prefer appimages since they are simpler and don't need a messy setup as flatpak, but i also won't use them pass the testing phase and i prefer packaging the software if possible.
snaps, on the other hand, will never go near any of my systems. not even by accident
MaysaMayako
in reply to shrewdcat • • •Personally I am okay with them actually. I use several on my system and having each app allowed to have different permissions is super useful.
But also I like things that are directly installed cause they seem just a tad faster performance wise.
MangoCats
in reply to MaysaMayako • • •MaysaMayako
in reply to MangoCats • • •MystValkyrie
in reply to shrewdcat • • •There was a few years where I pretty much only used Flatpaks because I was scared of the terminal. But now that I've learned how to use the terminal, it's so much more convenient because I can quickly update all my applications all in one place without having to open a separate app. Plus, some Flatpaks can fall really behind on software updates.
There might be a Linux userbase someday where no one other than developers actually knows how to use the terminal, because users can run everything they want without a command line, but maybe that's actually a good thing because it'll drive up how many people use a Linux distro.
With Windows and Mac, there's a shareholder incentive to enshittify. With Linux, if a distro goes bad and gets commercialized, there's always another distro people can move to, not to mention there's no financial incentive. The more people get on Linux, the less power these tech companies have. Personally, that and privacy are what drew me to Linux much more so than being able to tinker or fine-tune my experience.
otacon239
in reply to MystValkyrie • • •Ideally, all the essential terminal commands could be replicated in a user-friendly GUI-applicable manner. Don’t ever have to remove the terminal for those that enjoy it, but if we could have a magic world where even the failure states could be navigated with little to no prior knowledge required and it gets everyone away from Windows and Mac for good, I’m all for it.
captainlezbian
in reply to MystValkyrie • • •NostraDavid
in reply to shrewdcat • • •17lifers
in reply to NostraDavid • • •Lovable Sidekick
in reply to shrewdcat • • •ztwhixsemhwldvka
in reply to shrewdcat • • •geneva_convenience
in reply to ztwhixsemhwldvka • • •sudo_halt
in reply to ztwhixsemhwldvka • • •✋😕🤚
Absolute Dogshit
PillowD
in reply to shrewdcat • • •MangoCats
in reply to PillowD • • •wewbull
in reply to PillowD • • •BeardedGingerWonder
Unknown parent • • •spookedintownsville
in reply to shrewdcat • • •setVeryLoud(true);
in reply to spookedintownsville • • •Flatpaks aim to be a middle ground between dependency hell and "let's pull in the universe" bloat.
Applications packaged as Flatpaks can reference runtimes to share "bases" with other applications, and then provide their own libraries if they need anything bespoke on top of that.
MangoCats
in reply to setVeryLoud(true); • • •And they are still, in my experience, slow to load, a cumbersome addition to the update process, and often un-necessary.
Don't get me wrong, if you're in a tight spot and can't make two significant software packages work in a distribution due to conflicting library version requirements... some kind of lightweight container solution is attractive, expedient, and better than just not supporting one of the packages. But, my impression is that a lot of stuff has been moved into flatpak / snap / etc. just because they can. I don't think it's the best, or even preferred, way to maintain software - for the desktop environment.
(Returns to checking on his Docker containers full of server apps on the R-Pi farm...)
setVeryLoud(true);
in reply to MangoCats • • •I'm running an immutable distro at the moment (GNOME OS), and I felt no loss of performance due to Flatpaks. Snaps, on the other hand, do have a perceivably longer launch time.
Given that it's an immutable distro, everything I need needs to be either a Flatpak, a Snap, an Appimage or an extracted tarball, otherwise it runs in a container. The advantage of this system is stability and making the host incorruptible, as well as the ability to very easily roll back updates or failed systemd-sysext layers.
Not everything can run in a Flatpak at the moment, but we're hoping the evolution in Flatpak, XDG portals as well as encouraging developers to use the available XDG portals can make this a possibility someday. Namely, IDEs don't run that well in a Flatpak, but GNOME Builder has proven that it's 100% possible with the currently available XDG portals as well as connecting your IDE or editor to a container.
MangoCats
in reply to setVeryLoud(true); • • •Not mocking: can you share any good guides to practical immutable systems?
What I observed of Ubuntu Core made a strong "not ready for prime time, and even if it was I don't want it" impression on me.
setVeryLoud(true);
in reply to MangoCats • • •Ubuntu Core, based on Snaps, is very much not ready for prime time IMO. It's kind of a mess outside of server use.
Look instead at Fedora Silverblue, Vanilla OS, and for the bleeding edge of immutable systems, GNOME OS.
KDE is about to launch their analogue to GNOME OS relatively shortly, named "Project Banana". These two are not exactly distros as they do not distribute the kernel, they are simply platforms that layer a bunch of images together to create a stable, reproducible system. There's also OpenSuSE Aeon, but I don't like its style of immutability as it's immutable by rootfs lock-out rather than immutable by image.
As for advice, learn how to use Distrobox / Toolbx containers. If you're a developer, this is where you will be working.
Immutable Linux is still young, and a lot of software isn't written with it in mind, so expect some growing pains.
beastlykings
in reply to setVeryLoud(true); • • •I'm on silverblue, well, bluefin, specifically.
So far so happy 🤷♂️
MangoCats
in reply to setVeryLoud(true); • • •Thanks. In the past I have worked in Slackware, and even had Gentoo on my home system for a couple of years, but otherwise I've been fully saturated in Debian and its children - so that's my "comfort zone." I used to like KDE, but drifted away from it when I got a 4K screen notebook and KDE hadn't figured out resolution scaling yet, while Ubuntu/Unity had. I never quite warmed up to GNOME, but definitely have done my time with it. XFCE has matured enough for me to daily drive it without too much pain now, and I love the ways it can be de-featured (don't want a launcher bar? Don't run it, nothing else breaks.)
Server-side, I have been filling my Raspberry Pis with Docker containers for a while now... it's not completely alien, but I do kind of tend to "set it and forget it" when it comes to container deployments.
Toribor
in reply to spookedintownsville • • •HugeNerd
in reply to spookedintownsville • • •Unlike that apostrophe.
Crabhands
in reply to shrewdcat • • •setVeryLoud(true);
in reply to BeardedGingerWonder • • •JayArr
in reply to shrewdcat • • •HugeNerd
in reply to shrewdcat • • •SpiceDealer
in reply to shrewdcat • • •beleza pura
in reply to shrewdcat • • •seralth
in reply to beleza pura • • •Fatur_New
in reply to shrewdcat • • •commander
in reply to shrewdcat • • •I'm happy to use Flatpaks but the annoyances I've had are like when one application says to use you'll need to point to the binary of another application that it depends on but very understandably doesn't package together, figuring that out to me can be annoying so I'll switch to a regular installation and it all just works together no fuss, no flatseal, no thinking about it really. Also some applications where it's really nice to launch from the terminal especially with arguments or just like the current working directory and with Flatpaks instead of just right off the bat it's application name and hit enter, Flatpak hope you remember the whole package name
org.wilson.spalding.runner.knife.ApplicationName ...
Ya alias but got to remember to do that. So far anything I'd ever want to run from terminal, no Flatpak
Paddy66
in reply to shrewdcat • • •As long as software is available in the Software Manager to be installed that way... I don't care what format it's in.
But don't make normies go to the terminal. It's inhumane, and really does not help the masses get away from big tech - which is a worthier goal than keeping your software terminal-only.
arc99
in reply to shrewdcat • • •While I wouldn't want flakpak going deep into the OS I think the advantage of using them on the desktop is obvious. Developers can release to multiple dists from a single build and end users get updates and versions immediately rather than waiting for the dist to update its packages. Plus the ability to lock the software down with sandboxes.
The tradeoff is disk consumption but it's not really that big of a deal. Flatpaks are layered so apps can share dependencies. e.g. if the app is GNOME it can share the GNOME runtime with other apps and doesn't need to ship with its own.
RheumatoidArthritis
in reply to arc99 • • •MoondropLight
in reply to shrewdcat • • •Perhaps ironically, this is mocking a strawman. Flatpacks can be installed and managed using the terminal! Not only that but Linux-Distros have had graphical package managers for decades.
The primary reason that distros have embraced flatpack / snap / appimage is that they promise to lower the burden of managing software repositories. The primary reason that some users are mad is that these often don't provide a good experience:
Theoretically they are also more secure... But reality of that has also been questioned. Fine grained permissions are nice, but bundling libraries makes it hard to know what outdated libraries are running on the systems.
grue
in reply to MoondropLight • • •org.mozilla.firefoxinstead of justfirefox), which is a very terminal-specific issue, LOL!nullpotential
in reply to shrewdcat • • •a Kendrick fan
in reply to shrewdcat • • •seralth
in reply to a Kendrick fan • • •rumba
in reply to shrewdcat • • •I need OBS on this new computer!
Let's install the flatpack!
V4l problems
Plugins Problems
Wayland Problems
I'm just going back to the .deb, thanks.
Carlos Solís
in reply to rumba • • •Captain Beyond
in reply to shrewdcat • • •Not a fan for a few reasons. Flathub (as far as I know) works on the app store model where developers offer their own builds to users, which is probably appealing to people coming from the Windows world who view distros as unnecessary middlemen, but in the GNU/Linux world the distro serves an important role as a sort of union of users; they make sure the software works in the distro environment, resolve breakages, and remove any anti-features placed in there by the upstream developers.
The sandboxing is annoying too, but understandable.
Despite this I will resort to a flatpak if I'm too lazy to figure out how to package something myself.
Developers: Let distros do their job
drewdevault.comscholar
in reply to Captain Beyond • • •Mahi
in reply to shrewdcat • • •muusemuuse
in reply to shrewdcat • • •Enter the calm and quiet room
Pass out torches and pitchforks, guns and knives
“Snaps exist”
War erupts.
sudo
in reply to muusemuuse • • •SNAP BAD
grue
in reply to muusemuuse • • •War with who? I'm posting this from Kubuntu and I'd happily agree with you that Snap should fuck off and die. (In particular, the backend being controlled by Canonical makes it objectively bad compared to Flatpak.) Even among people like me who tolerate Snap (for now...), I really don't think you're gonna find anybody who actually likes it, let alone enough to champion it.
Can't start a war when there's a consensus!
Decker108
in reply to grue • • •limelight79
in reply to shrewdcat • • •I "grew up" with Slackware, so I definitely understand the dependency issue.
I like flatpaks (and similar) for certain "atomic" pieces of software, like makemkv. For more "basic" software, like, say, KDE, I want it installed natively.
Bilb!
in reply to shrewdcat • • •Bronstein_Tardigrade
in reply to shrewdcat • • •kaidezee
in reply to shrewdcat • • •like this
Carlos Solís likes this.