bramhaag
Here's a summary:
- The project is licensed under the "Corridor Key License" [1], which is CC BY-NC-SA 4.0 with extra clauses that permit commercial use of you have their blessing (That's right, CC BY-NC with commercial use allowed).
- CC licenses should not be used for software, and the non-commercial restrictions make this project not open source.
- This project is based on Hiera, which licenses its weights under CC BY-NC 4.0 [2]. Again, non-commercial. He is selling this.
- The license was changed a few times after the community rewrote large parts of this project. The contributors should've retained their copyright to their contributed code as there was no CLA or similar, but to my knowledge their code was relicensed without their consent.
[0] https://github.com/nikopueringer/CorridorKey/issues?q=licens...
[1] https://github.com/nikopueringer/CorridorKey/blob/main/LICEN...
If there was a grain of truth to this claim, surely someone would've stolen the prize by now? Thousands of people would've had a working POC if it was this easy.
There are zero good private trackers that you can pay for to enter. Buying invites will get you banned, and paying the site directly is only possible on scummy trackers.
There is a lot of good information here [0]. Most notably RED is open via interviews conducted on IRC, and has a big invite forum to join other trackers. But yes, they do force you to contribute through maintaining a ratio.
I'm not looking forward to when passkeys become even more forced upon us and you have to carry around multiple devices by different manufacturers because platform A and B don't support the same devices.
See e.g. https://community.openai.com/t/daybreak-does-not-recognize-t...
But the homelabbing scene, and many parts of tech in general, are generally more inclusive than many other scenes, perhaps partly because we have a very diverse community in the first place. I think it is important context, and not just a needless detraction, for a physical gathering that the organizer does not share these views.
Regardless, I do not think any interpretation of "positive community" can include the dejection of homosexuality.
The reactions about this when announced on Reddit seem to contradict that:
> I'm a little disappointed that u/geerlingguy is the one running it, since he's posted some shitty beliefs about gay people that, to my knowledge, he has never retracted or disavowed.
> So he can tell all the women there they have no right to their own body?
> Hmmm I didn't know Jeff was anti-gay and anti-women's rights.
> Hi u/geerlingguy ! Are gay people allowed to attend your event?
https://www.reddit.com/r/homelab/comments/1wq04et/im_startin...
https://www.reddit.com/r/selfhosted/comments/1wq2orh/jeff_ge...
In some ways /e/ and GOS are trying to achieve different things (/e/ is not hardened and does not claim to be), but /e/ is severely lacking security wise compared to AOSP.
This [0] is, in my opinion, a fair review that mentions many of the issues. That Fairphone is ok with these is telling about their position on privacy and security.
[0] https://www.kuketz-blog.de/e-datenschutzfreundlich-bedeutet-...
> Fairphone has said they don't plan to add a secure element. It can be seen from their current devices that they don't fully keep up with privacy/security backports and lag a year behind on shipping yearly OS releases. They skip over the monthly and quarterly releases entirely. They replaced their own non-GMS Fairphone OS with a dramatically less secure /e/OS option in partnership with Murena. They clearly demonstrate that security and even privacy are not the priorities.
> The security implication here is that the telephonic operating system has access to the same system resources as the application operating system at the same time, right?
> The baseband is isolated on all of the officially supported devices. Memory access is partitioned by the IOMMU and limited to internal memory and memory shared by the driver implementations. The baseband on the officially supported devices with a Qualcomm SoC implements Wi-Fi and Bluetooth as internal sandboxed processes rather than having a separate baseband for those like earlier devices.> The Debian Project nevertheless expects that all contributions submitted to Debian, regardless of how and with which tools they were produced, satisfy the same standards of quality, correctness, maintainability, and legal compliance.
Slop text on the homepage does not scream "quality" to me.
The code is worse, somehow. Endless paragraphs of comments that say nothing: https://github.com/crmne/fastpotify/blob/d9aafbf8e0b0c4d2da3...
Except for the input of the hundreds of stakeholders they consulted, Anthropic included [1]?
> The Union is stuck on major economic crises (electricity prices for instance) because nobody can agree on anything.
That sure seems relevant for the implementation of AI watermarking...
> However, the bureaucracy forces tech into a privacy nightmare.
No, this transparency allows consumers to more easily detect AI generated content.
[1] https://digital-strategy.ec.europa.eu/en/policies/code-pract...
Unless with "proofreading" you actually mean having the LLM write your content for you.
If you are on Arch, you can do this simple fix (instructions are similar for other distros):
sudo pacman -S forgejo
sudo systemctl enable --now forgejoNo. https://blog.codeberg.org/protecting-our-floss-commons-from-...
This vote was urgently scheduled for today, the last day of parliament before the summer break. 113 MEPs were not present for this vote, likely having taken vacation days to extend their break. It's hard to believe choosing to do the vote today was done accidentally.
Google, out of all companies, also decided to partially walk away from the Chinese market in 2010 over censorship concerns [1].
Nobody is forcing Apple to do business in China, or the UK. They actively choose to do so, and because of that also put themselves in a position where they have to comply with these laws, presumably because it makes them more money.
[1] https://www.nytimes.com/2010/03/23/technology/23google.html