[a / b / c / d / e / f / g / gif / h / hr / k / m / o / p / s / t / u / v / vg / vm / vmg / vr / vrpg / vst / w / wg] [i / ic] [r9k / s4s / vip] [cm / hm / lgbt / y] [3 / aco / adv / an / bant / biz / cgl / ck / co / diy / fa / fit / gd / hc / his / int / jp / lit / mlp / mu / n / news / out / po / pol / pw / qst / sci / soc / sp / tg / toy / trv / tv / vp / vt / wsg / wsr / x / xs] [Settings] [Search] [Mobile] [Home]
Board
Settings Mobile Home
/g/ - Technology


Thread archived.
You cannot reply anymore.


[Advertise on 4chan]


File: file.png (106 KB, 603x770)
106 KB PNG
And I just moved from Firefox to Brave too
Time to go back?
>>
>>109878795
Why does everything Jeets touch become a locked down surveillance quagmire.
>>
>>109878809
Gotta appease their masters, is all.
>>
>>109878809
Jeet means victory
>>
>>109878795
>And I just moved from Firefox to Brave too
you deserved it
>>
Google regrets making this shit open source, same with shitdroid.
as google needs to pump those numbers up for financials, you'll see more insane shit.
>>
>>109878795
>he (in pic) thought daddy Jewgle would permit development of degoogled Chromium forks to continue in Year 2026
>Jewgle pull the ladder up in the same way they did with AOSP
>>
>>109878809
Because transparency would expose their ineptitude.
>>
>>109878795
Does Google know anyone can fork chromium and they can't do anything about it?
>>
>>109881333
>fork a branch thats 5 major versions behind
How do you expect normalfags to maintain chromium
>>
>>109881333
>they can't do anything about it?
Wrong, they can just update the hundreds of different living web standards faster than freetards can keep up with until the fork dies, basically what they already do
>>
>>109881381
Freetards can create a mirror and keep updating. Google can't do shit about that.
>>
>>109881373
They don't need to. Create your fork, keep merging. Done.
>>
>>109881373
>>109881381
Heck I'll find one mirror for you two idiots: https://github.com/chromium/chromium

Wow that was hard! It took one search in GitHub.
>>
wtf I was just about to switch to brave too because firefox is slow as fuck
>>
>>109878795

Time to switch to Lynx
>>
>>109881431
>To check out the source code locally, don't use git clone! Instead, follow the instructions on how to get the code
So what happens when their custom sync process requires google account auth too?
>>
>>109881373
With AI.
>>
>>109878795
>Brave
>>
>>109878795
Ladybird can't come soon enough
>>
The ladder is being pulled up. "Open source" was a phase to get everyone on their standards, now there's no escape.
>>
It's AI scrapers fault, even the Linux kernel website is being locking down web access.
>>
>>109881875
their sync process is fucking retarded anyway it pulls 66Gb for a fucking browser
>>
git cloning? Fair enough

But there isnt a real manual on how to use git, last time I checked
>>
I did a custom build of Chromium. It's way better.
>>
>>109881875
You have a volunteer that merges from origin. What do you think it would be? They probably already have that setup in that mirror with SSH.
>>
>>109882077
I'm not sure if you're joking or not but here you go: https://git-scm.com/book/en/v2
>>
File: 39641373.jpg (116 KB, 950x1097)
116 KB JPG
>>109878795
>Safari will win your lifetime
I HATE THE GOOGLE-CHRIST!!!
>>
>>109881431
>>109881875
Too lazy to try right now. What happens if you try to git clone it? Does it not work?
>>
>>109878795
I got to be honest, after reading this thread I'm pretty sure many of you have zero idea how git works, why this login doesn't really matter, that Google can't lock down source code with a login. Panicking because of this, thinking brave will be impacted whatsoever, or believing mirrors are screwed tells a lot. Pro tip, this login doesn't mean crap, it's not a show stopper.
>>
>>109882742
Of course it works, it's GitHub. You don't need to sacrifice a chicken. You don't even need a GitHub login.
>>
>>109882775
Yeah that's what I was thinking. What's even special about the "official" way?
>>
>>109878952
>Google regrets making this shit open source
No they don't. All part of the plan.
https://en.wikipedia.org/wiki/Embrace,_extend,_and_extinguish
>same with shitdroid.
They didn't make the kernel, so there's a hard limit to their rugpulls in that regard. They tried making their own permissively licenced kernel, but that turned out to be too hard. But yes, they have been getting tight on the userspace components, as shown by them not publishing Pixel sources, leaving AOSP out to dry.



[Advertise on 4chan]

Delete Post: [File Only] Style:
[Disable Mobile View / Use Desktop Site]

[Enable Mobile View / Use Mobile Site]

All trademarks and copyrights on this page are owned by their respective parties. Images uploaded are the responsibility of the Poster. Comments are owned by the Poster.