db0

joined 1 year ago
MODERATOR OF
[–] db0@lemmy.dbzer0.com 3 points 1 day ago* (last edited 1 day ago)

This approach was developed precicely for threaded fediverse. The initial use-case was protecting my own lemmy from CSAM! Check out fedi-safety and pictrs-safety

[–] db0@lemmy.dbzer0.com 2 points 1 day ago (2 children)

Ye, a normal VPS would be too slow for production use, as a GPU is recommended. But you can plug in any home PC to do it without risks

[–] db0@lemmy.dbzer0.com 4 points 1 day ago (4 children)

IFTAS is already working with Thorn towards this goal. But you already have access to such technology through my toolset.

[–] db0@lemmy.dbzer0.com 7 points 1 day ago

haha, nah people reported some unexpected censors, and we investigated what part of their prompt might be causing it.

[–] db0@lemmy.dbzer0.com 2 points 1 day ago

Image processing libraries are used at the forefront of almost all web services, including lemmy and are extraordinarily robust. I really don't have the time to go at this in depth, but if you are familiar with this stuff you will know how extraordinary such an exploit would be and its existence would be causing massive chaos all over the world.

[–] db0@lemmy.dbzer0.com 37 points 2 days ago (2 children)

I fully expect companies would switch to releasing some bullshit and call the DLC released.

[–] db0@lemmy.dbzer0.com 42 points 2 days ago* (last edited 2 days ago) (2 children)

It's the earliest AI technology striving to expose unreported CSAM at scale.

horde-safety has been out for a year now. Just saying... It's not a trained AI model in this way, but it's still using Neural Networks (i.e. "AI Technology")

[–] db0@lemmy.dbzer0.com 2 points 3 days ago (1 children)

I'm always hacking at something. It's just different priorities

[–] db0@lemmy.dbzer0.com 3 points 3 days ago (3 children)

Sadly, I don't have enough time for that atm.

[–] db0@lemmy.dbzer0.com 4 points 3 days ago

And my point is that you don't know how dangerous a concussion is going to be without monitoring which is why every concussion needs to be taken seriously!

[–] db0@lemmy.dbzer0.com 3 points 3 days ago (2 children)

Yes, which is why any such injury must be taken seriously (and most medics do so), which is my point.

[–] db0@lemmy.dbzer0.com 2 points 3 days ago

While true, Hollywood has done almost irreparable damage to this effect, so maybe some extra scare won't be too bad.

 

cross-posted from: https://lemmy.dbzer0.com/post/28930199

A bit of an effortpost :)

Please do crosspost in more fitting communities if you think of any

 

A bit of an effortpost :)

Please do crosspost in more fitting communities if you think of any

 

cross-posted from: https://lemmy.dbzer0.com/post/28379114

Taken from microblogging

Some extracts:

Stunningly, Automattic’s CEO Matthew Mullenweg threatened that if WP Engine did not agree to pay Automattic – his for-profit entity – a very large sum of money before his September 20th keynote address at the WordCamp US Convention, he was going to embark on a self-described “scorched earth nuclear approach” toward WP Engine within the WordPress community and beyond. When his outrageous financial demands were not met, Mr. Mullenweg carried out his threats by making repeated false claims disparaging WP Engine to its employees, its customers, and the world. Mr. Mullenweg has carried out this wrongful campaign against WP Engine in multiple outlets, including via his keynote address, across several public platforms like X,YouTube, and even on the Wordpress.org site, and through the WordPress Admin panel for all WordPress users, including directly targeting WP Engine customers in their own private WordPress instances used to run their online businesses

During calls on September 17th and 19th, for instance, Automattic CFO Mark Davies told a WP Engine board member that Automattic would “go to war” if WP Engine did not agree to pay its competitor Automattic a significant percentage of its gross revenues – tens of millions of dollars in fact – on an ongoing basis. Mr. Davies suggested the payment ostensibly would be for a “license” to use certain trademarks like WordPress, even though WP Engine needs no such license. WP Engine’s uses of those marks to describe its services – as all companies in this space do – are fair uses under settled trademark law and consistent with WordPress’ own guidelines. Automattic’s CFO insisted that WP Engine provide its response to this demand immediately and later, on the day of the keynote, followed up with an email reiterating a claimed need for WP Engine to concede to the demands “before Matt makes his WCUS keynote at 3:45 p.m. PDT today.”

In parallel and throughout September 19 and 20, Mr. Mullenweg embarked on a series of harassing text messages and calls to WP Engine’s board member and also its CEO, threatening that if WP Engine did not agree to pay up prior to the start of Mr. Mullenweg’s livestreamed keynote address at 3:45pm on September 20, he would go “nuclear” on WP Engine, including by smearing its name, disparaging its directors and corporate officers, and banning WP Engine from WordPress community events.

They... they have text message captures. In the pdf. Matt Mullenweg was trying to extort them ... by text messages. They seem to have the entire thing in the writting.

In the final minutes leading up to his keynote address, Mr. Mullenweg sent one last missive: a photo of the WordCamp audience waiting to hear his speech, with the message that he could shift gears and turn his talk into “just a Q&A” if WP Engine agreed to pay up

They finish requesting Automattic to "preserve, and not destroy, any and all documents or information in their possession, custody, or control that may be relevant to any dispute between WP Engine and Automattic". They are going to war, big time.

All this crap is just because they refuse to pay his protection money. And the guy has been stupid enough to put everything in writting.

 

I wrote this a long time ago, but I think it's still pertinent

 
 

All the principled pirates have jumped ship to lemmy so it was bound to happen sooner than later.

view more: next ›