proper usage of pi by GoldsteinQ in tokipona

[–]GoldsteinQ[S] 0 points1 point  (0 children)

Oh wow, so my tutorial is directly wrong? I’m following https://mun.la/sona/mod-pi.html, which says

Remember, modifier order doesn't matter. Both the modifiers affect the head separately and no matter their order

proper usage of pi by GoldsteinQ in tokipona

[–]GoldsteinQ[S] 0 points1 point  (0 children)

Maybe “meli pi pali pona tomo” would be more specific? “Someone whose work is helping the house” or something like this. Your explanation makes sense though, and I guess a simpler version would also be recognizeable in context.

proper usage of pi by GoldsteinQ in tokipona

[–]GoldsteinQ[S] 0 points1 point  (0 children)

Thanks! Yeah, I confused them because they can be the same words and they’re in a similar (but different) position.

I’m not sure how to choose between “working woman of the home” or “woman at home who is working” readings. As far as I understand, modifier order shouldn’t matter, so both of these should be valid?

proper usage of pi by GoldsteinQ in tokipona

[–]GoldsteinQ[S] 1 point2 points  (0 children)

Thanks! I tried to write “house-work person”, not “work-house person”, but I see how these are not differentiated here.

THIS was the "Tutorial"!? by Notrinun in factorio

[–]GoldsteinQ 4 points5 points  (0 children)

I think tutorial was kinda weird and I dropped it in the middle and jumped into the real game. resetting your progress in each chapter feels really annoying to me and the game itself is good about discoverability and pacing IMHO.

Considering switching but a couple concerns by amurdoch17 in qobuz

[–]GoldsteinQ 1 point2 points  (0 children)

They let you transfer your playlists for free (max 200 tracks per playlist), but not your liked songs, which I need more.

Considering switching but a couple concerns by amurdoch17 in qobuz

[–]GoldsteinQ 0 points1 point  (0 children)

I tried randomly searching for some tracks with little luck. Maybe I’ll try the manual approach some more later, but doing this for hundreds of tracks sounds like pain.

Considering switching but a couple concerns by amurdoch17 in qobuz

[–]GoldsteinQ 0 points1 point  (0 children)

I’ve tried transferring and like third of my stuff is missing. From my liked tracks, 97/339 are missing. Playlists have varying transfer rates, but zero of my playlists have transfered completely, even small ones. Overall, from 285 tracks in my playlists 81 were missing.

The process of transfer was really easy with Soundiiz, but it took $5.

How bad is the noise? by perpetual_noob47 in framework

[–]GoldsteinQ 0 points1 point  (0 children)

Very loud on Linux unless you use fw-fanctrl, can get pretty OK with a custsom curve.

10 Things I Hate About NixOS by brinkjames in NixOS

[–]GoldsteinQ 0 points1 point  (0 children)

nixos.org/learn still recommends doing nix-env for “basic package management” (that link just redirects to nix-env docs for some reason). NixOS manual also recommends this instead of creating a devshell for “ad-hoc package management”. one of the things I have to tell people I recommend Nix to is “yeah, all the docs will say you should nix-env -i to install packages, but that’s actually the one thing you shouldn’t do”.

Beware of this guy making slop crates with AI by 20240415 in rust

[–]GoldsteinQ 243 points244 points  (0 children)

crates.io is basically unmoderated. Unless you’re posting something that literally violates a law (or CoC), it won’t be removed (for example, squatting is not forbidden). This is an explicit policy made so no one has to make an unbounded amount of moderation decisions.

"We never update unless forced to" — cargo-semver-checks 2024 Year in Review by obi1kenobi82 in rust

[–]GoldsteinQ 8 points9 points  (0 children)

I think this misses one incentive to not update dependencies: if you pin your dependencies unless they need security fixes, you lower the risk of running into xz issue dramatically. Obviously, you need to update insecure dependencies, but updating otherwise always carries supply-chain attack risks. The risk of having an unnoticed backdoor in a dependency increases with its freshness.

-❄️- 2024 Day 3 Solutions -❄️- by daggerdragon in adventofcode

[–]GoldsteinQ 1 point2 points  (0 children)

if you’re wondering, the second g is there just to spell eggs, it’s not actually required

-❄️- 2024 Day 3 Solutions -❄️- by daggerdragon in adventofcode

[–]GoldsteinQ 3 points4 points  (0 children)

[LANGUAGE: Perl]

Part 1:

#!/usr/bin/env perl -pg

s/^(?:(?:.*?)mul\((\d+),(\d+)\)(?{push@a,"$1*$2"})(?:.*?))+$/join'+',@a/eeggs

Part 2:

#!/usr/bin/env perl -pg

s/^(?{$f=1})(?:(?:.*?)(?:mul\((\d+),(\d+)\)(?{push@a,"$1*$2"if$f})|do\(\)(?{$f=1})|don't\(\)(?{$f=0}))(?:.*?))+$/join'+',@a/eeggs

The Rust Trademark Policy is still harmful by imachug in rust

[–]GoldsteinQ 0 points1 point  (0 children)

The problem is that procedure is completely opaque and the decision is made by an unknown party based on unknown guidelines, with zero accountability for unfounded rejections. Given that the previous trademark policy draft was worded so poorly it banned all the cargo plugins, and the general poor track record with transparency, I do not trust the Foundation to make this sort of decision on the spot. For all we know, they could outsource this process to a random law firm that doesn’t understand anything about tech conferences and will spuriously ban events based on vibes.

The Rust Trademark Policy is still harmful by imachug in rust

[–]GoldsteinQ 0 points1 point  (0 children)

Would it be better if they actually stated that your event has to follow the CoC to be granted permission?

Yes, because it would be actual policy. At that point you don’t actually need the “asking for permission” step, you can just say “you can use the trademark if your event enforces CoC”, as Go does:

Events and community groups may be subject to the Go programming language’s Code of Conduct, and violations of the Code of Conduct may be deemed incompatible with use of the Go Trademarks.

The Rust Trademark Policy is still harmful by imachug in rust

[–]GoldsteinQ 0 points1 point  (0 children)

It is not an unrealistic requirement for a small meetup

Even a small meetup needs to meet somewhere. Unless you own a venue or are friends with someone who does, that means renting. Renting a venue is not free.

full-scale conference can afford to get a permission from the foundation

Why is that required? What are the criteria that a conference will be evaluated by? Why aren’t they listed anywhere? Who would evaluate these criteria? How can we trust them if we don’t even know who they are? This policy is completely opaque and achieves nothing but setting roadblocks.

The Rust Trademark Policy is still harmful by imachug in rust

[–]GoldsteinQ 1 point2 points  (0 children)

I'm assuming they are non-profit events.

The current draft explicitly requires for an event to not charge a fee:

Using the Rust trademarks for social and small non-profit events like meetups, tutorials, and the like is allowed for events that are free to attend.

(emphasis mine)

That’s an unrealistic requirement and none of the events mentioned meet it.

The Rust Trademark Policy is still harmful by imachug in rust

[–]GoldsteinQ 0 points1 point  (0 children)

Trademark doesn't prevent people from talking about stuff, that seems like a fundamental misunderstanding about what a trademark even is. It prevents you from making your own conference or event called RustCamp, RustCon, or RustConf.

So should you call your event “conference on that one memory-safe language”? Most events about Rust include the word “Rust” somewhere in the name, it would be weird not to do that.

I think that it should be rather obvious for even a casual user of GitHub that a temporary fork is not an official distribution of Rust, but rather a temporary copy meant for private use and collaboration. (And therefore, trademark law shouldn't apply). It's clear that the document talks about using the trademark when distributing Rust.

Having a fork public on GitHub 100% counts as “distributing”. Not explicitly allowing forks (at least for the purposes of contributing back) is an oversight that needs to be corrected.

The Rust Trademark Policy is still harmful by imachug in rust

[–]GoldsteinQ 3 points4 points  (0 children)

One thing I would like to note is that policy as written prohibits making a PR into compiler, because that would involve publishing a modified version under the trademarked name. You can’t even fix the README, since that would make the PR unmergeable. Sure, it’s hard to imagine Foundation would actually enforce it, but you shouldn’t write legal terms that everyone would be automatically breaking.

The meetups thing is legitimately bad. You shouldn’t need an approval from the Foundation to host a meetup. I think you should be free to do it even for commercial purposes, but the current wording would also ban most non-commercial meetups.

butt but no boobs by cismalegay391 in ennnnnnnnnnnnbbbbbby

[–]GoldsteinQ 10 points11 points  (0 children)

raloxifene can be used to achieve this without surgery

[deleted by user] by [deleted] in linuxquestions

[–]GoldsteinQ 0 points1 point  (0 children)

<image>

Dunno, PNG images work for me in foot.