110 members have voted

  1. 1. Which team will win the Constructor's Championship?

    • Red Bull Renault
    • McLaren Mercedes
    • Ferrari
    • Mercedes GP
    • Lotus Renault GP
      0
    • Williams Cosworth
    • Force India Mercedes
      0
    • Sauber Ferrari
    • Scuderia Toro Rosso Ferrari
      0
    • Team Lotus Renault
    • Hispania Racing Team Cosworth
    • Marussia Virgin Racing Cosworth
  2. 2. Which driver will win the World Driver's Championship?

    • Sebastian Vettel
    • Mark Webber
    • Lewis Hamilton
    • Jenson Button
    • Fernando Alonso
    • Felipe Massa
    • Michael Schumacher
    • Nico Rosberg
      0
    • Nick Heidfeld
    • Vitali Petrov
      0
    • Rubens Barichello
      0
    • Pastor Madonaldo
      0
    • Adrian Sutil
      0
    • Paul di Resta
      0
    • Kamui Kobayashi
    • Sergio Perez
    • Sebastian Buemi
    • Jaime Algersuari
    • Other (specify below)
      0


Recommended Posts

You see that big strip of tarmac that is 20 feet wide, thats called a 'road', Cars drive on roads.

yes i see the tarmac. cars drive on roads, formula specification cars drive on roads and cut the track by using kerbs.

The other drivers managed fine, if he didnt cut the corner so much he wouldnt trash his suspension thats twice hes done it in as many days, you shouldnt be able to cut a corner so much without a penalty and the penalty is damaged suspension.

bold statement after the last weeks and in mind what happend to simoncelli and wheldon. do you remember south korea? i guess it was there when some of the kerbs just BROKE while cars cut it. its a clear security problem. look at monza/montreal and some other tracks. there they got it solved. add some "bumps" arround the kerbs, so riding and cutting the kerbs wont be an option. it was the same in monaco 2009, when massa and others rightfully cut the kerb and next year it was solved by track constructors.

this is what i fully expect to happen in india too.

you make it look like it was a driving mistake from massa, while i argue that others were just lucky not to get caught in the same situation. its not like others avoided kerb and massa fully cut it. if so he would have lapped full 2 seconds or so faster (given the lenght of the track) than all other cars.

answered in red :)

answered in red :)

They aren't supposed to cut the corners, they're given some leniancy but technically they shouldn't creep over the white lines at the side of the track because it isn't part of the track. The corner Massa hit wasn't a tight chicane or anything, he cut the corner too much, which ordinarily would shorten the track and improve lap time. They've rightfully opted to lay down something to prevent drivers from doing that, and all but one driver avoided hitting it too many times today.

The track is the track and if you can't stick to it you deserve to be thrown out of the race. Otherwise, where do you draw the line?

  • Like 1

They aren't supposed to cut the corners, they're given some leniancy but technically they shouldn't creep over the white lines at the side of the track because it isn't part of the track. The corner Massa hit wasn't a tight chicane or anything, he cut the corner too much, which ordinarily would shorten the track and improve lap time. They've rightfully opted to lay down something to prevent drivers from doing that, and all but one driver avoided hitting it too many times today.

The track is the track and if you can't stick to it you deserve to be thrown out of the race. Otherwise, where do you draw the line?

so then you just would throw out montreal, monza and monaco out of the calendar then because there, all drivers cut the track. several times a lap?

i have a very clear opinion on this: either you make the kerbs the way that no driver can cut them like seen here:

gloc_monz_toyo_2009_470150.jpg

or you make the kerbs the way, that by cutting them you still are inside the track, no rule is broken, and a normal f1 cars suspension survives the additional load like seen here:

buem_toro_montreal_2011-1.jpg

when they manage to get this done in montreal, monaco, monza and other tracks, then surely they should be able to do it in india as well. as it was the first year, i give them the benefit of doubt, but again, i bet with everyone here that by next year this is fixed.

answered in red :)

Im not trying to trivialise their deaths but all bikers have to protect them is a helmet and leathers, if you are leaning and a bike comes flying up 150-200mph and smacks you in the head there is nothing they can do to prevent that safety wise.

As for Wheldon im pretty sure i read that there were some safety concerns about the cars racing on that track in tight groups it was unfortunate he hit the car in front with launched him into the barriers.

Massa on the other hand was cutting the corner far too much, its not like it was an isolated incident he did it again and again and again and eventually his suspension snapped safely in the manner that it was designed to snap, you arent supposed to cut corners that much which is why that orange curb is there. No one else on the track that day had any issues with that curb because they raced properly.

I'm pretty sure the rules around jumping and cutting corners states that at least two wheels, front and rear, must remain on the track at all times, or within the confines of the track, the correct side of the white lines.

The exception to this, as the picture clearly shows on McLaren2 post, which looks like the exit of the last corner in Montreal, all the wheels are off the track. This because this line is technically making the track longer, and the driver gains no advantage to taking this line

Drivers trying to cut the chicane prior to this corner are penalize, as they do clearly gain some advantage.

Just on the Massa/Hamilton issue, I think it's quite interesting that everyone is blaming Hamilton.

A couple of races ago, Hamilton was defending from Massa, who sent one up the inside, only for Hamilton to intentionally turn in on him. Massa got a puncture and had to pit for repairs.

Result: Drive-thru for Hamilton for turning into Massa.

India: Massa was defending from Hamilton, who sent one up the inside, only for Massa to intentionally turn in on him. Hamilton got his front wing badly damaged and had to pit for repairs.

Result: Drive-thru for Massa for turning into Hamilton.

I thought the stewards did an excellent job today of showing that they're applying the rules equally and fairly. How is this suddenly ferocious pro-Hamilton support by the stewards? Bloody stupid.

I thought the track was boring. As for the Massa incident, well he could have avoided it, after all he did defend his postion so he knew Lewis was with him and he would have known he shouldn't have even defended as it pushed him a bit to far out, so he gave more then enough space.

As for cutting corners, well F1 drivers don't want to cut corners that want want to make the most out of the track. And for when cars go wide over the lines it depends if it adds any length to the circuit. So if you cut a corner yeah you're reducing the length, but if you go wide you're extending it so nothing happens to you.

Pat Fry: “There are many elements worthy of note that have come out of this weekend in India. Again today, we had a suspension failure, this time the front left on Felipe’s car: first analysis indicates the break was generated by a series of factors, starting with the collision with Hamilton. After that came the punctured tyre and it ended with the impact with the kerb.

now thats interesting. after the collision with hami felipe suffered a (slow?) puncture and that could indeed have caused the suspension to collapse if he went over the kerb. a normal working tire would just have taken the hit normally i say.

No, he had gone into the pits for a fresh set of Prime tyres then he binned it into the curb. Pat Fry is just trying to stirr up controversy, Massa went nowhere near Hamilton in Qualifying, whats the excuse there?

Don't really know the context of the qualifying statement, but Schumacher went nowhere near Rosberg. And Vettel should win most races by 3/4 of a lap with his qualifying pace. So how and where Hamilton is relative to Massa in qualifying trim don't mean much. As it is, Hamilton hardly seem to had much pace anyway, so it was always going to be a scrap.

I like Massa, but what I see is: He hit the kerb hard, he broke suspension, he crashed. Maybe Hamilton caused the damage, maybe Ferrari just have a weak suspension. Either way, both of his crashes involved going over the orange kerb, which is supposedly a no-no, so he can't blame anyone.

As for the penalty, I say racing incident. But because Hamilton needed a nose change and Felipe didn't, I think Massa was rightly penalised but it was a hardly clean bit of racing. Lewis was an idiot and naive to stick his nose there, it was always going to be a risk. Is not an overtake area, Massa was always going to have to cut back in. The verdict is that Massa needlessly took his racing line, he can have avoided by running wide, he didn't have the inside, he had room. If Lewis hit him despite giving him space, then sure, Lewis was in the wrong. But with the way Massa turned in, Lewis would had never had a chance to avoid it after he committed. Noentheless, I can see why Massa would feel aggrieved but while we can say drivers are reckless, drivers who stubbornly hold their ground despite imminent crash is also in their own way, reckless.

Frankly, two bit of a stubborn racing for 2 racers who looked ordinary for the season pretty much.

Don't really know the context of the qualifying statement, but Schumacher went nowhere near Rosberg. And Vettel should win most races by 3/4 of a lap with his qualifying pace. So how and where Hamilton is relative to Massa in qualifying trim don't mean much. As it is, Hamilton hardly seem to had much pace anyway, so it was always going to be a scrap.

I meant in the context of him hammering the suspension off the the orange curb, mclaren2/pat fry are insinuating that the collision between Hamilton and Massa was the reason his suspension failed. I was saying Hamilton wasnt driving anywhere near Massa and Massa still smashed his suspension so what is the excuse for Qualifying.

I went back and watched some footage from Quali and Race, Massa lap after lap consistently went nearly all 4 wheels off the track smashing that orange curb, its not a track/safety issue, its not crashing with another car issue, its his driving style destroying his car nothing else.

As to who could replace Massa at Ferrari: Nico Rosberg has yet to be confirmed for 2012 by Mercedes GP. Just a thought.

kimi could also replace him, if he decides to come back, at least he would be in a better car than the williams

kimi could also replace him, if he decides to come back, at least he would be in a better car than the williams

I've also thought about that. Dump Massa for Raikkonen - it'd be an interesting pairing. Would Alonso like being paired with a very capable world champion? I would like to see him make a return no matter what team he drives for.

raikkonen who got beaten by massa at ferrari should now replace him? that just made my day :laugh:

You've really got selective memory, haven't you. Yes, Massa beat Kimi in one of the three seasons that they were teammates (2008), but Kimi beat Massa in the other two seasons (2007, 2009), and even won the world drivers championship in '07, something that Massa hasn't done.

Just to compare the two...

2007 Season:

Massa - 4th (94 points)

Kimi - 1st (110 points)

2008 Season:

Massa - 2nd (97 points)

Kimi - 3rd (75 points)

2009 Season:

Massa - 11th (22 points)

Kimi - 6th (48 points)

Now, there is the benefit of the doubt in this season, as Massa only took part in the first ten races, due to his accident, so these were the standings after the first ten races:

Massa - 22 points

Kimi - 18 points

But the main point still stands; Kimi is the better driver overall. He's won a WDC, Felipe Baby hasn't.

BTW, I don't understand why you're such a Ferrari fanboy with a username like "mclaren2". You oughta change it to something else...

ok this nails it for me. talking about selective memory and then NOT taking into account the fact that massa could only drive half of the season in 2009. till hungary 2009 massa was leading raikkonen by double amount of points. just saying....

ok this nails it for me. talking about selective memory and then NOT taking into account the fact that massa could only drive half of the season in 2009. till hungary 2009 massa was leading raikkonen by double amount of points. just saying....

Double??? Read it again...

Massa - 22 points

Kimi - 18 points

A difference of 4 points; that is not double. Kimi would have had to have 11 points for Felipe to have double the points.

This topic is now closed to further replies.
  • Posts

    • We have disabled advertising in the forums for now for an undetermined period. If you feel like you get a lot of value out of the site please do whitelist ads on the news articles, and/or consider getting a subscription, we offer two tiers, one at: $14 per year (support the site for just over a dollar a month) or the $28/year tier (just over $2/month) that disables advertising and affiliate link tracking throughout the site (so also on the news side). We also have a 'Buy us a coffee' page if you just want to make a one-time donation. I am not mincing words when I say it is becoming harder and harder to monetize publications like Neowin, it's a fact of life that when we can no longer afford to pay for everything we'll go like many other sites already have. It doesn't have to cost you anything There are other ways to support Neowin too, like posting on topic content in the forums (technical support/questions/helping others) and sharing our news articles.. this costs nothing but your time and is just as important as subscribing or making a monetary donation! Anyway thanks for your time and continued support of Neowin. Now in our 26th year, and hopefully many more! For all the lurkers out there that whitelist us, make a free member account, and see fewer (only inline) ads on the news side  
    • BATorrent 3.0.2 by Razvan Serea BATorrent is a lightweight, open-source BitTorrent client built with modern C++ and Qt 6, offering a clean, fast, and privacy-focused alternative to traditional torrent apps. It supports magnet links, .torrent files, resume data, sequential downloading, per-file priorities, and even imports from qBittorrent. Power users benefit from integrated RSS auto-download with regex filtering, duplicate detection, and automatic tracker lists from Stremio. Streaming is seamless thanks to auto-detected players like VLC and IINA. BATorrent includes robust VPN tools—interface binding, auto-detection for WireGuard-based services like Mullvad and NordLynx, kill switch, proxy support, and IP filtering. A full WebUI enables remote control, while integrations with Plex, Jellyfin, and Emby automate library updates. With themes, speed scheduling, system-tray alerts, and cross-platform support for Windows, Linux, and macOS, BATorrent delivers a polished, high-performance torrenting experience. BATorrent features: Core .torrent file and magnet link support Resume data — picks up where you left off after restart Import torrents from qBittorrent Create .torrent files from any file or folder Sequential download mode Per-file priority control (skip, low, normal, high) Seed ratio limits with auto-pause DHT, PEX, UPnP, NAT-PMP RSS Auto-Download Subscribe to RSS feeds — automatically download new torrents as they appear Regex filters — match only what you want (e.g. 1080p|720p, S01E\d+) Per-feed settings — custom save path, check interval (5–1440 min), enable/disable Auto-download — matched items are downloaded automatically in the background Supports magnet links, .torrent URLs, and tags Tray notifications when items are auto-downloaded Duplicate detection — never downloads the same item twice Stremio Stremio Addon System pre-installed — works out of the box Auto tracker list from ngosang/trackerslist Streaming Play while downloading — stream video files before the download is complete Supports mp4, mkv, avi, mov, wmv, flv, webm, m4v, ts Auto-detects installed players (VLC, IINA, system default) VPN & Privacy Interface binding — lock torrent traffic to a specific network interface (e.g. tun0) Auto VPN detection — identifies VPN interfaces (tun, tap, WireGuard, Mullvad, NordLynx, ProtonVPN) Kill switch — automatically pauses all torrents if the VPN interface drops Auto-resume — resumes only the torrents paused by the kill switch when VPN reconnects Proxy support — SOCKS5 and HTTP proxy with optional authentication IP filtering — load P2P blocklists to block unwanted IP ranges Protocol encryption (enabled / forced / disabled) WebUI Remote management — control torrents from any browser at http://localhost:8080 REST API with JSON responses Add torrents via magnet link or .torrent upload Pause, resume, remove torrents remotely View peers and files per torrent Dark theme matching the desktop app HTTP Basic Auth with SHA-256 password hashing Configurable port and remote access (localhost vs 0.0.0.0) Interface 3 themes: Dark, Light, Midnight (bat/vampire aesthetic) Real-time speed graph Detailed panel with tabs: General, Peers, Files, Trackers Filter bar: search by name, filter by state (Active, Downloading, Seeding, Paused, Finished) Drag & drop .torrent files and magnet links Drag & drop reorder in torrent list System tray with notifications (download complete, kill switch events, RSS auto-downloads) Splash screen with bat animation Bilingual: English and Portuguese (BR), auto-detected from system locale Bandwidth Scheduler Alternative speed limits — set different download/upload limits on a schedule Time range — configure active hours (e.g. 01:00 to 07:00), supports overnight ranges Per-day control — choose which days of the week the schedule applies Automatically switches between normal and alternative speeds Media Server Integration Plex — automatically trigger library scan when a download completes Jellyfin / Emby — same automatic library refresh via API Configure server URL and authentication token/key in Settings System Cross-platform: Windows, Linux, macOS Auto-shutdown — automatically shut down PC when all downloads complete (60s cancellable countdown) Auto-update system (AppImage on Linux, installer on Windows, DMG on macOS) CLI arguments: pass .torrent files or magnet: URIs directly Keyboard shortcuts: Space to toggle pause, Ctrl+A to select all, Ctrl+O to open BATorrent 3.0.2 changelog: Phone pairing & WebUI The browser WebUI was reskinned to match the desktop app — same dark palette, Inter font, flat surfaces, the real BATorrent logo (it was a random bat before), and a proper magnet icon. It now looks like the same product, not a separate dashboard. Pairing is one tap and zero typing: the generated WebUI password is now copyable, and the QR code carries the credentials — scanning it from your phone logs straight in (no typing the IP or password), then drops the credentials from the address bar. Search Two new providers: RuTor (CIS sources, no login, via a public TorAPI relay) and Torrents-CSV. Results are sorted by seeders (healthiest first), and each search now times out after 15 s so one dead provider can't hang the UI. Files & trackers Per-file priority is back: right-click a file in the detail panel to set Skip / Low / Normal / High. Rename an individual file inside a torrent (double-click or the file menu), separate from renaming the torrent. Remove a tracker from a torrent (the ✕ on a tracker row); adding was already there. Smart Paste on Ctrl+V — paste a magnet, a 40-char info-hash, or a .torrent URL straight from the clipboard and it's added immediately (text fields still paste text normally). Covers & titles Anime fansub naming ([Group] Title - NN) now resolves to the right show. Audio channel layouts in titles (DDP5.1, 7.1, …) are stripped so they don't pollute cover matching. Under the hood The legacy QWidget interface is gone. QML had been the only UI since 3.0.0 (reachable old code lived behind a hidden --legacy flag); with parity confirmed, the entire QWidget layer — main window, every dialog, the theme manager — was removed (~13,400 lines). The four restored actions above were features that backend already supported but the QML port had never wired. macOS: the WebUI password hash moved out of the keychain into app settings, so launching the app no longer pops a login-keychain password prompt on unsigned builds. The actual password still lives in the keychain. Cleanup: ~400 orphaned translation strings and a batch of dead code removed; internal duplication collapsed; an ARCHITECTURE.md added for contributors. Unit / security / memory tests and the ASan/UBSan/TSan sanitizers stay green. Download: BATorrent 3.0.2 | 30.5 MB (Open Source) Download: BATorrent Portable | 42.3 MB Links: BATorrent Website | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • How about a global switch to turn the awful things off instead of a registry hack? Then everyone wins.
    • This doesn't strike me as so shocking when... " IT admins do have some control over this rollout. If they choose to opt out, devices in their tenant won't automatically get the dreaded Copilot app"
  • Recent Achievements

    • Mentor
      grik went up a rank
      Mentor
    • Dedicated
      JKR earned a badge
      Dedicated
    • One Year In
      CHUNWEI earned a badge
      One Year In
    • Conversation Starter
      FBSPL earned a badge
      Conversation Starter
    • Week One Done
      I2D earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      475
    2. 2
      PsYcHoKiLLa
      262
    3. 3
      Skyfrog
      79
    4. 4
      ATLien_0
      60
    5. 5
      FloatingFatMan
      60
  • Tell a friend

    Love Neowin? Tell a friend!