Your First Car


Recommended Posts

first car i ever drove was a 1993 325i sedan, automatic.. i was 9 years old and my dad just let me go around the block with him. What sironic is that the first car my dad bought me turned out to be the same body style couple years ago now im 19, it was a 1992 318is 5spd red... this is what happened to the porr car because i guess you can say im an idiot?...

2ivlkld.jpg

  • 2 weeks later...
  • 2 weeks later...

My First car 1963 Chevy Corvair Monza. , I paid $125.00 for it in 1980 , it was in pretty bad shape, but my friend & I fixed it up and I drove it for almost 6 months, before it died again and I sold it to a collector for $150. and he towed it away.

Between then and now I have owned 23 cars.

HAROLD%20DUNN%201963%20CHEVY%20CORVAIR.jpg

This is a 1963 Corvair, the car in photo is just a googled photo of a '63 corvair, my Corvair was similar and same color.

1979 Ford Mustang Cobra. 2.3L turbocharged four-cylinder.

The same four, six and eight-cylinder engines were used as before, with the addition of a turbocharged 4-banger that developed 140 hp (same as the 302 V-8 version).

Many people will claim that there wasn't a Cobra in '79, but I had the door and dash emblems to prove it.

Too bad I don't have pictures. I had to buy a clutch and pressure plate for it and they were the same part number as the V8.

B reg (1984) FSO Polonez bought for 450 quid in England in 1991.

It featured a rear heated back window and 5 speed gearbox (1.5L) I had the 'Prima' version which meant it came with extras and yes, it was that color like on the image.

04f4aefd23f59842.jpg

Don't laugh..

This is what I drive now, but mine is Cobalt Blue 1993 3201 (2.2L 6cylinder) mine is also M Sport

39eg.jpg

Edited by Neobond
B reg (1984) FSO Polonez bought for 450 quid in England in 1991.

It featured a rear heated back window and 5 speed gearbox (1.5L) I had the 'Prima' version which meant it came with extras and yes, it was that color like on the image.

04f4aefd23f59842.jpg

Don't laugh..

Oddly, looks like an old Volkswagen Dasher / Passat.

Vw_passat_b1_v_sst.jpg

  • 1 month later...

My first car was a 1995 Saturn SL1

Pros:

Cheap on gas

Cost me $500 CND

Got me where I needed to go

Cons:

Burned about a quart of oil every 3 days.

250,000kms

Engine was getting laggy.

Front windows leaked when it rained

Trail of smoke wherever I went

Mods:

None

Current Car: 2001 Chrysler Intrepid SE

Pros:

Like driving a sofa

Large back seat ;)

Got it for very cheap, with low (70,000kms)

Cons:

Not so cheap on gas.

Mods:

Pioneer MP3/WMA/AAC deck

Dual MTX 12" Sledgehammer subs

1200W dual channel MTX amp

Stinger Cap and access.

  • 3 weeks later...
  • 3 weeks later...

My first car was/is a 1992 Toyota Corolla.

Pros:

Inherited.

Was at one time nice.

Four door + trunk = reasonable equipment hauling space.

Gas mileage.

Only 98k miles :)

Cons:

That thing's got an EFI!

Sounds like a damn ricer stock.

Is a damn ricer.

Hasn't been regularly driven for years.

Interior is wrecked up from years of family use.

No damn extras! In '92 there were powered windows, locks, and top windows! This one didn't even come with cruise control stock.

Current status:

Chilling outside our garage in a useless state.

- a tire, battery, and window.

But it's okay. About to pick up a '91 Camaro with T-tops :) And also possible a Buick Electra. Power to the people!

  • 3 weeks later...

2006_Kia_Rio__front.jpg

What was the first car you ever driven?

My first car

Beige Exterior/Interior 2007 Kia Rio LX

pros

Cheap on Gas

Small and mobile

Power everything

cons

Lack of power uphill

No aux port

engine problem in its first 2 weeks

Current Status

At the repair shop, its been 3 weeks. Hope to get it back tomorrow.

My First Car: Hyundai Santro Club GV 2003 Model

Current Car: Honda Civic i-VTEC Prosmatec 2007

Pros (First Car): Nice Car To Drive In A Heavy Populated Area Being A Small Car And It Has Factory Fitted CNG So Quite Economical Too.

Cons (First Car): Being A 1000cc Car, It Doesnt Have Good Pick Up

Pros (Current Car): Luxurious, Comfortable Interior With A Powerfull 1800cc Petrol Engine Which Has Good Power.

Cons (Current Car): Its Hard On Petrol Which Is Already Expensive Here

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • This whole dumb age verification thing needs to die and be replaced by giving parents tools to control devices. Why am I required to plaster my ID all over the internet to prove I'm old enough when parents should be the ones dictating what their kids are doing on their phones. Apple released great set of tools for iPhones coming to iOS 27 that do just that. Why are governments not mandating that kind of control to phone makers to built them into phones. This whole thing is so absolutely idiotic it's wild.
    • Remeber this decade, when the free internet died... tell your grand kids about this, record there reaction and post it on InstaTwitBook.com
    • UK nudity blockers are a looming privacy disaster, we must be able to see the source code by Paul Hill Image via Pexels The UK government, just like many state governments in the US and national governments around the world, has begun going on a bit of a power trip when it comes to digital safety. The major step taken so far is the introduction of the Online Safety Act, which requires users to prove their age to access adult websites (it includes more than this, too). Now, UK PM Keir Starmer is calling on Apple and Google, and presumably other mobile OS makers, to scan phones for explicit images to protect children. This potentially mandatory on-device scanning by vendor-controlled software will create unacceptable harms to individual freedoms and transparency, and introduce massive surveillance risks. In a statement on June 8, the Prime Minister stated that big tech companies, such as Apple and Google, must add features to their platforms, such as iOS and Android, that will detect and block sexually explicit or nude images involving under-18s on phones or tablets. Adults who want to take or send nudes would be required to hand over some form of identification to stop their phone from blocking these pictures, creating unnecessary privacy risks. According to the government, it wants to see these measures implemented within three months; otherwise, the government will introduce legislation to force them to introduce such technology. The legislation will include fines for companies and maybe even criminal liability for tech bosses who do not comply with the measures. In its announcement, the government said that stopping users from taking, sending, or receiving nudes without verifying their age is technically feasible, and pointed to a British firm called SafeToNet, which has made proprietary, closed-source, uninstallable software called HarmBlock and is actively selling a device with it enabled and is working with other OEMs. The fact that this software is closed source is a huge problem because it’s a black box; you do not know what it is doing on your device. The fact that it is unremovable is also a problem because you lose control of a phone that you own. Laughably, the government, just before highlighting SafeToNet, says that companies must introduce such measures “without threatening privacy or collecting any data.” It then says over-18s will still be able to view adult content by providing proof of age… Which sounds to me like data collection. SafeToNet makes some debatable claims about HarmBlock The government’s example software, HarmBlock, is a hugely alarming choice to espouse the virtues of this type of software. SafeToNet claims that HarmBlock is “ethically developed,” but this is the opposite of the truth. This black box software puts digital handcuffs on you if it’s installed in your device, taking away your freedom to control what software runs on your device, as it cannot be removed. It is not even free software, so we cannot inspect the source code to see what it is doing. For all we know, it could be acting maliciously. While that’s unlikely, we can’t verify that it’s not doing that. When Google and Apple do inevitably integrate these features on devices in the UK, they are very likely to be closed-source binaries, which will also be non-auditable. They will also have identity services built into them, which will require at least temporary collection of sensitive identity documents to verify your age. One saving grace for Android users is that this nudity blocker will very likely be implemented within the Google Play infrastructure that’s deeply tied into commercial Android devices. However, anyone with enough determination to throw out Google apps from their phone by flashing a custom ROM could find they regain control over their phone again without these digital handcuffs. Obviously, this is only how I expect Google to implement the feature; if it bakes it into the open-source Android somehow, that would be bad news for anyone looking to escape it. Outside of stripping mobile phone users of their freedom and sovereignty over their devices, these proprietary on-device machine learning or hash-matching solutions cannot be independently audited. This means that hackers could potentially exploit them because security researchers can’t investigate the code, and they could overstep their intended use case and collect even more user data without anybody knowing. We also wouldn’t know if the code is prone to detecting false positives or biased classification, because we can’t see the code. In the government’s announcement, contributing comments from the Internet Watch Foundation keep talking about “on-device protections” as if to say that users don’t need to worry about server-side processing; however, this is misleading, as data could flow from devices for the purpose of updates, remote model changes, telemetry, or server-side matching. We’ve also seen with the Online Safety Act that the government is never content with the laws it introduces; it always wants to expand the controls. If this scanning functionality arrives on devices, it might only block nudes initially, but later governments could pressure vendors for expanded access or use mandated features for other surveillance aims. The introduction of on-device scanners opens the door to massive risks in the future. Once nude blocking becomes normalized, regulators like Ofcom or politicians themselves could push for more controls over people’s devices. Very possible candidates for blocking include hate speech, misinformation, or undesirable political content. Also, there is a chance that once Apple and Google have developed this software, they might attempt to reuse the infrastructure for commercial or foreign requests, putting customers in greater danger. Just the UK's demand for this sets a precedent. What if a dictatorship decides to spy on activists by demanding that Google or Apple implement similar controls? Another concern with this scanning is that it adds compliance costs for businesses looking to get into the mobile operating system space. While Google and Apple dominate the space right now, there are lots of smaller companies creating mobile operating systems too, including community projects with very shallow pockets. How are these smaller competitors supposed to implement sophisticated nudity detectors? Simply put, they can’t. Then the government goes after them, causes them to shut down, and Google and Apple have less competition. Image via Aurora Store For us users who value sovereignty over our technology, this development will force us to seek freedom-respecting alternatives. The simplest path forward will likely be to install a custom ROM on an Android device; however, kicking Google off the phone with its black box nudity blocker could also make it harder to access apps such as banking apps, which tend to need you to pass Google's integrity checks. Thankfully, Google Play Store apps can still be obtained by storefronts such as the Aurora Store, but it just adds to the friction. To be fair to those pushing this measure to protect children, I think it will be reasonably effective, but people will still try to find ways around it, just as they’ve done with age gates on adult websites introduced under the Online Safety Act. In the effort to find circumvention methods, it could lead users to join riskier platforms that introduce new dangers. This effort also diverts resources from proven interventions such as law enforcement cooperation, targeted investigations, education, and support services to broad technical controls that have uncertain effectiveness (due to their newness). If the government is set on introducing such tools, then there ought to be safeguards in place. Any mandated code should be released as free software so that it can be audited, and the binaries should be reproducible builds so that the public knows nothing has been tampered with in the code used to create the binaries shipped out. Ideally, these tools should also be voluntary, opt-in, and even community-run. This would also allow people to have full control over their hardware while allowing parents to flip a switch to turn on these protections for children, with the knowledge that the code being run is doing exactly what it says on the tin, and nothing nefarious, like a black box solution could be doing. The government should also have a narrow legal scope where this technology stays with blocking nudes and not spreading to blocking political opinions, hate speech, and so on. Ideally, any implementation should avoid identity-linked age verification to keep user data safe, and matching should be done locally with no server telemetry to ensure it is truly on-device. While I do understand that stakeholders such as parents want to keep children safe, the potential for abuse with this type of software is colossal. It would entrench black-box surveillance and take away our freedom to use our devices as we want. There is also the acute risk that the government will demand this surveillance be expanded to block other activities, which could be particularly dangerous. If you are in the UK and don’t wish to see these measures implemented, it is still possible to write to your MP, which could lead to some better safeguards being introduced before it’s too late. Once we get more technical information about how this will be implemented, then we will be able to see if de-Googling Android devices will bypass this measure. For anyone with an iPhone, there is zero chance that you’ll be able to take off these handcuffs because Apple doesn’t let you mess with your software.
    • I'm reading the reports as EU rejecting Apple's proposal because Trusted System Agent would be an intermediary offered to third party AI's (this article is also worded as such) but Siri AI itself would not pass this intermediary. This would cause a situation where Siri AI would have more direct system access and offer it an unfair advantage. (speaking from EU regulator perspective here) Apple is citing security issues with doing what EU asked for, and I think this also supports this theory, because truly direct system access like Siri AI would make it impossible to control third party AI's running on the devices and e.g. reign them in via adjustments to Trusted System Agent. So, I _think_ this is the sticking point right now: EU saying they need to be on equal footing as Siri AI, Apple saying they can't be because Apple only trusts their own AI. Apple could of course be leaning a bit extra hard towards this because they're biased in terms of excluding competitors. One method to find an agreement would be to have Siri AI also run through Trusted System Agent and treat it as untrusted. This kind of defensive architecture design (especially when involving an AI) would honestly not be a very bad idea from a sheer engineering standpoint. But then Apple would need to swallow their pride and adapt worldwide due to EU, and make perhaps major updates delaying Siri AI once more.
  • Recent Achievements

    • Very Popular
      Captain_Eric earned a badge
      Very Popular
    • One Month Later
      amusc earned a badge
      One Month Later
    • One Month Later
      DJC50PLUS earned a badge
      One Month Later
    • Week One Done
      DJC50PLUS earned a badge
      Week One Done
    • Proficient
      Eric Biran went up a rank
      Proficient
  • Popular Contributors

    1. 1
      +primortal
      511
    2. 2
      PsYcHoKiLLa
      220
    3. 3
      ATLien_0
      92
    4. 4
      +Edouard
      90
    5. 5
      Steven P.
      83
  • Tell a friend

    Love Neowin? Tell a friend!