News for hackers. Stuff that matters.
Re:Kyoto project is moving from GitHub to Sourcehut by akudha on Saturday July 02, 2022 @07:55PM (#31963641)
As a rule of thumb, it is a good idea to support smaller and indie companies than mega corporations, IMHO - even if those mega corporations aren't doing anything that is ethically dubious. That is doubtful, as it is likely not possible to become that big without trampling on some toes or bending some rules.

Why support Github when there is st.ht? Why support Starbucks when you can support a mom & pop coffee shop? Why buy books from Amazon when you can buy from a Indie book store? Granted, not everyone has the patience, time and money to vote with wallet, but we can try wherever possible. I hope more people ditch Github

Re:Kyoto project is moving from GitHub to Sourcehut by throwaway894345 on Saturday July 02, 2022 @08:56PM (#31964033)
> Why support Github when there is st.ht?

I’m not super opposed, but Drew can be pretty over the top ideological/irritable for my tastes (at least that’s my perception from reading his blog). I’m not sure I want to invest in his platform if he could just boot me over an Internet disagreement or something. Yeah, I can back up my stuff, but at a certain point I may as well self-host.

Re:Kyoto project is moving from GitHub to Sourcehut by ddevault on Sunday July 03, 2022 @05:13AM (#31966313)
In the history of SourceHut, only one person (setting aside spam/crypto-miner bots) has been banned from the platform. They were harassing maintainers and failed to respond to an email inquiry seeking to discuss their behavior before resorting to a ban.

I have strong principles and I stand steadfast by them. However, one of those principles is tolerance for different views. I want SourceHut to be available for everyone, even if we don't see eye-to-eye. You won't be booted off if you and I happen to end up in an argument somewhere online.

I've made myself personally available to users, as a person they can directly reach about problems and concerns with the services, rather than a support ticket answered by a random lackey. I think this is very valuable. Software is made by people. One of the risks that comes with this, however, is that people can start to view SourceHut and my private identity tangled together. Rest assured, they are separate, and I treat SourceHut with a great deal of deliberate professionalism and reverence for our users.

Re:Kyoto project is moving from GitHub to Sourcehut by specialist on Sunday July 03, 2022 @08:02AM (#31967076)
Wondering if SourceHut has a code of conduct, I found its Terms of Service > Permissible Use: https://man.sr.ht/terms.md#permissible-use

Nicely done.

About banning... thinking out loud...

I wonder if a public ban log would reduce food fights. Nothing too fancy. Maybe just date, account name, cite terms violated, optionally cite evidence, admin actions taken. No need for comments, discussion, whatever.

Then whenever the peanut gallery starts concern trolling, you can just link to the ban log entry. Instead of explaining yourself, yet again.

Re:Kyoto project is moving from GitHub to Sourcehut by ddevault on Sunday July 03, 2022 @09:25AM (#31967546)
Maybe. Even if someone is banned, I still care about their privacy, and I would not want to disclose that they were banned. Providing this information also provides useful feedback to malicious actors like spammers, who are ordinarily banned in a means which makes it difficult for them to tell when an account is burned.

SourceHut is not a social network and does not have particularly arduous moderation needs. It's vanishingly rare for us to ban someone at all for this reason. We additionally provide banned users with a complete data export and tools to re-import that data into other SourceHut instances or instances using compatible software, so they are not left without options.

If someone feels slighted by moderation on SourceHut, I would invite them to speak publicly about it. I'm prepared to justify our actions in the court of public opinion with consent from the maligned.

Re:Kyoto project is moving from GitHub to Sourcehut by throwaway894345 on Sunday July 03, 2022 @10:03AM (#31967762)
Well said.
Re:Kyoto project is moving from GitHub to Sourcehut by indrora on Saturday July 02, 2022 @11:14PM (#31964728)
I at one point encountered Drew at a meetup.

He basically ignores anyone who has or currently does work at any company he deems unethical (read: Google/Amazon/Facebook/etc). You're forever tainted in his eyes, and your opinions are always only useful if someone else agrees with you that isn't tainted.

Which really sucks because his entire software stack depends on the work (and opinions) of the people that he discards: Go, Python, and Git for a few.

Re:Kyoto project is moving from GitHub to Sourcehut by eesmith on Sunday July 03, 2022 @03:34AM (#31965846)
But is he right? At what point is it unethical for an ethical person to continue to work for an unethical company? When should people who work for an unethical face personal negative effects?

He's not unique in this viewpoint. Quoting jwz: "As I've said before, if you work for Facebook, you should quit; it's the only morally defensible thing for you to do."

> his entire software stack depends ...

That sounds like the Mr. Gotcha meme: https://thenib.com/mister-gotcha/ . Again referring to jwz, his nightclub is on Facebook and Instagram because it's not economically viable to avoid them. ... Gotcha!

Similarly, it's hard to avoid all software which doesn't have influence from the big tech companies. I used https://github.com/swenson/sort ('Sorting routine implementations in "template" C"), and even this little indy package has contributors from Google Inc and the main developer worked at Google for a year.

DeVault's working on a new programming language, Hare. You could view that as having the long-term unstated goal of escaping unethical companies.

Re:Kyoto project is moving from GitHub to Sourcehut by smoldesu on Wednesday July 06, 2022 @03:18PM (#32005509)
I think the other comment was right to call them out on hypocrisy. There really are people out there who put their beliefs before their own comfort and even productivity (see: Richard Stallman). Now, that doesn't make them right, but if you're going to defend an opinion, you may as well go all the way. Personally, seeing petty behavior like this doesn't exactly fill me with confidence for whatever product they maintain. I wish I could get paid to maintain random OSS projects too, but the lights gotta stay on and $3 GitHub donations only take you so far. There's nothing evil about working at a company like Facebook unless you're an evil person.
Re:Kyoto project is moving from GitHub to Sourcehut by akudha on Saturday July 02, 2022 @09:03PM (#31964073)
I only gave source hut as an example. Maybe there are other projects like source hut that you might like, but are not ethically challenged like GitHub, that you might support?

The larger point still stands though. Instead of consumers simply supporting the biggest players in the market (because of convenience), it would be nice to give smaller players (who are not shady) a chance?

Re:Kyoto project is moving from GitHub to Sourcehut by mariusor on Sunday July 03, 2022 @03:59AM (#31965952)
> I’m not sure I want to invest in his platform if he could just boot me over an Internet disagreement or something.

There's a wide gap between being irritable and being unprofessional. Nothing I've seen so far in regards to how SourceHut is being managed, indicate that you'd have such problems. (I'm saying this as a long time user of SoutrceHut and as someone that got into arguments with Drew)

Re:Kyoto project is moving from GitHub to Sourcehut by yellowapple on Saturday July 02, 2022 @10:19PM (#31964464)
> I’m not sure I want to invest in his platform if he could just boot me over an Internet disagreement or something.

Has that happened?

Re:Kyoto project is moving from GitHub to Sourcehut by pmontra on Sunday July 03, 2022 @02:47AM (#31965641)
Self hosting is OK. I self host my personal projects and a few work ones (the ones with a customer that basically doesn't know what code is.) I usually don't want anyone else to look at them though. I let some friends work with me on some of them. If I need strangers or customers to look / work at the code it's been GitHub, GitLab or Bitbucket.
Re:Kyoto project is moving from GitHub to Sourcehut by josephcsible on Saturday July 02, 2022 @10:33PM (#31964537)
> I’m not sure I want to invest in his platform if he could just boot me over an Internet disagreement or something.

But the FAANGs do that to people all the time.

Re:Kyoto project is moving from GitHub to Sourcehut by kelnos on Sunday July 03, 2022 @12:02AM (#31964945)
That's not a reason to use a small, independent platform with a capricious project leader, though[0]. That's just an argument to use neither.

[0] (I have no idea if Drew DeVault would actually boot someone off his platform for arbitrary reasons, though. I'd hope that's not the case.)

Re:Kyoto project is moving from GitHub to Sourcehut by eesmith on Sunday July 03, 2022 @03:12AM (#31965745)
The iPhone App Store terms still conflicts with the GPL, right?

If so, isn't that also "over the top ideological"? After all, we know Apple's opposition to the GPL dates back to the early 1990s when NeXT used gcc for Objective C, and their rejection of GPLv3 caused them to ship ancient versions of bash, recently replaced with zsh, so it's not like they weren't aware of the GPL.

Some people use Linux (the moral equivalent to "self-host") to avoid Apple's ideological stance.

Which, from a business standpoint, makes for a marketing opportunity for a FOSS-aligned source code hosting company. Which takes us from an ideological position to an economics one.

(To quote Bill Hicks: “Oh, you know what Bill’s doing? He’s going for that anti-marketing dollar. That’s a good market. He’s very smart.”)

Re:Kyoto project is moving from GitHub to Sourcehut by BeetleB on Saturday July 02, 2022 @08:00PM (#31963673)
Last time I checked, sr.ht was mostly an email based workflow, and many teams wanted an issue tracking system that is web based
Re:Kyoto project is moving from GitHub to Sourcehut by ddevault on Saturday July 02, 2022 @08:05PM (#31963707)
SourceHut offers an email-based workflow with a web application built on top of it. You can file tickets via email, but you can also file tickets on the web:

https://todo.sr.ht/~sircmpwn/hare

The same goes for patches. You can submit changes directly via email, but you can also use our web interface. We're also working on web-based tools for code review built on top of our mailing lists, which will provide a complete experience similar to GitHub's pull requests, but built on top of the decentralized, standardized protocol that git was designed for.

Re:Kyoto project is moving from GitHub to Sourcehut by hunterb123 on Saturday July 02, 2022 @08:30PM (#31963857)
Hello, kinda offtopic, but are there plans for ForgeFed / ActivityPub support?

That really seems the best way to dethrone GitHub, as it's moat is mainly carved via a social network.

The git repo is already decentralized, ForgeFed is a great way to integrate and decentralize the social part.

In the future gitea, srht, and many other implementations could interact with each other's users.

Re:Kyoto project is moving from GitHub to Sourcehut by ddevault on Saturday July 02, 2022 @08:34PM (#31963880)
No, not at this time. I don't think that ActivityPub is the correct way to address this issue -- some people treat it like a golden hammer.

SourceHut is already federated: via email. Email is a standardized, federated protocol with thousands of implementations and a global fault-tolerant system already working in production for decades, and it's the approach git was designed to use. I think this is a better solution. You can already use SourceHut's tooling to contribute to projects like Linux, which don't use any forge software at all, thanks to this standardization.

Re:Kyoto project is moving from GitHub to Sourcehut by hunterb123 on Saturday July 02, 2022 @08:54PM (#31964018)
That's unfortunate. It's pretty difficult to run your own email server plus deal with the blacklisting. I see your points, but I also see a possibility to support both email and ActivityPub mediums. A lot of people want a dedicated interface, hence you having to make a web portal. I don't see why the web portal couldn't support ForgeFed in addition to email.

Being able to bridge standalone gitea instances users with repos on your service would be a good step forward for federation.

Re:Kyoto project is moving from GitHub to Sourcehut by ddevault on Saturday July 02, 2022 @09:01PM (#31964064)
ForgeFed is just a protocol, just like email. The interfaces can be essentially identical.

It's pretty difficult to host a fediverse server, too. I want to make SourceHut easier to self-host post-beta, including dealing with email bits, but I also don't think the dream of federation involves everyone running their own servers. One of the advantages of the federation model is that it strikes a balance between total centralization and total de-centralization in that it allows a talented sysadmin to provide services for a large number of users. There are more ways to federate than ActivityPub.

Re:Kyoto project is moving from GitHub to Sourcehut by hunterb123 on Saturday July 02, 2022 @09:09PM (#31964108)
Exactly my point. You could support both ActivityPub and email as protocols. I believe even commits could contain either address as it's a similar format.

As far as hosting difficulty goes, once Gitea supports ForgeFed, you'd be able to spin up your own instance as easy as running one program, and no worries about blacklisting.

I agree not everyone needs their own server, which is where shines sr.ht over Gitea, but a community developing a product sometimes wishes to run their own servers for their users. Sure they could run an email server, and users could use that, but it seems roundabout and outdated.

I agree there's more than one way to federate, but the goal is bridging everyone together. Those two aren't mutually exclusive if you support both protocols.

Re:Kyoto project is moving from GitHub to Sourcehut by ddevault on Saturday July 02, 2022 @09:14PM (#31964134)
Sorry, but I think we have to agree to disagree.
Re:Kyoto project is moving from GitHub to Sourcehut by jefurii on Sunday July 03, 2022 @03:37PM (#31970350)
It sounds like you want to volunteer to add ActivityPub to Sourcehut!
Re:Kyoto project is moving from GitHub to Sourcehut by hunterb123 on Sunday July 03, 2022 @04:41PM (#31970821)
Is the part that would allow this in sourcehut opensource & allowing contributions for this?

From the sounds of things he does not want the feature.

Re:Kyoto project is moving from GitHub to Sourcehut by the-anarchist on Saturday July 09, 2022 @01:24AM (#32032026)
And that's the caveat with SourceHut and the current discussion around it. While I respect Drew and his work, he isn't exactly the most approachable person in OSS.

If you and several other people happen to have a hard requirement for a specific feature that he (or his buddy Simon) don't see fit for, you won't get that feature, even if you volunteer to implement and maintain it. The only thing you're left with is basically to fork SourceHut, host it yourself and maintain your feature all by yourself, dealing with continuously patching a very much still-in-development (and therefore ever changing) software. That is something you're probably not going to do, especially considering SourceHut's architecture and way of doing things.

SourceHut isn't exactly extensible/pluggable and hosting it as a one man show or even a small company becomes a huge PITA, as soon as you diverge from the holy grail that is Drew's way of doing things (Alpine, no containers, no good config management, no easy way to scale things, and the dedication to invest your blood and tears into maintaining this thing).

Hence I really cannot comprehend the current trend that is "let's all dump GitHub for this, and that, and SourceHut". So far, SourceHut really hasn't made an effort to prove itself worthy of the influx of OSS projects. And while I do see Drew commenting here, reassuring folks he won't ban anyone over any internet disagreement, reading the public mailing lists of the SourceHut repos doesn't really show much of a welcoming behavior either. I mean, he's the person behind what has become one of the most popular Gemini servers, and as soon as that was the case, he began threatening client apps to arbitrary block them for doing things that don't align with his values (in this case, [showing a favicon](https://github.com/makeworld-the-better-one/amfora/issues/19...)). And the cabal of elite internet Amish, that have been on SourceHut since its early days and that makes a large portion of the platform, aren't that different either.

I do agree with GitHub being the wrong place for OSS projects, but I don't agree with SourceHut being the right one. At least for as long as it doesn't become obvious that its founder and the community around him has changed and started to genuinely appreciate people for the work they're doing, regardless of their own ideological beliefs.

Re:Kyoto project is moving from GitHub to Sourcehut by mariusor on Sunday July 03, 2022 @04:09AM (#31966015)
I see Drew already weight in on this, but there were a number of debates between ActivityPub proponents (of which I am one, though not in the source forge space) and him regarding this, where he was very explicit that he's not interested. Over time I ended up coming more to his side, and I agree that SourceHut doesn't need any extra social interaction that ActivityPub might bring.

That being said, the devs of Gitea are in the process of adding AP support, and it has been mentioned on HN already: https://news.ycombinator.com/item?id=31934758

Re:Kyoto project is moving from GitHub to Sourcehut by hunterb123 on Sunday July 03, 2022 @04:42PM (#31970834)
I'm aware, part of my assertion was to bridge Gitea and Sourcehut projects together via AP, I go into detail in my other replies.

I understand and support his decision, but I will be going with Gitea because I'd prefer AP networking over email. To each their own for sure, but my main suggestion was to support both so the communities aren't fragmented, that would be a bigger threat to Github's network effect. Oh well.

Re:Kyoto project is moving from GitHub to Sourcehut by BeetleB on Sunday July 03, 2022 @03:52PM (#31970468)
Thanks Drew. I may have been mistaken, or perhaps you added those features after I tried them.

I'll take another look.

Re:Kyoto project is moving from GitHub to Sourcehut by akudha on Saturday July 02, 2022 @08:44PM (#31963945)
That is why I said "wherever possible". If your team is going to quit their jobs (I doubt it) because they will only deal with a web based issue tracking, then sure, go for GitHub.

The point I am trying to make here is - by default people spend their money with mega corps, because of brand awareness, convenience etc. Instead, it would be nice if the default is indie/small businesses.

In other words instead of "the mega corps aren't working for me, let me look for smaller/indie options instead", it would be nice if we all did "smaller indie options don't fit my requirements, let me go with Microsoft/Apple/etc instead".

Maybe this is too idealistic?

Re:Kyoto project is moving from GitHub to Sourcehut by billythemaniam on Saturday July 02, 2022 @09:11PM (#31964117)
There is usually a reason those mega corporations became mega corporations. GitHub, in particular, is the easiest way to collaborate for most developers and they were the first one to get most things right. Absolutely vote with your wallet. If you want to support smaller companies, then do that. But realistically GitHub will be the default option until something comes along that is better. And whatever replaces Github has to be significantly better to justify the switching cost for majority of developers.
Re:Kyoto project is moving from GitHub to Sourcehut by presentation on Saturday July 02, 2022 @11:22PM (#31964759)
At such point it will probably become a large corporation that people will consider ethically challenged.
Re:Kyoto project is moving from GitHub to Sourcehut by BeetleB on Saturday July 02, 2022 @11:09PM (#31964704)
> If your team is going to quit their jobs (I doubt it) because they will only deal with a web based issue tracking, then sure, go for GitHub.

No but they will quit because an ideology most members of most teams was used to justify a decision that affected their work.

Re:Kyoto project is moving from GitHub to Sourcehut by nirui on Sunday July 03, 2022 @12:19AM (#31965026)
Maybe also too optimistic as well.

Let me start by telling you a story about me trying to buy clothes for the first time:

Back then, I have no idea of branding and the symbolism behind, I don't even have the idea of quality.

After many hours of browsing and comparing, I picked what I liked based on showcase pictures and user reviews, completely brand-blindly.

A week later when they arrived, I quickly discovered that few of them are false advertisments, some of them are in the wrong size and one got damaged during shipping. And for the rest items that were "just right", half of them ripped/deformed after half-year of use.

So, as a normal person would do, I created a table which consist of factors such as durability, price and styles etc to help me increase my "success rate". And after few years of iteration, that table ended up points me to just few brands that happens to be well-known and big.

I eventually settled on those brands with membership cards etc, and now whenever I need new clothes, I open their store page.

What I learned from my experience is that discovery itself generates cost, and the cost is nonrefundable. It is reasonable for an user to settle on a trusted brand. It's not brand loyalty, it's just rational decision making.

For most users, choose GitHub is rational, because it's the most trusted platform out there, and it provides good services (including the infrastructures and socials). You already knew what to expect before you even sign on, that's the level of trust GitHub delivers.

It's really hard to ask users to discover and move to the alternatives once their needs are well-fulfilled by the current one, even when the alternative provides the same level of service.

What makes it even harder is that services such as BitBucket, GitLab, SourceHut, Gitea etc can't provide the same level of service that GitHub offers for free. At this circumstances, the megacorp such as GitHub will always win even when the user is pro-indies by default.

But we are not completely dead in the water here. GitHub succeed because they created something new at the time, something better than what SourceForge offered.

I assume if someone wants to beat GitHub, they need to do the same. Don't just create alternatives, create something new that also does old things better.

Re:Kyoto project is moving from GitHub to Sourcehut by pmontra on Sunday July 03, 2022 @02:51AM (#31965663)
Let me point out that if you go buying clothes in a physical shop you can easily assess a large part of the quality of the clothes and you have no problems with shipping. This has a cost though and it doesn't solve the discovery part happening when you clean them (shrink, discoloration etc.) I think I never bought clothes online so far.
Re:Kyoto project is moving from GitHub to Sourcehut by yowmamasita on Saturday July 02, 2022 @08:07PM (#31963724)
Email is still the most robust communication medium. But I have also observed that it has also prevented emoji-only replies which is great.
Re:Kyoto project is moving from GitHub to Sourcehut by SnowHill9902 on Saturday July 02, 2022 @08:52PM (#31964003)
Standard but not robust. In fact it can silently fail.
Re:Kyoto project is moving from GitHub to Sourcehut by ddevault on Saturday July 02, 2022 @09:12PM (#31964120)
Email is very robust and does not fail silently -- unless you ignore the "undelivered returned to sender" emails you get. Mail servers are very fault tolerant, with essentially all implementations supporting an exponential backoff on failure. What's more, even if SourceHut is down, everyone in the Cc will still receive your emails, because they're routed around lists.sr.ht anyway. In the event of a lists.sr.ht outage, you might not even notice that we're down.
Re:Kyoto project is moving from GitHub to Sourcehut by kelnos on Sunday July 03, 2022 @12:06AM (#31964957)
Unfortunately some of the larger mail providers will "accept" mail they don't like, but then blackhole it.

Yes, you can say "well, your intended recipients shouldn't use mail providers that do that", but in reality that's not our choice.

Re:Kyoto project is moving from GitHub to Sourcehut by midenginedcoupe on Sunday July 03, 2022 @03:59AM (#31965951)
That's unfortunately just not true. It does, and has, failed silently.

I've had Google silently swallow emails before, both sending and receiving. It's not fun.

Re:Kyoto project is moving from GitHub to Sourcehut by kcartlidge on Sunday July 03, 2022 @04:29AM (#31966112)
You may be right generally, but for your specific example that's not email being rubbish it's Google being rubbish. Why not switch to a professional provider?
Re:Kyoto project is moving from GitHub to Sourcehut by midenginedcoupe on Tuesday July 05, 2022 @05:25AM (#31986126)
Yes. Google's implementation of email. One of the most highly used email implementations on the planet.

That was just one example, I've seen corporate Exchange systems do the same. Are they not professional?

If one of the biggest email providers on the planet can silently swallow and not deliver emails, then blanket statements saying emails never fail are just wrong. It's important to understand practical failure modes of the systems we use, and not pretend they're more perfect than they are in reality.

Re:Kyoto project is moving from GitHub to Sourcehut by nix23 on Sunday July 03, 2022 @07:29AM (#31966894)
It's funny that always when email fails, the next word is gmail, maybe go away from that wannabe email service? And no dont tell me a private server is impossible, i manage more then 150 (from different customers) of them and have zero problems with delivery to gmail ms etc, but yes you need to veryfi your domain @ google and microsoft.
Re:Kyoto project is moving from GitHub to Sourcehut by spoils19 on Saturday July 02, 2022 @08:42PM (#31963933)
Then those teams are wrong considering email is more robust, efficient and overall a better tool for the job.
Re:Kyoto project is moving from GitHub to Sourcehut by snapetom on Saturday July 02, 2022 @09:23PM (#31964181)
> Why support Starbucks when you can support a mom & pop coffee shop

Because small, local is not always better. It's quite common to find coffee shops here in the PNW that make a horrendous espresso. Most roasters here in Seattle are pretty mediocre and only capitalizing on the Seattle reputation. I can rattle off all the "local" and "small-batch" bourbon/gin/vodka distilleries that use sourced alcohol and are over-priced train wrecks powered only by marketing and no skill. At least with Starbucks, I get consistently bad coffee. I'm not risking over paying for coffee that I spit out.

Definitely have been looking at st.ht but if github fulfills my needs better, I'm sticking with that.

Re:Kyoto project is moving from GitHub to Sourcehut by petre on Sunday July 03, 2022 @01:39AM (#31965379)
> I'm not risking over paying for coffee that I spit out.

That's exactly what happened to me at Starbucks. I had to wait for a small cookie shop to open up in order to buy an overpriced decent espresso. They had an Illy logo which helped a bit.

In Italy and Greece you specifically want to avoid big chains as almost every small shop makes better coffee.

Re:Kyoto project is moving from GitHub to Sourcehut by snapetom on Sunday July 03, 2022 @03:30PM (#31970287)
I remember getting a cappuccino from a train station vending machine in Italy and saying, "Hey, this isn't too bad! Much better than Starbucks!"

Problem is that, I would say the majority of, small coffee shops in the US makes horrible espresso. Coffee isn't a craft to your average American no matter they claim, and they'll drink any swill. It's a way to get caffeine in you. Dark roast is the best selling roast.

If I go to a small coffee shop and they ask me what I mean when I order a doppio, that's when I start looking across the street for a Starbucks. At least Starbucks baristas are trained on what doppios are, and I'll get a consistently bad one. There's a very good chance that small mom and pop one will make me cigarette ash juice if they don't know what a doppio is. I'll take bad espresso over ash juice any day.

Re:Kyoto project is moving from GitHub to Sourcehut by OJFord on Sunday July 03, 2022 @07:47AM (#31966986)
> They had an Illy logo which helped a bit.

Interesting, does it? Obviously tastes differ, but I'm trying a tin at the moment because I ran out and could get it same day vs. waiting for delivery from my usual roaster subscription - I may as well be drinking any old thing off the supermarket shelf, don't find it superior at all.

Possibly the blend just isn't too my taste, it also doesn't seem to be as fine as I think I would grind it, but I think the main thing is freshness. Despite its vacuum seal it's still months old, vs. I usually receive beans within a few days of roasting and grind on demand.

Re:Kyoto project is moving from GitHub to Sourcehut by petre on Sunday July 03, 2022 @08:19AM (#31967149)
Maybe. I'm not a habitual coffee drinker, we buy roasted beans at home/work. It tastes better than Starbucks sludge or vacuum sealed supermarket stuff. Illy was the most decent supermarket brand, but in shops they use beans.
Re:Kyoto project is moving from GitHub to Sourcehut by flakiness on Sunday July 03, 2022 @02:08AM (#31965484)
Comparing Seattle with Italy would be insulting :-/
Re:Kyoto project is moving from GitHub to Sourcehut by petre on Sunday July 03, 2022 @02:34PM (#31969896)
For Italy?
Re:Kyoto project is moving from GitHub to Sourcehut by vlunkr on Saturday July 02, 2022 @08:19PM (#31963794)
Smaller companies are a much bigger risk as a dependency. Whatever GitHub may do in the future, they are unlikely to disappear in any time frame I care about.
Re:Kyoto project is moving from GitHub to Sourcehut by 015a on Saturday July 02, 2022 @08:42PM (#31963935)
Tell that to the people who relied on Google Wave and Wunderlist. Or to the people who said "Linux will go the way of every other hobbyist OS" in 1994. I knew several orgs who were devastated when Atlassian shut down Hipchat.

If you want the only guaranteed probability about the future: its that most predictions about the future are wrong. Everything dies eventually; the things you least expect last longer than you expect them to; or sometimes much shorter. I do feel pretty confident that both Github and sr.ht will be operational tomorrow. But, not 100%; and even less than that next Tuesday; and even less by September.

Actually, Github has had 12 public incidents since May. So... maybe I shouldn't be so bold with my predictions about Github's operational status.

When people say "something is unlikely to happen" what they really mean is: I really hope that thing doesn't happen. Me, personally; I hope both Github and sr.ht continue to see success. As you say; me choosing to pay Github $5/mo won't change anything for the better or worse; but paying that to sr.ht, now that impact is much bigger. If you distil it down to the manifestation of your own hopes: I think the choice of who to support is obvious.

Re:Kyoto project is moving from GitHub to Sourcehut by EricE on Saturday July 02, 2022 @09:55PM (#31964353)
Google and Microsoft are not even remotely similar in culture or product support.

Say what you want about Microsoft, they do more than just search or advertising. If anything you are interested in from Google isn't search or advertising related, don't count on it lasting. The only people surprised by Wave and/or Wunderlist getting canned are people who haven't been realistically looking at who Google is and how they operate. The worst IT contracts I have ever had to administer are with Google - they are a complete joke.

As for "incidents" - lol - who doesn't have them? What's more important is how does the org in question respond to them. You seriously think sr.ht is going to have the same resources as github/Microsoft? Then again it's a dramatically simpler platform so that's a huge advantage as far as that goes - but just look at this thread; as they add more features the chances for incidents goes up.

Re:Kyoto project is moving from GitHub to Sourcehut by 015a on Saturday July 02, 2022 @10:21PM (#31964476)
You're aware that Wunderlist was purchased and shut down by Microsoft, correct?
Re:Kyoto project is moving from GitHub to Sourcehut by Kwpolska on Sunday July 03, 2022 @03:44AM (#31965894)
You’re aware that Microsoft To Do is effectively the new Wunderlist, correct?
Re:Kyoto project is moving from GitHub to Sourcehut by nix23 on Sunday July 03, 2022 @10:08AM (#31967787)
Re:Kyoto project is moving from GitHub to Sourcehut by newuser94303 on Saturday July 02, 2022 @08:57PM (#31964041)
Google Wave is a bad example. I went to the first hackathon and knew it was doomed. It never had any real traction.

Github has massive market share and may get expensive but is unlikely to die.

Re:Kyoto project is moving from GitHub to Sourcehut by OJFord on Sunday July 03, 2022 @07:49AM (#31967002)
Yeah exactly, GitHub would be sold, not turned off.

And that would worry people, sure, new owners may not look after it, etc., but there'd be plenty of time and warnings to move off it.

Re:Kyoto project is moving from GitHub to Sourcehut by snapetom on Saturday July 02, 2022 @09:25PM (#31964191)
Google Wave was also a looong time ago. People were still thinking of them as the "do no evil" company.
Re:Kyoto project is moving from GitHub to Sourcehut by ddevault on Saturday July 02, 2022 @08:23PM (#31963812)
This is why we take pains to be transparent about things like finances:

https://sourcehut.org/blog/2022-04-08-2021-financial-report/

SourceHut is profitable and sustainable, thanks in no small part to the fact that we expect users to pay if they have the means. Small companies providing free services with investor subsidies are much more likely to disappear than a company with a service you're paying for which isn't beholden to any investor demands for infinite growth.

Re:Kyoto project is moving from GitHub to Sourcehut by alberth on Saturday July 02, 2022 @09:02PM (#31964067)
> “ we expect users to pay if they have the means”

Hi Drew

I’d encourage you to start charging then based on your comment above.

Because sourcehut pricing page currently says “payment is currently optional”.

You’ve been in alpha for a few years now and I’m sure many of us would agree it’s totally appropriate for you to start officially charging based on the quality of your service.

https://sourcehut.org/pricing/

Re:Kyoto project is moving from GitHub to Sourcehut by ddevault on Saturday July 02, 2022 @09:13PM (#31964130)
I should have been clearer: the expectation is only in force following the beta. We have a specific set of goals we would like to meet first. In the meantime we expect users to pay but are understanding of those who would prefer not to pay for incomplete software, even if our definition of "complete" exceeds industry standards.
Re:Kyoto project is moving from GitHub to Sourcehut by zxspectrum1982 on Sunday July 03, 2022 @08:35AM (#31967228)
But is it really profitable and sustainable?

IIUC your report, you are paying developers (and yourself) only USD $30,000/year. The typical software developer would make at least three time that much elsewhere. With 3x salary, I'd say SourceHut would no longer be profitable or sustainable. Or am I missing something?

Re:Kyoto project is moving from GitHub to Sourcehut by ddevault on Sunday July 03, 2022 @10:27AM (#31967919)
We pay out base salaries well below market rates, but we supplement them with the FOSS consultancy at each individual employee's discretion. With these sources combined, our total compensation is similar to market rates, and often more -- one of our engineers made over $150,000 last year. We also set aside 3 months base salary for all developers so that even in the worst case scenario of our revenue dropping to zero, they have security. I explained how some of this works the last time we posted a job ad:

https://sourcehut.org/blog/2021-08-23-work-at-sourcehut/

The sustainability metrics are based on revenue covering the small base compensation plus operating expenses, as well as having a large enough standing balance to weather any unexpected events. We seek to make models which guarantee the longevity of the platform, and prioritize making sure that our cash flow will always provide for operating expenses. If our revenue dropped to zero today, we would be able to run the platform for several years.

Ultimately, everyone involved in SourceHut is there because they believe in free software and believe in the model we've designed to further its cause. Our non-negotiable ethical standards calls for a creative business model to make this thing work.

The work experience and impact we offer is something that is, in my opinion, completely unmatched in the industry. It's not for everyone, but we believe in what we're doing, and it's worth taking a gamble on an unproven business model.

Re:Kyoto project is moving from GitHub to Sourcehut by josephcsible on Saturday July 02, 2022 @11:30PM (#31964794)
They're less likely to disappear, sure, but they're way more likely to permaban you and lock you out of your stuff, with no way to get ahold of a human who can undo it for you.
Re:Kyoto project is moving from GitHub to Sourcehut by tssva on Sunday July 03, 2022 @02:09AM (#31965488)
Having dealt with many local small businesses owners I'm not sure there is any significant difference in their propensity for ethically dubious behavior vs mega corporations.
Re:Kyoto project is moving from GitHub to Sourcehut by Aeolun on Saturday July 02, 2022 @08:15PM (#31963776)
> Why support Github when there is st.ht?

Github is about 1000x more user friendly?

Re:Kyoto project is moving from GitHub to Sourcehut by 015a on Saturday July 02, 2022 @08:52PM (#31964002)
I would argue, that depends on the user.
Re:Kyoto project is moving from GitHub to Sourcehut by mkeedlinger on Sunday July 03, 2022 @02:53AM (#31965668)
If it's more user friendly for 1000x the number of users, I would say that counts.
Re:Kyoto project is moving from GitHub to Sourcehut by xigoi on Sunday July 03, 2022 @11:48AM (#31968584)
What proportion of GitHub users has tried SourceHut?
Re:Kyoto project is moving from GitHub to Sourcehut by xigoi on Sunday July 03, 2022 @11:48AM (#31968579)
If by “user-friendly” you mean “slow”…
Re:Kyoto project is moving from GitHub to Sourcehut by badrabbit on Saturday July 02, 2022 @08:17PM (#31963781)
Are you kidding me? Smaller companies will use you to make mistakes and learn. And when they can't support something because of resources then you bear the consequences. Nice notion but not a rule of thumb in my opinion. Mega corps like google are terrible as well. Newish companies that have been in the industry a few years are the rule of thumb unless you can afford to be their guineapig/stepping-stone.
Re:Kyoto project is moving from GitHub to Sourcehut by echelon on Saturday July 02, 2022 @08:55PM (#31964023)
> Smaller companies will use you to make mistakes and learn.

And the big ones don't ever do this? You're probably shielded from the jira ticket backlogs that are thousands deep.

While there's no hard and fast rule, small companies tend to care more, as they're closer to the pain. A loss of a customer isn't just "churn".

We should strive to have at least four to six alternatives for every type of system. It keeps pricing competitive, gives users lots of alternatives, and prevents single players from strong arming behavior.

Right now there are too many monopolies and duopolies in tech.

Re:Kyoto project is moving from GitHub to Sourcehut by badrabbit on Saturday July 02, 2022 @11:12PM (#31964720)
I agree with the last part of your post but I think you misunderstood what I meant by smaller, I meant small because they are new not because they haven't grown yet. It is unavoidable for new companies to have growing pains, doesn't matter how much they want to please customers. Once they have developed some maturity with their staff the "jira backlogs" will be prioritized right because their staff has learned from outages they caused because they did not understand what different aspects of your product mean to each customer.
Re:Kyoto project is moving from GitHub to Sourcehut by RicoElectrico on Saturday July 02, 2022 @08:15PM (#31963772)
On the B2B and B2G side economic patriotism is strong in Germany and France, but it seems that as a result local companies don't have to try as hard. Why bother if they will choose you based on nationality, not necessarily merit?

Remember OVH server room fire? Was there any failure of such magnitude in AWS/Azure/GCP?

Re:Kyoto project is moving from GitHub to Sourcehut by Macha on Saturday July 09, 2022 @08:51AM (#32034605)
OVH is not playing in the same market as the big cloud providers - its primary business is doing commodity dedicated servers with the primary selling point being low cost.

It's hardly surprising that low cost options are more prone to failures in many markets.

Re:Kyoto project is moving from GitHub to Sourcehut by wnolens on Saturday July 02, 2022 @08:07PM (#31963727)
I don't follow what you've taken for granted.

Why not buy the best product at the price you're willing to pay for it, even from a company with the values you share? Where does company size take precedent?

Re:Kyoto project is moving from GitHub to Sourcehut by MatthiasPortzel on Saturday July 02, 2022 @08:36PM (#31963889)
Two reasons.

If you don’t make an effort to try smaller company’s products, you’re going to be biased towards bigger companies by virtue of them having better marketing and network effects. Some conscious preference to smaller companies can help counteract this.

And even if the smaller company has a worse product initially, some people using it anyways can help keep them alive in order to fund innovation. Smaller companies tend to be more willing to experiment or innovate, but that can’t happen if no one is willing to make a long-term bet.

Re:Kyoto project is moving from GitHub to Sourcehut by RootKitBeerCat on Saturday July 02, 2022 @08:10PM (#31963738)
Who shares Microsoft’s “values”, and what are they?
Re:Kyoto project is moving from GitHub to Sourcehut by minraws on Saturday July 02, 2022 @08:48PM (#31963976)
Microsoft? from what the flowing winds tells me, they seem to be,

> A very rich, multi-trillion dollar asshole-ish corporation, that feels lonely on it's birthday and goes on a bender buying less rich and asshole-ish companies to successively kill them, to calm it's mood.

Not sure how true that is, but something tells me it might just be the reality.

Re:Kyoto project is moving from GitHub to Sourcehut by kelnos on Sunday July 03, 2022 @12:11AM (#31964979)
I think it's more nuanced than that. I'm happy to buy from a smaller producer that may not have the absolute best product, as long as it meets my needs. I think consolidation and concentration of capital is one of the worst features of capitalism, and we should patronize smaller producers when it's reasonable to do so.

Having said that, I still buy a lot of things from Amazon because it's much more convenient than the alternatives. It's a habit I've been trying to kick, but I have a ways to go.

Re:Kyoto project is moving from GitHub to Sourcehut by wnolens on Sunday July 03, 2022 @04:40PM (#31970816)
Consolidation is efficient. It frees up capital to be used elsewhere. No need for 10x accounting and marketing and sales department when 10 companies exist instead of one.

Of course a homogeneous world is less interesting. And anti-competitive behaviors are net bad and need to be disincentivized. Big company hate just seems misplaced.

Re:Kyoto project is moving from GitHub to Sourcehut by manfre on Sunday July 03, 2022 @06:41AM (#31966664)
Another generic rule that is worth following is to not depend on software or services self labeled as alpha, beta, or any other pre-release.
Re:Kyoto project is moving from GitHub to Sourcehut by ddevault on Sunday July 03, 2022 @10:41AM (#31968038)
It's a useful shorthand, certainly, but what is it shorthand for? Sophistication of the software, availability, performance, sustainability, security? We have many of these things and we offer transparency and data to back it up. SourceHut has a proven record of better uptime than GitHub and GitLab over its entire lifetime and is the highest performing forge platform available. We can offer many guarantees, backed by public data, which many platforms which label themselves as production-ready cannot.

We hold ourselves to a higher standard than most and we have a specific and documented set of goals to accomplish before we declare the alpha complete. However, any potential user who wants to use SourceHut today can find a wealth of information to secure peace of mind in their choice.

Re:Kyoto project is moving from GitHub to Sourcehut by rendaw on Saturday July 02, 2022 @11:40PM (#31964842)
You're alienating the vast majority of devs by choosing sr.ht, who don't have accounts there and don't want to set up yet another account, don't want to use mailing lists, etc.

In the end it's an ideals tradeoff. Are you going to prioritize the growth of your project ecosystem but give into megacorps, or are you kneecap contributions by choosing esoteric ethical workflows.

Re:Kyoto project is moving from GitHub to Sourcehut by freeopinion on Sunday July 03, 2022 @12:18AM (#31965023)
I'm not here to defend any one service specifically. But I would like to let anybody with an aversion to Github know that they are not alone. And you are not some pariah. For that matter, it's ok if you don't even use git. If you have an interesting project, people will still be interested if you're willing to work with them.

Many a would-be contributor has lost interest when a project was entirely dependent on github, too. It's pretty telling when a contributor uses git, but can't contribute to a project that also uses git.

Re:Kyoto project is moving from GitHub to Sourcehut by astrange on Sunday July 03, 2022 @02:29AM (#31965576)
> Why support Github when there is st.ht? Why support Starbucks when you can support a mom & pop coffee shop?

Small businesses usually treat their employees worse than chains do (because "we're all a family"). Also… coffee shops seem to have big opinions of themselves but the farmers do all the work. Baristas just have value unfairly credited to them by the customers because the product is addictive.