Forums online, news to follow


Recommended Posts

But you'd have to be in here to read that comment in the first place.

Something of a catch-22 here. :p

Actually thats how I always went to the forums, and then navigated to

the main page from there. :shiftyninja:

Pinging 67.19.42.49 with 32 bytes of data:

Reply from 67.19.42.49: bytes=32 time=123ms TTL=245
Reply from 67.19.42.49: bytes=32 time=112ms TTL=243
Reply from 67.19.42.49: bytes=32 time=111ms TTL=245
Reply from 67.19.42.49: bytes=32 time=112ms TTL=243

Ping statistics for 67.19.42.49:
	Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
	Minimum = 111ms, Maximum = 123ms, Average = 114ms

Pinging 66.28.242.201 with 32 bytes of data:

Destination host unreachable.
Destination host unreachable.
Destination host unreachable.
Destination host unreachable.

Ping statistics for 66.28.242.201:
	Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

Tracing route to 49.67-19-42.reverse.theplanet.com [67.19.42.49]
over a maximum of 30 hops:

  1	10 ms	11 ms	 9 ms  host-83-146-18-45.bulldogdsl.com [83.146.18.45]

  2	 9 ms	 9 ms	 9 ms  ge-3-0-0.32.cht-cor-002.bddsl.net [83.146.22.94]

  3	 9 ms	 9 ms	 7 ms  so-1-0-0.0.cll-cor-002.bddsl.net [83.146.19.45]

  4	11 ms	 9 ms	 9 ms  999.ge6-2.mpr1.lhr1.uk.above.net [217.79.160.12]

  5	11 ms	 9 ms	 9 ms  so-4-1-0.cr1.lhr3.uk.above.net [208.184.231.174]

  6	11 ms	 9 ms	 9 ms  so-0-0-0.cr2.lhr3.uk.above.net [208.184.231.146]

  7	 *		*		*	 Request timed out.
  8	 *		*		*	 Request timed out.
  9   110 ms   111 ms   110 ms  216.200.6.237.theplanet.com [216.200.6.237]
 10   113 ms   112 ms   112 ms  vl31.dsr01.dllstx3.theplanet.com [70.85.127.29]

 11   113 ms   112 ms   112 ms  vl42.dsr02.dllstx4.theplanet.com [70.85.127.91]

 12   119 ms   112 ms   114 ms  49.67-19-42.reverse.theplanet.com [67.19.42.49]


Trace complete.

Tracing route to 66.28.242.201 over a maximum of 30 hops

  1  Destination host unreachable.

Trace complete.

I don't quite get you...subforums? They run the software..?

For me, the main forum that contains all the subsections and subforums is displayed in the old(er) version while the subsections/subforums ie: General Discussion or Site & Forum Issues contains the new version where the posts are highlighted with the mouseover and all the other cool new features.

Yesterday it was fine though, both the main forum and its subsections contained the new version

yeah whens the front page comin' back up, i miss it :(

no time-table has been given yet for the release of the new frontpage. The GFX team and the other coders are still in process of getting the final coding and tweaking done.

I'm sorry but you guys must have a bad development model... because before you deploy you are ALWAYS supose to get all codeing done and working and fully tested so you can have a seamless deployment... this should of all been done before it was ever tansitioned over... you should of made a backup copy of the database to this new place, set up the entire sit ethere first tested it out completely while letting the old neowin running on neowin.net. once you where sure all the code worked then sync the databases... you really need to look into changing how you guys do things...

Can see the websites usage decrease more and more every day, and those lost members won't ever return :/

Well you we could do with there been less users because the severs were not coping and now we have new severs with less users, so it should be even faster! :ninja:

I might of been a good idea is they did get 3.9 Swift script ready before moving to new severs, but then what right do I have to comment.

I'm sorry but you guys must have a bad development model... because before you deploy you are ALWAYS supose to get all codeing done and working and fully tested so you can have a seamless deployment... this should of all been done before it was ever tansitioned over... you should of made a backup copy of the database to this new place, set up the entire sit ethere first tested it out completely while letting the old neowin running on neowin.net. once you where sure all the code worked then sync the databases... you really need to look into changing how you guys do things...

What did you think we did? Bugs happen and were working on getting them fixed. We expected the complete transfer to occur on the 29th, however some things poped up that blocked us from releasing the main page to the public.

I can see the main page and its making good progress. It's not like its going to be down for months. :rollyes:

We are working on the issue and hope to get it resolved very soon...

What did you think we did? Bugs happen and were working on getting them fixed. We expected the complete transfer to occur on the 29th, however some things poped up that blocked us from releasing the main page to the public.

I can see the main page and its making good progress. It's not like its going to be down for months. :rollyes:

We are working on the issue and hope to get it resolved very soon...

Thanks Shockz. That's good enough for me. Keep up the good work guys. :yes:

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • The laptop in the bedroom is an Acer with i7-10510U CPU. Acer's website states they will not be upgrading it so I had little choice other than disable secure boot. I know next to nothing on these matters so hopefully it will be fine.
    • GitHub removes manual model selection from Copilot free and student plans by Karthik Mudaliar GitHub is removing the ability to manually select an AI model from its Copilot Free and Student plans, making its automatic routing system the default and only way to choose a model. This means users on these tiers will no longer be able to deliberately select a particular OpenAI, Anthropic, Google, or Microsoft model for a task. In its announcement, GitHub said Copilot Auto will dynamically choose what it considers the best model for each request. Free and Student accounts will retain access to models from multiple families, although the available selection will continue to depend on the restrictions attached to each plan. GitHub did not identify a fixed pool of models that Auto will always use, and its documentation warns that model availability can change over time. GitHub describes Auto as more than a random fallback system. On supported surfaces, its task-optimization technology evaluates the complexity of a request alongside real-time information about model health and availability. Straightforward prompts can be routed to faster and less expensive models, while more demanding coding tasks may be sent to higher-cost reasoning models. The company says this approach should reduce rate limiting, latency, and failed requests. Auto generally selects one model along natural prompt-caching boundaries rather than repeatedly switching models during a session, as GitHub found that mid-session changes increased costs without producing sufficient improvements in output quality. Users can still check which model generated a response. In Copilot Chat, the information appears when hovering over an answer, while Copilot CLI and the Copilot cloud agent display the selected model alongside their output. Auto is available in Copilot Chat, Copilot CLI, and the cloud agent, with the exact implementation and release status varying between supported development environments. The latest restriction follows several months of adjustments to Copilot’s individual plans. GitHub temporarily halted new Pro, Pro+, and Student subscriptions in April as it sought to manage demand and service reliability. It later introduced token-based billing and began gradually reopening individual-plan registrations on June 17. Alongside the picker change, GitHub is retiring the “Preview” label from Microsoft-developed models. It argues that the label is no longer necessary because Auto handles model routing and models are continuously updated behind the scenes.
    • Look up 'inflation' kid. Ask an AI for the numbers between both games.
    • Google reportedly set to lose two key Gemini and DeepMind researchers to Anthropic by Karthik Mudaliar Google is reportedly preparing to lose two more prominent artificial intelligence researchers, with Gemini contributors Jonas Adler and Alexander Pritzel planning to join rival AI developer Anthropic. According to a report from Bloomberg, both researchers are viewed internally as important contributors to Google’s flagship Gemini model family. Adler worked on Google’s AI coding efforts, while Pritzel was involved in the process used to train AI systems. Neither company has publicly confirmed the moves. The report also does not say when the researchers will formally leave Google or what positions they will hold at Anthropic. Training a large AI model requires decisions covering its architecture, data preparation, distributed computing infrastructure, and post-training methods that shape how the finished system behaves. Researchers with experience operating at the scale of Gemini are consequently difficult to replace quickly. Both Adler and Pritzel have previously contributed to Google DeepMind’s scientific research as well. They are listed among the authors of the company’s work on expanding AlphaFold protein-structure predictions across entire proteomes, alongside AlphaFold researchers including John Jumper. The reported departures arrive shortly after another important change within Google’s Gemini organization. Gemini co-lead Noam Shazeer is leaving Google for OpenAI, after returning to the search company in 2024 through its deal with Character.AI. Shazeer is particularly well known as one of the authors of the Transformer paper, whose architecture became the foundation for most modern large language models. Anthropic, meanwhile, has been recruiting recognizable figures from other leading laboratories. OpenAI co-founder and former Tesla AI director Andrej Karpathy joined Anthropic’s pre-training team in May. His move, followed by the reported recruitment of several Google researchers, suggests Anthropic is strengthening the research teams responsible for the core capabilities of future Claude models rather than concentrating solely on product and enterprise sales. The competition is complicated by the companies’ extensive commercial relationships. Anthropic competes directly with Google’s Gemini models, but it also relies on Google as an infrastructure partner. In April, Anthropic announced an expanded agreement with Google and Broadcom covering multiple gigawatts of next-generation Tensor Processing Unit capacity. TPUs are Google-designed accelerators used to train and run large AI models. via Bloomberg
  • Recent Achievements

    • One Year In
      Philsl earned a badge
      One Year In
    • Dedicated
      Scoobystu earned a badge
      Dedicated
    • First Post
      Tom Schmidt earned a badge
      First Post
    • One Month Later
      D0nn13 earned a badge
      One Month Later
    • Rookie
      +ChiefOfNeo went up a rank
      Rookie
  • Popular Contributors

    1. 1
      +primortal
      461
    2. 2
      +Edouard
      177
    3. 3
      PsYcHoKiLLa
      124
    4. 4
      Michael Scrip
      79
    5. 5
      Xenon
      76
  • Tell a friend

    Love Neowin? Tell a friend!