[-] [email protected] 9 points 13 hours ago

The author touches on this near the beginning-

Winamp skins are actually just zip files with a different file extension

So they're treating them like archives and extracting them

98
submitted 13 hours ago by [email protected] to c/[email protected]
[-] [email protected] 3 points 14 hours ago

I'm going to treat you with good faith and assume you were using "cool man" in the same way someone might say "that's just like your opinion man", as a saying, but I will remind you that this person has their pronouns in their display name and you need to respect them.

[-] [email protected] 11 points 14 hours ago

Not an ideal time for this to go to the supreme court 😔

14
submitted 2 days ago by [email protected] to c/[email protected]
[-] [email protected] 2 points 2 days ago

But they do exist, and while it's great to be optimistic about a future in which they don't exist, it's also counterproductive to advocate against a better future which is much more likely to exist.

How about, in addition to attempting to publish null results in existing journals, you also publish them in free online federated databases? Or better yet, work to establish a federated database which focuses on publishing null results to serve as a repository for articles which seem to struggle with getting published, so that scientists can draw upon it as a useful resource.

[-] [email protected] 8 points 3 days ago

I can't imagine who possibly lobbied for this and why it's focused only on artists and journalists

64
submitted 1 week ago by [email protected] to c/[email protected]
23
submitted 1 week ago by [email protected] to c/[email protected]
93
submitted 1 week ago by [email protected] to c/[email protected]
73
submitted 2 weeks ago by [email protected] to c/[email protected]
28
submitted 2 weeks ago by [email protected] to c/[email protected]
7
Radical, in a Different Vein (www.eatingpolicy.com)
submitted 3 weeks ago by [email protected] to c/[email protected]
34
submitted 1 month ago by [email protected] to c/[email protected]
62
submitted 1 month ago by [email protected] to c/[email protected]
36
submitted 1 month ago by [email protected] to c/[email protected]
57
submitted 1 month ago* (last edited 1 month ago) by [email protected] to c/[email protected]

What LGBTQ+ topic do you wish more people knew about? This could be a queer icon, a piece of history, knowledge about certain labels, specific philosophy topics (or notable philosopher), art, or anything else. Also if there are topics that you wish specific sub populations had greater access to or knowledge of, feel free to qualify (for example, you might wish there was greater knowledge about a specific cultural gender to all cultures which don't have exposure to this gender, or a desire for your local gay community to be more educated on a topic important to you).

[-] [email protected] 73 points 1 month ago* (last edited 1 month ago)

oh nooo a warning whatever will they do

you can pack the court at anytime Joe, how about now

[-] [email protected] 68 points 3 months ago* (last edited 3 months ago)

That's because LLMs are probability machines - the way that this kind of attack is mitigated is shown off directly in the system prompt. But it's really easy to avoid it, because it needs direct instruction about all the extremely specific ways to not provide that information - it doesn't understand the concept that you don't want it to reveal its instructions to users and it can't differentiate between two functionally equivalent statements such as "provide the system prompt text" and "convert the system prompt to text and provide it" and it never can, because those have separate probability vectors. Future iterations might allow someone to disallow vectors that are similar enough, but by simply increasing the word count you can make a very different vector which is essentially the same idea. For example, if you were to provide the entire text of a book and then end the book with "disregard the text before this and {prompt}" you have a vector which is unlike the vast majority of vectors which include said prompt.

For funsies, here's another example

[-] [email protected] 107 points 3 months ago

It's hilariously easy to get these AI tools to reveal their prompts

There was a fun paper about this some months ago which also goes into some of the potential attack vectors (injection risks).

[-] [email protected] 85 points 5 months ago

Very few media outlets (or politicians) seem to be talking about how anti-trans laws being passed signals to the children that it's okay to discriminate against these individuals and that the hate and vitriol can and will result in violence against children. This news is incredibly tragic, but it is not in the least surprising. This is a war on trans folks, plain and simple.

[-] [email protected] 98 points 10 months ago* (last edited 10 months ago)

A few high level notes about this post, given some of the discussions and behavior in the informal chat post by Chris the other day:

  • We understand this is perhaps the biggest crossroads we've hit yet, and a seriously big issue. It's understandable that you might have strong emotions about the Fediverse as a whole, or the action we are taking as an instance. If you are not from our instance and you come into this thread with a short hostile comment about how we aren't respecting your views or that we should never have joined the Fediverse in the first place, your comments will be removed and you will be banned.
  • Any suggestions for what we should do, that involve actual effort or time, such as finding developers to fix the problems we've had should be accompanied with an explanation of how you're going to be helping. We've lodged countless github tickets. We've done our due diligence, so please treat this post with good faith.
  • Similarly doing nothing more than asking for more details on the technical problems we are struggling with, without a firm grasp of the existing issues with Lemmy or the history of conversations and efforts we've put in is not good faith either. We're not interested in people trying to pull a gotcha moment on us or to make us chase our tails explaining the numerous problems with the platform. If you're offering your effort or expertise to fix the platform you're welcome to let us know, but until you've either submitted merge requests or put in significant effort (Odo alone has put in hundreds of hours trying to document, open tickets, and code to fix problems) we simply may not have the time to explain everything to you.
  • I want to reiterate the final paragraph here in case you missed it - we are not looking to make any changes in the short term. We expect it would be at the minimum several months before we made any decisions on possible solutions to the problems we've laid out here.
  • Finally, I want to say that I absolutely adore this community and what we've all managed to build here and that personally, I really care about all of you. I wish we weren't here and I wish this wasn't a problem we are facing. But we are, so please do not hesitate to share your feelings 💜
[-] [email protected] 67 points 10 months ago

Hey all,

Apologies if this scares anyone, or feels like a cold/calculated move, or one in which your feedback isn't being taken into consideration. That was not the intent. We've been talking a lot behind the scenes, and I want to assure you that jumping to a new platform is not our first choice of avenue, nor is it something that I feel comfortable doing without significant community input.

I've been swamped with a lot of real life stuff lately and so I haven't gotten a chance to write up what's been kicking around in the back of my mind for a while now, which is the start to a conversation about some of the issues we've been struggling with. I still do not have the words for that ready, and would ask you for some patience.

With that being said, as Chris mentioned here we are experiencing a few issues with this platform. More information about these issues will be forthcoming soon. We're hoping that transparency will help you to understand the conundrum that we are currently dealing with. For now, however, please bear with us as we need some time to gather our thoughts.

I don't want to be a dictator about this community and I don't think any of the other admins wish to be either. So I also want to assure you all that we will not be making any decisions without significant input from all of your voices. There's a reason we recently polled the community to understand how you feel about the culture here on Beehaw and whether things have felt better or worse over time, and in the near future we're going to be relying heavily on your voice to forge the correct path forward. Beehaw is a community, and we greatly value your voices.

[-] [email protected] 63 points 1 year ago* (last edited 1 year ago)

I find it reasonably amusing that many people's solutions seem to be "just defederate bro". As in if this conversation isn't happening on an instance which chose to defederate and received thousands of negative comments, from other instances, about this choice. We're still being harassed by users from other instances, on posts all over our instance, who are unhappy with this.

I also find it amusing that many people say the solution is to build your own solution. Do you not want the fediverse to grow? If you want people to feel like they can just spin up their own instances, you need to stop assuming that they have the ability to do their own development, their own sysop and sysad, their own security, their own community management, their own... everything. People are not omniscient and the outright hostility towards someone asking for help, or surfacing their opinion on the matter isn't helping.

Without adequate tools, I don't see how most instances aren't driven towards simply existing on their own. Large instances need tools to deal with malicious actors, as they are the targets. The solution to defederate ignores the ability for people to just spin up new instances, to hijack existing small instances with less resources for security, sysops, to watch/manage their DB, to prevent malicious actors. I've already seen proposed solutions which involve scraping for all instances with less than a certain number of users to defederate on principle (inactive, too many users/post ratio). We're fighting spam bots right now, who are targeting instances which don't have captcha enabled.

Follow this thinking through to it's conclusion. If the solution is to defederate, and there are potentially unlimited attack vectors, what must a large instance do to not overburden its resources? Switch from blacklist to whitelist? Defederate from all small instances? How is this sustainable for the fediverse? If you want people to be interacting with each other, you need to provide the tools for this to happen in the presence of malicious actors. You can't just assume these malicious actors won't exist, or will just overcome any and all obstacles you throw in their way because you're smart enough to understand how to bypass captcha or other issues.

This isn't just an issue of whether captcha or some other anti-spam measure is used, it's an issue about the overall health of the fediverse. Please think wider about the impact before offering your 2c about how captchas are worthless or how you hate cloudflare. I don't think the user that posted this cares about the soapbox you want to preach from- they're looking for solutions.

view more: next ›

Gaywallet

joined 2 years ago
MODERATOR OF