ssb1 (u/ssb1) - Readit News

ssb1 commented on Ireland joins OECD International Tax agreement gov.ie/en/press-release/5... · Posted by u/threatofrain

rtpg · 4 years ago

But I mean… Ireland has a higher English proficiency?

There are of course a lot of things doable fully in English. But when running a company not mastering the native language (even when all of the people you talk to speak English!) can be a big drawback.

ssb1 · 4 years ago

I'm willing to bet that an American would understand the English spoken in Amsterdam better than that spoken in pubs or on playgrounds in Ireland.

ssb1 commented on No More Medium – Build Your Own Site (2019) nomedium.dev/... · Posted by u/mooreds

lamontcg · 4 years ago

> (Note) there is an obvious opportunity to create a medium like experience that lets people blog using Hugo and Netlify. I open an app, connect to my account (GitHub pages, or Netlify) type my article and post.

This is what I'd really like. All these alternatives assume you want to use your editor in the terminal and git and CI publication process. I want to edit markdown text in a web browser and click a button to see how its rendered and then go back to the editor without changing contexts at all.

The editor/git/CI model feels too much like actual fucking $dayjob work. Writing is already a difficult enough process -- lets turn it into software development while we're at it! I need to worry more about dependency management of my plugins while I'm trying to write and publish something.

Medium is worse though, its very annoying.

ssb1 · 4 years ago

Well there is https://www.netlifycms.org/

ssb1 commented on The Drivers Cooperative drivers.coop/... · Posted by u/pasquinelli

jasode · 5 years ago

>Ride-hailing apps always seemed like a model that was extremely conducive to a cooperative, worker-owned model.

It's only the surface-level of an ride-hailing app that seems easy for worker-owned cooperatives to create. In reality, the extra expensive programming dollars required to tame the hidden complexity so that the app can present a seamless experience to the customers/passengers is a huge factor that works against co-ops.

E.g. see the famous Uber comment on the complexity of the app: https://news.ycombinator.com/item?id=25376346

Real-life customers don't want to enter their credit-card details into City_X_driver_coop and then re-enter their financial details multiple times again into City_Y_driver_coop. Even if you imagine a hypothetical national co-op to consolidate multiple cities, customers would still then have inconvenience of Country_X_coop and Country-Y_coop.

It takes a lot of capital to pay programmer salaries for desirable features that customers want and since co-ops are capital-constrained (by definition because they can't take millions in investors money), the app will always have less features compared to Uber/Lyft.

That's the financial constraint that causes co-ops to more easily organize in lower complexity businesses such as local grocery co-op or a farming coop. But a high-tech complexity business that's expensive to build is inherently too costly for a pool of drivers' savings to fund.

Whenever you see the phrase "worker-owned", mentally substitute "capital-constrained" -- and it starts to make sense why many businesses domains don't have any coops rising up to compete with VC-fueled startups.

EDIT to reply: >Driver co-ops or smaller operators simply don’t need to worry about half the nonsense in the comment you linked

Sure, the driver co-ops can choose to not spend capital on "useless" features but this leaves out the fact that customers can also choose not to use the co-ops because of the lower quality app experience. Keep in mind the behavior of customers who prioritize conveniences.

E.g. the non-profit RideAustin app fails customers even after Uber/Lyft left Austin: https://techcrunch.com/2017/03/12/austin-is-fine-without-ube...

It takes capital to build tech solutions that deal with peak load. And RideAustin later shuts down in 2020: https://www.google.com/search?q=rideaustin+shuts+down

Well, one might say RideAustin was hampered by coronavirus lockdowns. That's true, but it also takes capital to get past an economic downturn of low revenue. Uber/Lyft got hurt by COVID as well but they had more capital reserves to deal with it.

ssb1 · 5 years ago

Riders will just use pay-by-qr-code.

ssb1 commented on GitTorrent: A Decentralized GitHub (2015) blog.printf.net/articles/... · Posted by u/mbroncano

Boulth6 · 5 years ago

This is a solution to a non-problem. Hosting taken down git repos is easy an due to gits design all developers already have the source code.

The real problem is hosting issues and PRs in such a way. Github has an API and it's possible to script the backup but source code gets backup automatically so when the takedown strikes it's not a big problem.

ssb1 · 5 years ago

Not git obvs, but Fossil keeps bugs (wiki, forum) as part of the repo.

https://www.fossil-scm.org/home/doc/trunk/www/bugtheory.wiki

ssb1 commented on Show HN: Archivy – Self-hosted knowledge base embedded into your filesystem github.com/Uzay-G/archivy... · Posted by u/etherio

breakfastduck · 5 years ago

That's really cool. I had no idea the reMarkable was that kind of product.

Shows that user contribution to a platform can be part of its success.

ssb1 · 5 years ago

It sure can, but they're not super supportive. https://remarkable.engineering/ is very terse and the linked GitHub org is not very active.

ssb1 commented on Show HN: Archivy – Self-hosted knowledge base embedded into your filesystem github.com/Uzay-G/archivy... · Posted by u/etherio

ldng · 5 years ago

I like their pricing : 399 USD == 399 GBP == 399 EUR

ssb1 · 5 years ago

You like that? Personally I prefer 399 USD == 304.50 GBP

ssb1 commented on Shall the West Pass Too? Whispers from Fallen Civilisations themetasophist.com/chapte... · Posted by u/sheefrex

pstuart · 5 years ago

So far you're on point as far as I'm concerned. I'm eager to see what you have to say about reversing course.

An issue that bothers me no end is the fact that we very well could get out of this mess if we collectively wanted to.

ssb1 · 5 years ago

"to no end" means: uselessly, futilely. 'no end" means: endlessly.

ssb1 commented on Why I Use Suckless Tools christine.website/blog/wh... · Posted by u/martinhath

dhimes · 6 years ago

You have working sleep? Man I'm so jealous.

ssb1 · 6 years ago

I've had working sleep since at least 2010 on ThinkPads and Dell XPS, Ubuntu and now Mint.

ssb1 commented on Tiny websites are great tinyprojects.dev/posts/ti... · Posted by u/stokesyio

woodrowbarlow · 6 years ago

i think slack now allows you to disable the visual editor in settings - you can still format with markdown but the formatting isn't rendered until you send.

ssb1 · 6 years ago

Yeah but it's half-arsed; specifically, doesn't do [links](...).

ssb1 commented on Notion encourages busy-work medium.com/diesdas-direct... · Posted by u/_ttg

gault8121 · 6 years ago

I am a huge Notion supporter - it's our organizaation's brain and one of our most important tools.

However, having used the tool for more than a year at a 20 person org, one of the biggest pain points I have seen is people not knowing where to place new pages. There is "Notion anxiety" about not wanting to mess up the board.

One thing we've done to address this is by adding two common tables, the Documentation table and the Meetings table. Anytime anyone wants to create a new doc, they can simply add it to the documentation table and then tag it to their team, and we have a full list of all of the docs everyone has written. From there, if a certain piece of documentation needs to be somewhat else, it can be pulled out and moved there. Additionally, each team member has a default "project board table" and if you say need to create a quick to do list, you should just add it to your personal board. Having these "default tables" rather than a special table for each specific project may really help your team.

Notion requires intentional planning, and you need to be opinionated about the architecture. If you just keep adding things on haphazardly, it's going to turn into a mess.

Finally, I do agree with OP that notifications could signicantly be improved. If anyone from Notion is reading this, please think of notifications like emails. At the moment, notifications are only in the state of read/unread, and as soon as I open my notifications, they clear. Instead, I want my notifications to be a mini-inbox, where I can view notifications, respond to notifications, archive completed notifications, and filter notifications into channels (the same way I can filter emails). Notifications are a to do list, and should be thought of as such. Having this set up would address OPs concern about being able to filter notifications at the email level by setting the filtering logic in the app.

ssb1 · 6 years ago

Linked databases also help for this. You can create a linked db filtered for a team or tag on every team page. Create meeting docs from there, and then new meeting docs show up there and live in the master table with appropriate properties to categorise them.