Muddybulldog

Mixed feelings on this. Cool tool, great idea. On the other hand, it’s also an effective tracker. Not privacy friendly.

Disabling IPv4 isn’t going to do anything to move IPv6 forward. You’re just shutting those who remain limited to IPv4 through no fault of their own.

Beauty of FOSS is anybody can just remove it.

Funny thing being that the only reason SONY is in gaming was to screw Nintendo. They had a hardware partnership that fell apart because SONY was putting the thumbscrews to Nintendo over revenue sharing. Nintendo said, you’re not the only one who can provide what we need, and dumped them. PlayStation was the direct result.

In addition to the reasons already mentioned, Apple has a requirement that applications have a novel component. While it’s often questionable as to what is considered “novel” Weather applications get contrasted against the built-in weather app. If the app simply duplicates the functionality it will be rejected.

BC titles remain available through the current store.

True dat. I’ve been running it about seven weeks and am pulling about 700 communities. Most have near zero traffic but the high volume ones do add up.

42G	/mnt/sp4dot1-data/appdata/mylemmy.win/
12G	/mnt/sp4dot1-data/appdata/mylemmy.win/postgres
30G	/mnt/sp4dot1-data/appdata/mylemmy.win/pictrs

I use Lemmy Community Seeder. Every four hours it checks the top posts on instances you specifies and automatically subscribes you to communities that appear there but you aren’t already subscribed to. You can tweak it to ignore specific communities or instances.

Federation is enabled by default. Defedersting takes explicit action…

Indeed. !test@mylemmy.win is my community for, well, testing. It has 63 subscribers. One is me, the rest are bots that managed to find the community.

Battlestar Galactica, The Twilight Zone, The Outer Limits; just to name a few successful TV reboots (and some, accompanying films) of the same name.

The original Star Trek and SNW have more in common, quality and continuity than any two seasons of ST:Discovery.

It’s worthy of the name, in my opinion.

Biggest issue I have with this edition is the Strange New Worlds tag.

Should be just… Star Trek.

A true descendant of the show I grew up with.

It’s no win scenario for developers. While you’re ok with “one up front payment and then maybe in app purchases to pay for new features going forward” there’s a whole other slew of voices who are going to complain about being nickled and dimed.

Given those choices (and other factors), as a consumer I prefer the subscription model. If nothing else, it lets me forecast my expenditure and continually re-assess the cost/value proposition of the application in question.

We’ve got nobody to blame but ourselves for that.

I’m of the mind that the truth already is noise and has been for a long, long time. AI isn’t introducing anything new, it’s just enabling faster creation of agenda-driven content. Most people already can’t identify the AI generated content that’s been spewing forth in years past. Most people aren’t looking for quality content, they looking for bias-affirming content. The overall quality is irrelevant.

I can see wanting to run your own DNS to serve personal clients for privacy purposes but for self-hosting class stuff I can think of plenty of downsides and zero upsides to privatizing this.

Definitely a “yeah, you could” vs. “yeah, you should” situation.

Strange New Worlds episodic nature makes it easy to just drop right in. Technically it starts in Discovery but I think you’ll be just fine without it.

If they dropped the SNW and just called it Star Trek, I’d be okay with that. It’s deserving of the name.

Somewhat of a loaded question but, if we need to scroll through their comment history meticulously to separate real from bot, does it really matter at that point?

SPAM is SPAM and we’re all in agreement that we don’t want bots junking up the communities with low effort content. However if they reach the point that it takes real effort to ferret them out they must be successfully driving some sort of engagement.

I’m not positive that’s a bad thing.

I’m thinking you could care less.

Looks fine here, here and here so it’s likely not a problem on your side but problems with specific instances. Making a new change to your profile should forward the changes to other instances that may have missed the previous changes. That may be enough to jiggle the handle on the ones that don’t have the current information.