zalack

NVIDIA’s marketing overhypes, but their technical papers tend to be very solid. Obviously it always pays to remain skeptical but they have a good track record in this case.

He doesn’t. White supremacists clinging to celebrities they desperately want to believe support their views only to be slapped down in disgust is a tale as old as time.

I seen to remember the documentary about her covering the decision to publicly voice her political beliefs for the first time. There’s this one scene where she’s in a room full of white men telling her not to do it because it would damage her brand and her mom being the only person in the room to support it.

She went against all her business advisors and did it anyway, which should tell you enough about where she stands.

The comment was about strategy, not objective.

It’s not that strange. A timeout occurs on several servers overnight, and maybe a bunch of Lemmy instances are all run in the same timezone, so all their admins wake up around the same time and fix it.

Well it’s a timeout, so by fixing it at the same time the admins have “synchronized” when timeouts across their servers are likely to occur again since it’s tangentially related to time. They’re likely to all fail again around the same moment.

It’s kind of similar to the thundering herd where a bunch of things getting errors will synchronize their retries in a giant herd and strain the server. It’s why good clients will add exponential backoff AND jitter (a little bit of randomness to when the retry is done, not just every x^2 seconds). That way if you have a million clients, it’s less likely that all 1,000,000 of them will attempt a retry at the extract same time, because they all got an error from your server at the same time when it failed.

Edit: looked at the ticket and it’s not exactly the kind of timeout I was thinking of.

This timeout might be caused by something that’s loosely a function of time or resources usage. If it’s resource usage, because the servers are federated, those spikes might happen across servers as everything is pushing events to subscribers. So, failure gets synchronized.

Or it could just be a coincidence. We as humans like to look for patterns in random events.

It’s because the producers want their counterparts spending time, energy, and perceived social capital negotiating over it rather than the things the Producers actually worry about having to give up.

IMO it’s pretty transparent, but creative people are pretty scared of AI right now so it might be a good bargaining tactic if they can get rank and file Union members to tie up the negotiatiors by reacting.

Crowd extensions are already pretty common with traditional VFX techniques.

I worked in Hollywood editorial for a bit and, IMO, the producers are playing up the AI stuff so that said stuff can be given to the writers and actors as a “victory” instead of the real spectres in the room:

• streaming residuals need to get the same payout and transparency as home video and syndication did

• streaming numbers need to be made available to creators to facilitate the above.

• the ‘mini-room’ system that totally disconnects writers from the productions they are writing for needs to be broken down.

I’m pretty sure that ruling specifically relied on the denial of service being an expression of religious belief, which would be a hard sell here.

(Also, not endorsing the ruling, that’s just my understanding of it).

That’s what I meant. The GUI is all that 95% of end users interact with.

Sure.

Lol. Brain fart. Fixed

Folders. At least to the end-user. Under the hood it’s Unix, so it wouldn’t be wrong to call them directories either.

I’m gonna need some receipts for that one, mostly because as an end user the content quality on that sub is head and shoulders better than anywhere else on Reddit

Also, like, that kinda weird shit is going to happen occasionally anywhere there are power heiarchies. It sucks when it happens to you, but it’s unavoidable when a group of humans is given a set of rules to enforce.

AskHistorians may be my favorite corner of the Internet ever. What a great sub and mod team.

I posted a version of this in another thread:

I really think Lemmy, Kbin, and Mastodon need to figure out a way to have a default terms of service that ships with their product which forbids using the API to collect data for anything outside of user-facing social network interfaces, including account association heuristics and similar processes.

A way for users to set licenses on individual posts would be huge as well, with a default license instance admins can set.

That way for-profit instances could be forced to filter out posts with licenses that do not allow for-profit use. Honestly, even just a simple check mark “[ ] allow for-profit republication”, and have two licenses that can be attached: one that allows for-profit use and one that does not.

The fediverse should start baking in data control into it’s legal framework. Want to federate with Mastodon? You need to follow the ToS for what you can do with its posts. If we wanted to get really extreme we could even say the license should be copy-left. Any instance that wants to federate with a non-profit instances needs to also be non-profit.

That could block for-profit companies from becoming part of the network in the first place, even by use of stealth relay instances.

#threads

I really think Lemmy, Kbin, and Mastodon need to figure out a way to have a default terms of service that ship with their product which forbids using the API to collect data for commercial purposes.

Additionally, there should be a way for users to indicate licensing for individual posts, with a default license instance admins can set.

That way for-profit instances could be forced to filter out posts with licenses that do not allow for-profit use. Honestly, even just a simple check mark “[ ] allow for-profit republication”, and have two licenses that can be attached: one that allows for-profit use and one that does not.

Kbin generally seems to churn faster than Reddit for me, but posts on Lemmy do seem to stay around for a awhile.

I think it would be interesting to explore an API affordance for attaching licenses to fediverse content, with the admins being able to set a default license for their server.

So if Meta wants to get content from the fediverse, it has to check the headers of each post and make sure it’s licensed for commercial use.

The thing is that this can happen even without active malice.

If the product owners or engineers decide “hey, we want to add this cool feature, but it’s not supported by activity pub” the path of least resistance – bypassing the long process of changing the activity pub spec and getting everyone else on board – can be super tempting, and come from a place of wanting to make your product better.

Those ostensibly good intentions can lead to E/E/E without actively meaning to.

Thems the breaks when using what is essentially alpha software. The devs of both Lemmy and Kbin are aware that the admin tools need work, but stuff takes time.

Even if it’s just as a username? How would Google even know about that?

I’m not saying “sign in with Google” sign ins. Just that I use that email address as a username in a couple places