668 karma · joined May 21, 2019
Find me as Vega Deftwing on most sites
OwO
It's SCANOSS's fork.
> which could potentially go against GitHub’s rules
Not potentially, it does.
> we use the purl2cpe repository daily
Great, but not this fork. This fork is from SCANOSS, and I chose a repo which hard cursing (albeit due a dependency) to make my point of their hypocrisy.
> challenge those who think that knowing how to use ChatGPT makes them programmers
You really ought to look at who has commented in that thread, from well known cryptographers to other business owners. Attacking the people, rather than discussing the topic at hand, won't get us anywhere. I have not once accused SCANOSS of being bad programmers, bad at their job, etc. because, frankly, they're probably not. It's, seemingly, a successful business with reasonable development procedures. It's just that it seems they're in desperate need of ethics and PR knowledge.
> meaning anyone could easily impersonate someone else.
Interesting, from another account made just now, to be the only other defending SCANOSS. I don't think anybody impersonated Quique, because unlike SCANOSS, nobody - that I've talked to at least - is coming from a place of malice. We simply want an apology and acknowledgment wrong was done.
---
Honestly, this entire comment was confusing, and written in a style that makes me suspect of it's legitimacy, as ironic as that is.
Oh, quique.goni@scanoss.com exists. HM. I wonder if maybe you might have some bias in this?
What CoC did we violate, by the way? You're the ones who came into my repo with a bot and used a bot to tell me not to swear. Which, again, is a violation of GH TOS.
I have not falsified information, impersonated anyone, or extorted anyone. If I have, I welcome you to show it. Make a blog post, post it here, whatever.
Hell, sue me. I've emailed you guys with my personal email a few times and offered to call on Zoom or with phone.
As for "or their guardians" I'm an adult, though given you're pretending not be associated with your employer I'm questioning if anyone at ScanOSS is.
Those are
---
Oh! Looks like I still had my response to your bot open, so here was my raw, unfiltered, and (Oh no!) vulgar original thoughts, before I toned it down to comment here:
@scanoss
OOPS! Did I swear in my own repo? My bad.
Cursing, and how the open source community represents itself, are - and I can not stress this enough - not a business-polite thing. You're welcome to fork (Within my license terms) and remove them, but given part of open source and a healthy hacker ethos is the counter-culture vibe that made the technology I'm sure even you yourselves use possible, you can
[in fancy unicode text, unsensored] Go F* yourselves
What you're doing is not helpful to the OSS community, it's helpful to your business partners that profit off open source, and given the trend in industry, do so typically without giving back. You want to do something meaningful? Drop a recurring sponsorship of my website so I can take more time to write guides and cool things using whatever language I choose to best convey my intent and feelings.
That project was https://github.com/VegaDeftwing/opinionatedguide in case you interested in fucking sponsoring me <3 I would really fucking appreciate it!
--- and ---
Hey @agustingroh it looks like you're the most frequent committer on SCANOSS repos, thought I'd nudge this to get some attention brought to it. Still awaiting an apology myself, though at this point needing to ask for it makes it rather moot personally, it would still be nice for everyone else SCANOSS spam'd.
---
How they decided that second one is "abuse" is beyond me, but as you can see, while a bit less vulgar, I was, indeed, pissed off.
Those licenses let me say "This is open to the individual and small business, but not a mega corp" without actually needing to define a hard cut off.
Besides, it's not like most developers of FOSS software that use these have the time/money/energy to bother to sue over infringement anyway, so practically this is their main purpose.
1. Compensated for on call time 2. Be paid for overtime (No "You're salaried so we expect 45+") 3. Have the right, as an employee, to not respond when not explicitly on call without fear of retaliation.
1 + 3 require better changes to employer decimation law. As is, even if you know you were fired for unjust reasons, it's VERY hard to win a lawsuit as an employee.
I absolutely, passionately hate Bluetooth. I hate not being able to share the jack in the car. I hate spotty connections. I hate needing a dongle. I hate the subtle loss of high end frequency content's quality. I hate the pain in the ass of pairing. 3.5mm had its share of problems, but this was a cartel making a cash grab and I am absolutely livid I have to play the game.
I've ran a poll in a lot of the tech group chat's I'm in multiple times. Over 40%, each time, is willing to pay $50 more to have the jack back. The manufactures know this, but know it pales in comparison to the profit of some new bluetooth headphones.
We don't need monoplolies to negatively impact tech, just a few big players to intentionally normalize boning their own customers. We need consumer protection laws that reflect that normal.
We don't want kids looking at certain Hub sites, obviously, but, like, those same filters also often prevent high schoolers from looking up necessary safe-sex information.
As a music app, that's less of a concern, but I do think there's risk of parents over-controlling to only provide, say, conservative podcast audio and Christian music. Weather or not that's a parent's right also depends on the age. 4, like your daughter. Sure. What about 12? 16? 17? Age of majority in Nebraska, where I'm located, is 19. Should a parent be able to restrict their child from listening to, say, NOFX, Flobots, or The Narcissist Cookbook, at 18?
I lean no. Now, you're not the moral police and, arguably, it's not up to you if parents abuse this app against their more-adult-kids wishes, but have you put any thought into this? Have you made an effort to only target parents with kids of an age range or to put a "What should I let my kids listen to?" guidance section in the app?
I'd also like to ask if the app is obviously branded as for kids to kids, so that those "kids" or maybe some highly sheltered romantic partner, can take it as a hint?
---
> Exiting the audio player mode requires the password set by the parents
How does this work? I'm an Android guy, but over there, to my knowledge, there's no good way to tell the OS "Users shouldn't be able to kill this app", so how does it stop kids from closing it/switching apps?
There are some options, of course, but they're limited and often of poor quality, at least locally. Libraries are trying to adapt to fill this gap, and maker spaces spring up but most don't have funding to be good - or if they do, that funding brings things that ruin the spirit. Once you're looking for a place as an Adult, especially without kids, the number of relevant events and things to do drops quickly too - so these same children aren't going to find better options as they grow older.
I'm mostly an embedded guy (Usually much lower power ST parts), so it's neat to hear about how you approached it. Having multiple chips separate so can't underrun as easily if the UI needs to react is really nice design!
I see a lot of your engine is modified from from Mutable Instruments, but you do have a good selection of original sound sources as well. What sets yours apart? Did you have a strong background in DSP before Aodyo?
What do you see as setting your synths and hardware apart from, say, the Osmose and Hydrasynth?
If you don't mind me asking, for your hardware, what's running under the hood? Big ARM cores / SOC? RTOS on a Cortex-M? What challenges have you faced working on whichever you're less used to? (The VST if you have more hardware background, the hardware if you have more desktop software background)
> Can you explain more about the response and impedance of each? I am an engineer, so you can feel free to be quite technical.
---
>Certainly! Given your engineering background, let's delve deeper into the response characteristics and impedance aspects of both traditional ceramic piezo pickups and PVDF piezo pickups. Understanding these can significantly impact your choice, especially in terms of how they integrate with the rest of your audio chain (like preamps and amplifiers).
>
> Electrical Characteristics
> 1.
> Piezoelectric Coefficient
> Ceramic Piezo Pickups: The piezoelectric coefficient ( d_{33} ) of ceramics like Lead Zirconate Titanate (PZT) is typically very high. This coefficient measures the electric displacement produced per unit stress. For PZTs, ( d_{33} ) can range from 100 to 600 pC/N (picoCoulombs per Newton), depending on the formulation and orientation of the crystal structure.
> PVDF Pickups: PVDF generally has a lower piezoelectric coefficient, around 20 to 30 pC/N. Despite this lower coefficient, the material's flexibility and the ability to form larger, more adaptive surfaces can compensate in practical applications, offering sufficient voltage output under less stringent mechanical deformations.
> 2.
> Voltage Output
> The output voltage ( V ) from a piezo pickup can be estimated by the formula:
> [ V = d_{33} \cdot F \cdot A / t ]
> where:
> ( F ) is the force applied,
> ( A ) is the area,
> ( t ) is the thickness of the piezo material.
> Ceramic Piezo: Due to their high ( d_{33} ) value, even small deformations can produce relatively high voltages, which makes them sensitive to shock and vibrations, potentially capturing unwanted mechanical noises.
> PVDF Pickups: The lower ( d_{33} ) value means lower voltage outputs for the same mechanical stress compared to ceramics, but their larger possible surface area and thinner construction can enhance output levels and fidelity across a broader frequency range.
>
> [SNIP]
I mean, don't get me wrong, I still think Behringer as a company is doing bad things to the music land scape and that they've done some pretty horrendous IP theft and racist stuff, but I don't think "because you're poor" is right either.
To the point though, yeah, no, TE absolutely won't get a black eye for this: Nobody cares, and hardly anyone but tech bros even know. It's no worse than their wooden choir thing.
I know I personally have sought out better copies of some songs because the high end sounds awful, witch each hi-hat splash being a crinkly-codec failure.