/tech/ - Technology

>>18621
This and the fact Ubuntu now has stronger minimum requirements than Windows 11... Canonical has lost it.

The only one worth a damn is Lubuntu for being Snapless and lightweight.

>>18628
>Ubuntu now has stronger minimum requirements than Windows 11

Awww... That's sad.
N00b-lUser here, I am little better than a script kiddie, but there was a time that I kept my old Dell Attitude alive for another 4 months by installing Ubantu.
looking to find a good all-purpose image like possibly Cinnamon or a Mint fork.
I don't do big gayming anymore, so most of my needs are not high draw but for video and image editing anyway.
Since I already use GIMP, and other Open source softs on a highly modified WIN7PRO OS, I figured now that Everything Minilimp® is thoroughly jeeted, I should ought to have a backup plan.

I'm also trying to turn a few gen1 Kindle fires into exclusively e-readers for my PDF libraries, with no connections to the web whatsoever.
INB5
>GitGUd

ubuntu-10.04-desktop_screenshot_2_1_4c513809c0daf18b31e8ef307a033760.png
[Hide] (203.9KB, 800x600)

>>18636
It's sad indeed... I guess the alternative now is to use Linux Mint, the Debian based varient and not the traditional Ubuntu based one, or just use Debian itself.

Ubuntu used to be so good...

>>18640
>pic
Ah, Ubuntu 10... My very first Linux distro and the reason I went back to Windows for another 10 years. Ubuntu was terrible then and it's still terrible now, albeit for different reasons.

1751161035046.png
[Hide] (357.6KB, 1366x768)

>>18645
Fair enough, Ubuntu peaked with Unity.

>>18666
Although it's not the same thing, the part about protocols does somewhat remind me of Microsoft and the Halloween documents.

https://en.wikipedia.org/wiki/Halloween_documents
>Document I suggests that one reason that open source projects had been able to enter the server market is the market's use of standardized protocols. The document then suggests that this can be stopped by "extending these protocols and developing new protocols" and "de-commoditiz[ing] protocols & applications".

black-box-engineering.png
[Hide] (9.3KB, 608x479)

>>18667
Watching, especially, the horror of web browsers devolving over the years, I've come more and more to feel multiple independent proprietary software packages implementing well documented public APIs is a better approach than freely available source code nobody understands and everybody just keeps piling spaghetti on top of.

>>18663
The FBI does that.

>>18670
https://en.wikipedia.org/wiki/Accident_(fallacy)

>>18663
>CSAM
Anyone who uses politically correct corporate nuspeak deserves the death penalty.

1w9ghe748b6f1.jpeg
[Hide] (598.2KB, 1080x2340)

>>16876
I think it look neat, on iOS and Android, it's a nice look.

1749491887484149.jpg
[Hide] (618.5KB, 3840x2160)

>>16406 (OP) 
It can look fantastic when customized right.

>>16938
>it can make a great movie prop
ftfy

>>16406 (OP) 
How do you guys feel about Liquid Glass after the updates?

creed_of_assassins.webp
[Hide] (32.6KB, 505x639)

>>16406 (OP) 
Not really liquid glass-specific, but:
>haven't touched nu-crApple stuff for a while
>recently had to use one and it had multiple monitors
>not only is the menubar square
>not only is it translucent
>not only is it collapsible
>there are separate simultaneous menubars on each display, and they are different if there are different foreground apps
What's the point of having a menubar at all separate from windows if you're gonna pull this? These subhumans have no overall idea of what they're doing.

>>17694
It's not just about protecting data, or even bloat, it's just sheer restrictiveness of the Google handrails. Like, I wanted to adjust headphone volume in increments finer than 1/10, I look online "Oh, you gotta root it to do that".

>>17696
I never knew how to root a phone. Once I tried to root a xiaomi phone I had and they make you create an account and wait like a week or two just so you can root it. It's so annoying.

>>17697
>having to file an application to take control of your device
10/10 botnet goyims

>>17698
The good part about Android is anything will let you root it with enough fussing and it's always designed to allow that. The bad part about Android is the ease with which rooting can be done varies ENORMOUSLY, so if you're the one picking it's a very good idea to shop ahead and pick the most cooperative device.

Same for other stuff like long term OS updates, and 3rd-party distro/driver support.

20260103_114013.jpg
[Hide] (5.5MB, 3060x4080)

>>16332 (OP) 
I had a nightmare today where my tablet broke... posting on zzzChan from it now and I'm full of relief, I love this thing.

Any of you fags are using the pine phone? How is it?

>5 years ago
<still no linux phones

>>15936
is there any real actual advantages outside of being pinged? I would think that using something outside of android and IOS would put a red bullseye on your back.

>>10175
This picture feels so pointless yeah it's blatant the art is shit.  But what do you expect when you hire a hentai artist worse things come to worse being that if they drew her normally mentally ill women and homosexuals will cry they're sexualizing children despite it's just a drawing.
So no matter what you cannot win how you draw her unless you dress her like a Muslim woman with a hijab.

>>15936
They exist and you can even buy them, they are just not ready for daily use, which is a travesty. But then commercial UNIX pretty much died out because every vendor had its own line of expensive RISC work stations running their own flavour of UNIX, meanwhile anyone could take a random x86 computer and start tinkering with Linux. The problem is that there is no smartphone equivalent of x86 computers, instead you have to either fight tooth-and-nail to somehow put your own OS on a locked down phone, or try make your own. The former is not that much fun when you can permanently brick your phone if something goes wrong, and the latter seems to be too expensive for an end product that is objectively inferior to a low end Android phone.

fumo-smoking-fumafarhan.gif
[Hide] (178.8KB, 640x640)

>>15897
I see some people shilling Ubuntu Touch on YouTube, is it still supported? How's the support of modern apps and updates?

>>17054
>shitcrypted protocols
>they're too slow
are you imblyign it's slow because of encryption? that's long been accelerated to multiple Gbit even if it's triple AES encrypted. if i2p is slow it's because all you niggers with Gbit fiber at home don't run a node so there are only a few thousand fast nodes worldwide and you don't seed torrents
>niche to use
>why everyone sticks with Google Chrome
no it's because they're cattle that use whatever jews feed them by default

>>17066
>implying implications
Stopped reading there, KYS memetarded normalnigger.

85d22392c0afca2048af169614bc0c5df08f7528940c1fa7ab5d574d77f12bcc.jpg
[Hide] (82.5KB, 600x600)

Since the IPs of all I2P routers are publicly available, doesn't this mean that it could be easy to find a particular eepsite's real IP address by correlating its downtime with a particular IP's downtime?

c622a1bdaefb4b12c4a803714a24ad566f40167abd2baa9436410c833eed5857.jpg
[Hide] (83.8KB, 660x660)

>>18402
>Since the IPs of all I2P routers are publicly available, doesn't this mean that it could be easy to find a particular eepsite's real IP address by correlating its downtime with a particular IP's downtime?
Yes that's called Live Behavior Alignment or on/off attack. It's not as simple as it sounds because you need to go offline several times for any kind of pattern to make it through the noise of all other nodes joining and leaving. The main mitigation is called multihoming where you serve the same hidden service from multiple difference servers so it's not obvious to an attacker when one of the servers goes offline.
https://arxiv.org/html/2512.15510

You can read more about known i2p attacks and mitigations in the official docs
https://i2p.net/en/docs/overview/threat-model/

f24f24efb92a6526d39b341b98fe233f98af38666d8655f4f6f771813ed085c8.jpg
[Hide] (94.8KB, 500x333)

>>18518
>The main mitigation is called multihoming where you serve the same hidden service from multiple difference servers so it's not obvious to an attacker when one of the servers goes offline.
I was mainly concerned with the idea of that type of correlation because it's bad for a self-hosted setup since it reveals your personal IP. If I could get some VPS or other external server for "multihoming", at that point I could as well only host it on that server and not care about correlation attacks since getting its IP found out wouldn't be as bad for my personal privacy.
Anyway, only with a single server, could you confuse an attacker and mostly mitigate these attacks by waiting a little before putting up a service when your I2P router goes online after being offline, and also by randomly shutting down your service for short periods of time from time to time while keeping your I2P router online?

4a56d59bb4c3a4b5787aa93f90a1d44026a026974a263893bd5535fe05b7ec44.png
[Hide] (99.2KB, 881x542)

>>17943
>I'm probably going to grab that Touhou collection before it goes
Hope you got what you were after. Moriya Shrine related. Unsure if this was an April fools joke or not.

van.jpg
[Hide] (36.6KB, 600x451)

>>18458
I feel like (they) will go for Torrents next, anon... that's why we need to backup, and backup the backups.

Here's some sort of Myrient revival: https://minerva-archive.org/
Torrents: https://cdn.minerva-archive.org/

>>18462
>Unsure if this was an April fools joke or not.
It is.

>>18472
There should be some sort of rule about how long an April fools' joke can go on for. 24 Hour limit.

1746759676636665.jpg
[Hide] (51.3KB, 600x850)

>>17365
Based.

>>17368
Fair. As much as I like tablets, I'll admit the only demographics that use it a lot are children, elderly, homossexual men and college women.

>>17257
Well I find the idea delightful! My main driver is an iPhone Mini, and the consumption unit a full size iPhone (will probably get an iPad to replace it next). I've always found the idea of digital minimalism a worthy goal. Picrel is my last mini phone (Palm PVG100) before the market decided smartwatches were what gymrats wanted for a small comms unit.

IMG_0935.jpeg
[Hide] (1.5MB, 2912x2557)

^---

>>17466
>>17468
It's cool to see likeminded people, it seems this idea of mine is mostly unpopular on /tech/ overall, but I still like it, might try Syncthing as I've heard good things about it. Nice to see smaller smartphones, I personally prefer them bigger because my hands are big and fat, so it's more comfortable for me, but I still find smaller ones charming and wish they'd be common.

>>8229
So the less code you need to look through the less that needs to be maintained?

>>15982
I see, fair enough.

>>15984
Thanks for the reply! Don't be hard on yourself, I think you're doing a great job, this place is pretty great.

6.png
[Hide] (693.9KB, 784x806)

>>15983
Reddit is much worse, everything about it. And I don't think it was ever gud, unlike slashdot. Slashdot was decent in the late 90's, before they defaulted anonymous posts to -1 and changed the interface to a very painful browsing experience in Lynx.
Reddit mossad lady on the left.

installgentoo wiki link has changed:
https://igwiki.lyci.de/wiki/Main_Page

deploredit.jpg
[Hide] (78.8KB, 1136x640)

>>15987
Reddit was never good, but before all the purges under Pao/SRS it at least wasn't BAD. Much like SA or opinionstube, it was at least mediocre back when it was sincere(le retarded) Randroid fedoralords instead of Blue Qboomer Langley spambots.
>Slashdot
Main structural advantage of /. versus its later knockoffs like Reddit was the Anonymous Coward feature. It's worth remembering that, in its early years, most 4chan posts were NOT anonymous! The cultural norm of anonymity by default evolved later, from something originally more like USENET where anon posts were commonly known but most weren't even pseudonymous.

>>17966
The old URL redirects to the new site. Shame the new URL is less memorable, but it's still likely a good idea to update the link.

>>18167
>Last time I used it guix pull was unbearably slow, however.
That's specifically Savannah being slow as hell as it is(/was?) getting hammered by bots.
I believe they have switched to Codeberg as default since then. If not, just add this to ~/.config/guix/channels.scm:
(list
  (channel
    (inherit (car %default-channels))
    (url "https://codeberg.org/guix/guix")))

sonatype_survey_infographic.jpg
[Hide] (1.4MB, 1350x4800)

>>18167
>muh buttstrap
Asinine cargo cultism

If you actually cared about muh security you'd have somebody conduct a legit audit of every LTS release, but of course nobody does that except a handful of safety critical embedded platforms.

If you just want something unambiguous enough to trust gut feelings on, but easier to read than assembly, C is still a terrible choice because it's full of undefined crap and its bloated compiler's wizardry. Maybe something like Forth would be better.

>>18177
Guix uses a cryptographic (SHA256) hash of the source code and goes the extra mile to ensure 100% reproducibility.
It is not practical to verify a full-blown (and actually usable for common tasks) desktop OS without fully reproducible builds, so the work Guix and NixOS do is very important in this regard.

>>18181
>(SHA256) hash of the source
Cargo cultism. Hashed binary packages are exactly as trustworthy as uncompiled source nobody read.
>the work Guix and NixOS do is very important in this regard
The parts about ensuring bit-for-bit identical environments to those used by auditors can be deployed "the right way", instead of blindly dumping Docker images and Flatpak fake "sandboxes", yes. The arbitrary fetishism of C source as some sacred cow of transparency, not so much.

Security and bugginess aside, though, the ability to build everything the same way and roll everything backward and forward alongside multiple branches in the same install is extremely convenient for a ton of other reasons. Or at least it would be if the UI wasn't so autistically unpolished and the documentation wasn't so scattershot, for a project old enough to have kids in school.

>>18197
Assuming we are fine with starting "from scratch", how about something like this?

1. Specify a type of immutable object that isn't just bytes but also references other objects.
Specifically, make addresses not "just an integer/bytes" so it is possible to trace all objects to leaves from a single root node with just a single program/algorithm.
Instead of a single type of objects with both bytes and references, having two types of objects is fine too (one plain bytes, one only with references).
As the objects are immutable it is guaranteed they form a directed acyclic graph.
These references should be opaque to avoid exposing implementation details.

2. Use a cryptographic hash to refer to these objects.
This is possible due to the objects being immutable and not having any cyclic references.
The hash must differentiate (use a different domain) between plain bytes and references to avoid confusion attacks (e.g. tricking an implementation to interpret bytes as a reference).

3. Use "drivers" to transform objects.
These drivers take a single object as input and output a single object.