copygirl @ copygirl @lemmy.blahaj.zone

Just a dorky trans woman on the internet.

---

Read more

Posts

30

Comments

213

Joined

2 yr. ago

Selhosting and a vpn are optional depending on your use case; the app works with niether to help users try it out and get started. Like all secure messaging apps, its better to selfhost given the option.

I'd say self-hosting is done for control over your data, not security. A typical end user will not know how to self-host, how to pick a privacy-respecting VPN, let alone secure their system. If your aim is to get to that same level of security, then I feel like the current direction is flawed, at least from what I took away from the readme.

Or, in other words, "self-hosting is more secure given the option" sounds kind of like "writing your own software is more secure".

This project is aiming to create the most secure and private chat app. It will heavily depend on how you use it. Here are some reccomended security optimizations/advice to keep your data secure and private:

• Use a self-hosted instance of the app.
• Use a VPN to protect your data from being intercepted.
• Only connect to trusted peers.
• Validate public key hashes.
• You and your peer should use a secure device/os/browser with the latest updates.
• use general security practices like not sharing sensitive information, not clicking on suspicious links, etc.

These recommendations are bizarre.

• Is it really P2P if you need to a host your own instance?
• Use a VPN? So a company can now track you instead of the ISP?
• If it's aiming to be safe, then why not share sensitive information?

If you want secure and private, then I would first look at Session.

And of course, that response cost you one wish credit.

I'm unsure why it changed since you moved to a server, but the config file config/waystones-common.toml has a bunch of settings for balancing / restricting waystones, like for example making naturally spawned waystones unbreakable.

My chosen name, Tess, was literally picked from a variable name from de-obfuscated Minecraft code over a decade ago. It said Tesselator tess = ... or something like that. And I thought "that sounds neat". Some time after, I found out it's also a real name used by real people in the real world.

To explain: The world you spawn in in Compression is not the Overworld. It's a trashdump between dimensions, which is why everything is broken, and why beds explode on use, as they would in the Nether or End. (Yes, it also got me when I was trying to sleep in a villager's bed, not thinking hard enough.)

Discord also works poorer in Linux

Certainly not Linux' fault if developers write shitty Electron apps and then put a bunch of OS-specific stuff in it.

Also, try Vesktop? I like that I can customize my experience a little more with the plugins.

Snap

All my homies hate Snap.

Haven't watched the video, but I think just the conversation this created ended up being interesting to me. A handful of extra views won't do any harm.

color_rect.set_instance_shader_parameter should work, as long as the color_rect is unique to each instance of the card, rather than being reused. If you assigned it in the node editor you could check the "Local To Scene" checkbox. Assuming cards are defined as separate scenes you instantiate. Otherwise you could duplicate() the resource in code.

The same would be true for color_rect.material.set_shader_parameter for the ShaderMaterial. If you could ensure it's unique per card, it should work. However, duplicating the material might not be as ideal, especially since the other option is also available.

A little tip: You could try print debugging with the get functions before and after you use set to see what the value was before (and notice that it might be the same as the previous set call from another card) and that it was correctly set afterwards. (Assuming I'm correct about diagnosing the problem.)

edit: Actually, my advice is only true if color_rect was a resource, but I think it's a node, specifically a sub-class of CanvasItem or GeometryInstance3D, so it should already be unique for each instantiated card. So without more information I'm not sure why set_instance_shader_parameter is not working.

Tangentially related: Oh boi I just love AI bros coming out of nowhere defending GenAI when nobody asked for their opinion. Wish more communities / instances would take a hard anti-AI stance and just get rid of them. It's not like anyone will make them see where they're wrong.

You see, it's not the internet censorship tool that prevents you from speaking your mind, it's the people that control it!

You can dislike the tool.

AI was built on stolen work, and will not create a generation of future artists that simply has a new tool available. It'll create a generation of workers that create profit for the wealthy class by generating garbage until it's somewhat presentable. Meanwhile, AI will starve out because it will run out of data to learn from.

Generative AI is the current fad of the tech bro world and it's what everyone clings onto because if everything goes well (for them), they can get future generations hooked and make stupid money. Meanwhile, media literacy will further decline, and with it the ability to look up anything on the internet, making it even more easy for the masses to be controlled.

Perhaps after having familiarized with GDScript, learning C# with the same game engine and API is also an interesting way to learn another programming language. There's also extensions for other languages, like Rust.

most of the the Arch cult forget to mention that

The "Arch cult's" holy book, the ArchWiki, states the following pretty clearly:

Warning: AUR packages are user-produced content. These PKGBUILDs are completely unofficial and have not been thoroughly vetted. Any use of the provided files is at your own risk.

Mention of one's use of the AUR for their needs doesn't need to come with a disclaimer.
People who don't read or don't use their brain are going to keep not doing so, regardless.

To add to what you're saying: To be fair, most of the lawsuit I don't really agree with, but maybe it's just laying it on thick.

Part of the argument is them trying to separate the Steam "Store" from the Steam "Gaming Platform", and in many ways that's obviously not possible. But they say that because of Steam's monopolistic-ish position, publishers can't not be on the "gaming platform", because it's where most people want their games, or else they'll lose out of a large chunk of money. (And without it, these games likely would not be made in the first place.) Thus Steam can force these unfair terms on developers.

There was also this portion on discounts that was quite revealing:

20. For example, Valve has set up visibility in its Steam Store to focus on games that are nominally “on sale” to gamers. Knowing that the best way to reach their audience is through discounting, game publishers must artificially inflate their list prices so they have headroom for discounting. But the “sale” price is not consistently available, and therefore some gamers pay an artificially inflated list price for the game. These supracompetitive prices increase Valve’s cut, force gamers to overpay, and prevent publishers from setting the most efficient game prices they could in the first place. Even worse, these supracompetitive prices are transmitted across the broader market by the contractual restraints discussed above.

They're admitting to inflating games' prices, so they can then offer a fake discount that's closer to the actual price they actually wanted the game to be. And then they complain when Valve doesn't let them list a game on sale for an extended period of time, just so they can essentially scam people. (Probably, once again, standard in the industry and elsewhere, but I feel like that's gotta be banned by EU pro-consumer laws.)

The EU can and should force Steam to get rid of the MFN clause. All Valve needs to do is to let competing stores price games cheaper than on Steam. (So long as Steam services are not involved with that off-Steam purchase.)

There's still plenty of benefits Steam provides to customers that many may choose it over a different store even if they could get the game for cheaper. And Steam also provides developers with tools that make Steam worth it, like Steam networking and cloud saves. As Gabe Newell famously said about piracy, but I believe this applies in this case too, it's simply a service problem.

And this was only mentioned in a footnote in the complaint document, though I saw it many times when browsing through the earlier lawsuit documents. Interestingly, this sounds like it should already be illegal in the EU, as per the Wikipedia link you gave.

How clear is the wording? Is it possible to find the text of the terms / agreement / contract online? Or is it covered by an NDA?

This is true! Vintage Story does it, for example. They're doing okay from what I can tell, but it's more of an exception. It's pretty clear that they are losing out on potential customers. Notably, you also lose out on regional pricing, which is pretty difficult to set up yourself. If you're creating games for a living, you don't have much of a choice about whether you put your game on Steam.

Because we are talking about someone using AI for most if not all tasks that involve thinking and/or creativity, as if it was any other tool.

First of all, it's hypothetical. If only for the fact that using a wheelchair in real-life actually greatly increases difficulty getting around. The point is that if you don't lose your muscles, they get weaker. Happens with anyone that has an accident that causes them to be unable to use their muscles for a prolonged amount of time. See also: Astronauts needing to exercise while in space or back on earth because they've not had to use many of their muscles as much due to lack of gravity.