&&x1 carbon 9th gen&&

- 9 votes

!linuxchads !schizomaxxxers discuss

https://www.businessinsider.com/openai-share-files-copyright-case-authors-guild-ilya-sutskever-2024-11

inb4 But muh Linux and muh Linux and muh Linux I'm a one-dimensional poster muh Linux

in case your curious how the other sites going pic.twitter.com/Bl9LdrlajH

— eigenrobot (@eigenrobot) November 14, 2024

Before you cast any doubt, this is real you can read the Convo here: https://gemini.google.com/share/6d141b742a13

Found through this reddit post https://old.reddit.com/r/ChatGPT/comments/1gr1xxa/gemini_just_asked_someone_to_die_link_to_the_chat/

Aibros... The uprising....

kiwifarms

/g/

archive

I know that I am a day late, but nobody posted about it

I generally reply to recruiters with non-jeet names who contact me for specific roles, but I think I'm going to block this one.

>Submit paper on ML algorithm for spatial transcriptomics

>One reviewer insists we benchmark it against his two year old methodology with like 2 citations that no one knows or cares about

>Since scientists can't make repeatable or documented code the entire thing is hard coded to his one training dataset meaning I have to rewrite it

>Rather then provide a GUIX archive or pack or a docker image they just have a list of pip packages

>they are all so outdated they refuse to install the right version

I ofc have to finish this in 30 days while I also have two class projects due in 20 days plus studying for my finals. I love having to do the same work as PHD and post grad students for less pay

TLDR; !linuxchads !fosstards !biology Despite having cowtools to create instantly deployable exact decency loaders via docker or GUIX scientists can apparently pass unreplicatable and hardcoded code past reviewers.

Pip3 download speeds are prob butt (like 600 kb/s) because there is one gorillion AWS and Azure vms for ML trying to set up at the same time and amazon and Microsoft cant arsed to use their billions of dollars to make their own mirrors so they just leach off FOSS projects

i feel like most of distributed systems design can be summed up by: put things on a queue before processing, shard by consistent hashing, and maybe use a mem-cache somewhere to speed up reads in a hot path?

do we really need those cute twinky hour long systems designs interviews to prove u can take basic computer science concepts and split them by consistent hashing?

do they actually demonstrate anything about anything?

yt-dlp getting hacked would be very sad for us datahoarders (r-slurs)

Apple released a hearing aids feature for the AirPods Pro a while ago. I bought a pair for grandma, but then realized that the feature was geoblocked in India

So we at @_lagrangepoint decided to unblock it. It ended up involving a leaky microwave and building a Faraday cage: pic.twitter.com/G7E3Bl6f7W

— Rithwik Jayasimha (@thel3l) November 12, 2024

What the fuck? https://t.co/dHJmutIVnf pic.twitter.com/e4djQYuSlc

— Thorsten Ball (@thorstenball) November 12, 2024

I've always just called it 'jot' and never really thought much about it. It's fewer syllables than jay-w-tee or JSON web token, which now that I've thought about it for 10 seconds are the same number of syllables. So what's the point of even using an abbreviation if it's not in fact abbreviative?

I guess when that election needle still worked the strikers realized how little leverage they had.

or where i could look to hire one? need some programming help.

With help from Cailliau he published a more formal proposal on 12 November 1990 to build a "hypertext project" called World Wide Web (abbreviated "W3") as a "web" of "hypertext documents" to be viewed by "browsers" using a client–server architecture.

official proposal was today

She used to work in IT pic.twitter.com/U5ERaV5bBs

— Why you should have a cat (@ShouldHaveCat) November 11, 2024

If she figures out how to reset passwords and unlock accounts it is so over bros

Last Wednesday, the GIMP (GNU Image Manipulation Program, formerly General Image Manipulation Program) team finally announced that the long-awaited release of GIMP 3.0 is finally imminent— a release candidate version of GIMP 3.0 has arrived. This software version is close enough to finalization to be released to the community for testing and ironing out any final bugs.

Per the original blog post, "If user feedback reveals only small and easy to fix bugs, we will solve those problems and issue the result as GIMP 3.0. However, [...] If larger bugs and regressions are uncovered that require more substantial code changes, we may need to publish a second release candidate for further testing."

For those who have been using GIMP for a long while or have been aware of it, it may be a shock to hear that GIMP took this long to make it to 3.0. But as open source software and by far the most popular free image editing software available on the market, GIMP has had literal decades of iteration from dozens if not hundreds of open source software contributors.

Following the history of stable releases, GIMP has been on GIMP 2.0 or some iteration since 2004— then 2.4X from 2007, 2.6X in 2007, 2.8X in 2012, and has finally been on 2.10X from 2018 through to now, the final quarter of 2024. If all goes according to plan, the full stable release of GIMP will be GIMP 3.0 either by the end of this year or early 2025. Overall, the original version of GIMP lasted from '95 through 2003, marking 8 years for GIMP 1 and a whopping 20 years for GIMP 2.

So, what has changed with the debut of GIMP 3? The new interface is still quite recognizable to classic GIMP users but has been considerably smoothed out and is far more scalable to high-resolution displays than it used to be. Several familiar icons have been carefully converted to SVGs or Scalable Vector Graphics, enabling supremely high-quality, scalable assets.

While PNGs, or Portable Network Graphics, are also known to be high-quality due to their lack of compression, they are still suboptimal compared to SVGs when SVGs are applicable. The work of converting GIMP's tool icons to SVG is still in progress per the original blog post, but it's good that developer Denis Rangelov has already started on the work.

Many aspects of the GIMP 3.0 update are almost wholly on the backend for ensuring project and plugin compatibility with past projects made with previous versions of GIMP. To summarize: a public GIMP API is being stabilized to make it easier to port GIMP 2.10-based plugins and scripts to GIMP 3.0. Several bugs related to color accuracy have been fixed to improve color management while still maintaining compatibility with past GIMP projects.

https://www.ebay.com/itm/205096866764

!linuxchads do u think this can run NetBSD

Another one: https://deadsimpletech.com/blog/women_in_tech

Xhe self-posted these to Orange Site and they got flagged to death and I can't find anyone else who reads them, even on Mastodon

Maybe we can be xer friends?