Hmmm, that isn’t open source, I don’t know if one can trust it. Why does a browser need in-app purchases? Try Mull or Cromite.

Edit: from the description, it uses Brave Search (to answer you question), so it doesn’t send to Google your queries. But I’d be careful with an app with a bunch of SEO keywords in its description.

I agree that generative AI is polluting the wider mainstream internet, turn every corner and you will see AI being mentioned or used ad nauseum. I also agree that captologist algorithms are addictive. But to disagree, I think you should still have faith in the wider population. The dopamine addicts are a fraction of the total population. I believe it is possible to outsmart AI driven captology. To give this up means giving into fatalism that AI technology is somehow “stronger than us” and will “enslave us”. I think this is x-risk speak and it’s being utilized by big AI to fear-monger and control public sentiment (which seems to be effective given the numerous articles from mainstream tech outlet).

That being said, I also don’t have a perfect way out for those who have fully embraced mainstream tech and services. Seems like they don’t care about their privacy because they have “nothing to hide”, are easily sold “privacy-friendly” solutions that are still shady (ahem Brave) and part of the problem, maybe they will care when their own bubble bursts. It’s hard to tell an addict to quit cold turkey.

I’ll share what I’m doing: stick to FOSS, use the Fediverse, run Linux and GrapheneOS, I also self-host a lot of services I rely on, don’t use any social media besides pseudo-anonymous forums, and only using second hand devices and parts. I’m exposed to the internet daily and have managed to avoid the generative AI plague and captology algorithms. I don’t view my relationship with technology as parasitic or unhealthy.

Also, you might be interested in this: https://permacomputing.net/

Ah that would make sense as to why the SCSS files don’t do anything.

If you see my response to the other comment on this post, I basically had the same issue, my theme looked like the screenshot you attached when generating with bootstrap.build. I ended up not using it at all.

I didn’t want to get into bootstrap, so yes I edited it by hand. My theme isn’t perfect yet, it took me 2 hours or so by editing the vaporwave theme.

Maybe it’s cached… have you tried in incognito or force reload? If not, maybe try manually deleting the nginx cache if you set up Lemmy with nginx.

Yeah I figured it out (check out my instance), a few hiccups here and there but I basically did the same thing I posted up there and it now loads correctly.

The problem wasn’t from my end, lemmy-ui didn’t move fully to bootstrap 5 when I made that post.

After an update to pre version 0.18.x, I could use bootstrap.build and follow the rest and the theme loads.

Post 0.18.x, when the devs reintroduced some bundled themes like the vaporwave ones and others, my theme broke again, bootstrap.build doesn’t seem to work anymore. They now also require three files _variables.theme.css, theme.scss and theme.css

Now I’m not a web frontend dev or anything like that so I ended up just copy and renamed the vaporwave theme and edited it to what I want.

That link contains the hash needed for your OTP generator. It definitely isn’t clear but you had to copy the link and paste it to your OTP app instead of clicking on it.