PhilKunz

But it means we are optimizing for something else than the best outcome or not? It is like with mp3 vs flac: mp3 is fine and optimizes for amount of data to represent a certain waveform, but lossless is the real deal for audiophiles and the only one capturing the real thing at a certain resolution. Same might be true for complex code or the best solution to a compression algorithms. Can the question really be answered if optimizing for marking does still produce the best result? Is it not like an author wanting to say something one way, but being forced to use certain words to get there?

What would you be willing to pay rent wise for such a space? Would be helpful to know required square footage/m^2 , location/city, maximum acceptable price/month, acceptable commuting distance to desired location.

Honestly: By trying to control usage its not FOSS anymore and you yourself become a bad actor in the eyes if the FOSS idea. No soon to be unicorn can use any of your stuff.

May I add: You’d have to stop using VsCode or TypeScript, or even npm and Chrome, if you think big means bad, and you don’t want to fuel big corporations.

One can see how rediculous the whole idea of limiting FOSS in a “who can use this” way is.

Truly free will always win in the long way. Or you don’t think, a paid dev with some AI can replace your package fairly quickly?

fair enough. I replied to the wrong comment. Sorry for that.

coffee.link is getting a git based version feature to make changes more transparent.

Also there is a deno (+ electron for GUI version) based testing tool coming to better understand network routes.

Additionally I plan to do a well researched series called "How does the internet work".

I've learned quite a bit from the comments here, also got to see perspectives I wasn't focusing on. I've since then added a bit to the article about how one could be in favour of the deal. To be more transparent about changes, version history is coming to coffee.link.

The question I'm having is: Where exactly do inter.link and Google peer? Like either they are both at a public IXP (which would mean Google is not actually discontinuing peering, or you'd have to really define the "direct" in that quoted sentence), or one has a fiber cable to one of the others DC? How does that work? Any insights?

Is it the only peering of Starlink though?

except the only infrastructure to replace is the satellite dish, and not the fiber that goes into your home. Or am I wrong here.

HeyHey. The website uses Ghost right now, and a lit based web components catalogue. Some features are not yet entirely carved out. The commenting system being one of them. Components are ready, but some integration work has to be done. We also want to enable highlighting stuff directly, so people can comment on specific referenced stuff...

The commenting APIs in ghost are a little obscure.

How come? Based on what do you make the assumption? ;)

How come noone mentioned serena MCP here until now :D

Then use some rust file where you trust that the compiled file matches the source.

Well, you can read the source at least. Or tell AI to take a look.

In the end you always trust someone. At least bash and TypeScript is understood by enough people to judge it.

;) You still have to tell it to update.

This only installs 3 modules in total. net-snmp and 2 sub dependencies. It provides its own node.js bin directly from the node website so nupst knows exactly what it is working with.

Anyways, you don’t have to use it.

I mean I don't get this, especially after the recent security incidents...

AGPL ist the first moment ;) Elastic license the next one.

I believe in the common sense and basic goodness of people.

If people contributed for example under a MIT license without further contractual agreements, then licenses can't be simply changed by the main maintainer. This it is not a "me" problem.

Also it just means that people should for example now contribute here: * OpenSearch(https://opensearch.org/) instead of elasticsearch. * OpenTofu (https://opentofu.org/) instead of Terraform.

Maybe I need to revisit that part. My key point in other words is: restrictions are bad: In one moment they are intended to work pro open source, the next they work anti Open Source, by wrongfully claiming Open Source work for some exclusive commercial interests of a single entity.

Depends, no one took .so seriously before notion.so

Also, I own newyork.today for example... I think there is domains that the tld works with.

the logo is already taken by https://pocketbase.io

So how is a normal influencer then an actual influencer, and not just a person "releasing" content "for free to (the) world"?

I think a little bit differently about that:

There are some duties that apply to people that are open sourcing stuff:

* Don't lie about what it does. * Don't hack people by smuggling some nasty code into minor version updates. * Don't leave people vulnerable to third party exposure by not taking care of your private keys.

I am an Open Source dev myself, having about 300 modules on npm. I use it as reputation credit for actually getting jobs that pay good money.

If you are an Open Source dev, you are a "Code Influencer". You have to be straight about what you do. It is the same for normal influencers when they have to declare any paid promotion stuff.

how do devices find each other without an introductory server?

This is Phil from Lossless. I got a notification yesterday about someone having bought the domain skyglide.com .

Upon looking through the sales contract I noticed that instead of the other buyer party being listed in it, the data of the buyer was completely redacted. I repeatedly asked for the data, but was not receiving it. I then withdrew my declaration of intention to sell the domain in the first place, since in Germany and Europe the other party is an essential part of a sales contract. Without listing both parties a contract is rendered void. What is your opinion on this? How can they do this as a professional domain brokerage company?

yeah... either its lossless or its not.

I've always been a little cautious of running it myself. When I look at the components involved there are a lot of moving parts. And I don't want to be ever in a position where I can't get things started again. If I'm running on premise I'll switch to gitea with drone ci instead.

It seems like GitLab should indeed focus on stability now. The feature set is great. But it is all not worth it if it keeps disrupting work on a constant basis by being unstable.