foo

Well, why not both? I'd say you're going to have trouble finding a full time, remote software position as an 18 year old without a degree, work experience, or internships. That's not to say it's impossible, and I certainly don't believe a CS degree is an absolute requirement as an entry credential for this industry, but it does help quite a bit. Without one you'd need to demonstrate your abilities which it certainly sounds like you're making strides towards with side projects so definitely keep that up. But it also means you'd have to network and go to career fairs to actually talk to recruiters to make your case. You'd likely find it easier to go after internships at first rather than full time positions, especially remote ones. With a few successful internships under your belt and some references from them you could more easily transition into a full time position somewhere, especially if you've continued to build up a portfolio of side projects to exhibit. In the meantime, working on cars could be a good income while moonlighting getting your software career started.

https://lemmy.ml/post/2946747. This is a question for !lemmy_support@lemmy.ml too.

These links? They work for me.

• https://github.com/RupertBenWiser/Web-Environment-Integrity/
• https://github.com/chromium/chromium/commit/6f47a22906b28994

91%, Firefox with ublock and Privacy Badger on a network with pfBlockerNg.

Write to your country's anti-trust body if you feel Google is unilaterally going after the open web with WEI (content below taken from HN thread https://news.ycombinator.com/item?id=36880390).

US:

• https://www.ftc.gov/enforcement/report-antitrust-violation
• antitrust@ftc.gov

EU:

• https://competition-policy.ec.europa.eu/antitrust/contact_en
• comp-greffe-antitrust@ec.europa.eu

UK:

• https://www.gov.uk/guidance/tell-the-cma-about-a-competition...
• general.enquiries@cma.gov.uk

India:

• https://www.cci.gov.in/antitrust/
• https://www.cci.gov.in/filing/atd

Example email:

Google has proposed a new Web Environment Integrity standard, outlined here: https://github.com/RupertBenWiser/Web-Environment-Integrity/....

This standard would allow Google applications to block users who are not using Google products like Chrome or Android, and encourages other web developers to do the same, with the goal of eliminating ad blockers and competing web browsers.

Google has already begun implementing this in their browser here: https://github.com/chromium/chromium/commit/6f47a22906b28994....

Basic facts:

1. Google is a developer of popular websites such as google.com and youtube.com (currently the two most popular websites in the world according to SimilarWeb)
2. Google is the developer of the most popular browser in the world, Chrome, with around 65% of market share. Most other popular browsers are based on Chromium, also developed primarily by Google.
3. Google is the developer of the most popular mobile operating system in the world, Android, with around 70% of market share.

Currently, Google's websites can be viewed on any web-standards-compliant browser on a device made by any manufacturer. This WEI proposal would allow Google websites to reject users that are not running a Google-approved browser on a Google-approved device. For example, Google could require that Youtube or Google Search can only be viewed using an official Android app or the Chrome browser, thereby noncompetitively locking consumers into using Google products while providing no benefit to those consumers.

Google is also primarily an ad company, with the majority of its revenue coming from ads. Google's business model is challenged by browsers that do not show ads the way Google intends. This proposal would encourage any web developer using Google's ad services to reject users that are not running a verified Google-approved version of Chrome, to ensure ads are viewed the way the advertiser wishes. This is not a hypothetical hidden agenda, it is explicitly stated in the proposal:

"Users like visiting websites that are expensive to create and maintain, but they often want or need to do it without paying directly. These websites fund themselves with ads, but the advertisers can only afford to pay for humans to see the ads, rather than robots. This creates a need for human users to prove to websites that they're human, sometimes through tasks like challenges or logins."

The proposed solution here is to allow web developers to reject any user that cannot prove they have viewed Google-served ads with their own human eyes.

It is essential to combat this proposal now, while it is still in an early stage. Once this is rolled out into Chrome and deployed around the world, it will be extremely difficult to rollback. It may be impossible to prevent this proposal if Google is allowed to continue owning the entire stack of website, browser, operating system, and hardware.

Thank you for your consideration of this important issue.

I get that there are extremely rare side effects for certain individuals, there's no such thing as a perfect medication afterall. But OP here is clearly either trying to be a troll or peddling conspiracy bs and it's not worth anyone's time to engage with them beyond telling them that they're full of shit.

I'd have to look at the code to be sure, but I'd guess it converts the timestamp into the browser's timezone. You could test this by changing the timezone on your computer and seeing how Lemmy displays it.

At least that's how I'd build it. Keeping backend times in UTC and then converting on the frontend to the user's set timezone is generally a best practice. Using non-UTC times on servers is just asking for trouble.

Take your blatant conspiracy theory bullshit elsewhere.

I’ve tried posting about the side effects a few times but it always gets downvoted to oblivion, so I guess most people don’t want anyone to know about the side effects and want the government to censor that information, but I don’t understand why.

Because everything you've posted here is bullshit. The mRNA COVID vaccines have been widely available for 2+ years now and it's definitively shown to have saved many lives without serious side effects.

What's more likely: forgetting the master password to your password manager or one of the many passwords you have memorized? I totally get not wanting to trust a hosted service with all of your passwords in case it disappears (having an offline backup would remedy that), but not using one out of fear of forgetting a master password is overblown.

+1 for Kagi. I finally decided to drop Google after their bullshit WEI proposal with Chrome recently and it has been great so far. Yes, Kagi is paid, but we all know the saying that "if you're not paying for it, you are the product." That's not the case with Kagi.

Yup, it's expired.