Vysogota

Vysogota

@petko.me

за днес толкова, вика, и този свят свърши 🌉 bridged from ⁂ https://social.petko.me/@petko, follow @ap.brid.gy to interact

31 followers6 following990 posts

Vysogota
@petko.me

> Кирил Вълчев призова Георги Кандев да бъде мъж и да се съгласи на дебат а колко е тъп....

Vysogota reposted

peio
@pei0.bsky.social

Ако ГЕРБ и ДПС имат минимални инстинкти за самосъхранение, ще хвърлят всичко зад Гюров на втория тур.

Vysogota reposted

peio
@pei0.bsky.social

Една част от мен се сеща, че Демерджиев беше адвокат на този от ПИМК, а сега е щял да бъде рамо до рамо с Бинев. Не му върви нещо на този министър с битовата престъпност

Vysogota
@petko.me

Ум царува, ум робува, ум ЛЛМ-и пасе, @kunev. Дошло е при нас нареждане всичко да се пренапише на nodejs+react

Vysogota
@petko.me

In other news today, tech CEOs are scared shitless by the vibecoded Adobe competitor. Because of that, our team has been split in two and one half of the team with 50 slop machines will burn an irresponsible amount of Euros trying to ship a ground-up rewrite of our product...

Vysogota
@petko.me

Hey, @openstreetmap community, is there a project that reads #osm2pgsql data and outputs a .osm or .osm.pbf (for use with mkgmap)? #OpenStreetMap #osm2pgsql #mkgmap

Vysogota reposted

lea
@lea.ordinary.cafe.ap.brid.gy

If you/your project is affected by DigitalOcean stopping their OSS credits program, please shoot me a PM immediately. Might be able to help. Boosts for visibility would be appreciated. #foss #linux

Vysogota reposted

Tom Chadwin
@tomchadwin.en.osm.town.ap.brid.gy

If anyone can help with my @geoserver cascaded WMS any further, I'd be really grateful: https://discourse.osgeo.org/t/cascade-wms-failing-in-v3-0-1/ #geoserver

discourse.osgeo.orgCascade WMS failing in v3.0.1Hello We had a cascaded WMS working in 2.28.5. After upgrade to 3.0.1, it is failing to load in a WMS client (QGIS). The remote WMS loads fine in QGIS direct without Geoserver cascading it. It appears to be timing out after a long delay in QGIS. Log includes: Error rendering coverage on the fast path Caused by: org.geoserver.platform.ServiceException: org.apache.hc.core5.http.ConnectionRequestTimeoutException: Timeout deadline: 180000 MILLISECONDS, actual: 180000 MILLISECONDS Caused by: org....

Vysogota reposted

Todor Hlebarov
@todor.mograph.social.ap.brid.gy

Replying to @todor.mograph.social.ap.brid.gy

Made a quick sketch in my style to honour it! And to me it's about more than just the game itself. It's also how CDPR respect their audience and build trust by giving fans a solid update for completely free. Can't think of many other AAA companies that do that *cough cough* Activision *cough cough*

Vysogota
@petko.me

@kunev а знаем ли защо ллм индивидите настояват да посочвад claude за co-authored by в гит къмитите си?

Vysogota reposted

sky
@scroeser.kolektiva.social.ap.brid.gy

Repeated reminder that if you're new here, following the #intro and #introduction tag (and posting your own introduction) is a good way to find people!

Vysogota reposted

Daniel Gultsch
@daniel.gultsch.social

Conversations is now permanently available for free on Google Play. Google doesn’t deserve me and my money anymore. https://gultsch.de/posts/breaking-up-with-google-play/ #XMPP #Jabber #Conversations_im #Android #FOSS #OpenSource #Google #GooglePlay

gultsch.deBreaking Up with Google Play: Why Conversations Is Now FreeConversations, my federated instant messaging client for Android, started out as many traditional open-source projects do: as an attempt to scratch my own itch. Development started in January 2014 in my student dormitory, and within weeks I started dogfooding and using the client as the primary means of communicating with my friends. However, when it came to releasing the app to the public on March 24, 2014—exactly twelve and a half years ago today—it was immediately clear to me that I would at least try to turn my open-source project into a business. While I didn’t invent the business model of making the source code publicly available but charging for the convenience of a compiled binary, it was certainly unusual in 2014.
Vysogota
@petko.me

https://blogs.gnome.org/alatiera/2026/09/23/the-gnome-llm-policy-that-i-want/

blogs.gnome.orgThe GNOME LLM Policy That I WantKDE is on the news because of a _controversial_ proposal to define an official “AI” (LLM) policy. Other projects have tried their hand at similar policies and stances but, in my opinion, they miss the mark about the goal of such initiatives. I think that the point of these statements is shaping _social norms_ and not micro-managing developer workflows. They should be about signalling what kind of behavior we want, and what kind we reject. This proposal does not go into detail about the many problems that LLM have caused to society, workers, the environment. It goes without saying that all these ills are fundamentally opposed to the humanist spirit of GNOME. With all that in mind, here is what I _personally_ think a GNOME LLM policy could be: ## A GNOME Project LLM Policy The GNOME Project prioritizes the social and human aspects of collective software creation. Therefore: 1. LLMs ("AI") can not be used to create or modify code submitted to GNOME, or hosted on GNOME infrastructure. You might be asked to prove your code meets this requirement. You might be banned for trying to circumvent this policy. #### Example Guidelines for Contributors These are just a draft of the kind of criteria one could use to evaluate if a submission fits the policy. * You must be able to personally reason and explain your changes * You must be able to demonstrate knowledge of the problem space you are working on * You must solve the underlying issue, not just its symptoms * You must respect the time of fellow contributors * You must not impersonate yourself through chatbots, agents, or other automated systems ## This Is About The Future Of GNOME GNOME is not just software that happens to ship every six months. That is just a delusion we have been holding up for the last 30 years to keep our loose group of colleagues, friends, and acquaintances, together. GNOME exists as a collective that find joy in reaching beyond our individual limitations to achieve something bigger. These people, this joy, are the whole point of the project. Contributors are not payroll, a liability, that we hope to downsize next quarter. _“Come do free labor for a handful of corporations by reviewing chatbot output in your free time”_ is not an attractive proposition to young talented people in 2026. If we want GNOME to continue we need to create an attractive and inviting social space where people are valued as people. Just like the Foundation is moving to individual donations to stop depending on just a handful of companies, we need to look for the next 100 people that will donate a tiny bit of their time, instead of hoping that corporations will keep 10 overworked engineers on staff. We already have seen how companies will happily abandon a whole chunk of GNOME on a whim. GNOME is not just software, and it should protect the social and human aspects that make it special. Our success metric is the community and social bonds we create. In the most literal sense GNOME is about the journey and the friends we make along the way. Free Palestine. ## FAQ #### How do you enforce this? You can not. People will still send LLM generated code. This policy makes it explicit that we do not welcome these careless submissions. We have a Code of Conduct that is 80% about telling other people what our values are, and 20% about handling unwanted behavior (“enforcing”). This is similar. #### What if people simply lie about not using LLMs? This is the same problem as authorship, in the copyright sense. Whenever we receive new code we have to assume that “beyond a reasonable doubt” said code has been authored by the person contributing it. We make our best guess. The attached guidelines are a suggestion to make these new guesses. #### Ok. But what if people are really good at lying? This policy is about the majority that will not even try to lie. See previous questions.