picoblaanket

joined 2 years ago
[–] [email protected] 3 points 1 month ago (1 children)

I’m waiting for the math... Support your claim that you would “make a killing”.

I don’t see how you would...

The most you could possibly make would be $32.50 in an hour... (and that’s ONLY if you had a fare for ALL 60 minutes of an hour... and somehow still made less than $32.50 from those fares).

...And you'd be driving your own car and burning gas for that whole hour...

So show me (with math) how you’d be “making a killing”.

[–] [email protected] 6 points 1 month ago* (last edited 1 month ago) (1 children)

The central feature of their business IS having drivers WAITING when a ride is requested.

So yes - it would be fair if they included some “waiting time” for each ride (maybe up to 15 minutes of actual waiting time).

These apps ONLY have value if there are drivers WAITING when a ride is requested, so drivers should be paid for that.

[–] [email protected] 7 points 1 month ago* (last edited 1 month ago) (3 children)

Okay...

Give me the math of how this new wage would help you “make a killing”.

Keep in mind that this wage merely sets a floor for the specific-minutes when you have a fare.

  • (And brother - driving for uber is not "running your own business"... it's being maximally-exploited by a business... with no liability-protection, no security, and almost zero rights.)
[–] [email protected] 35 points 1 month ago (13 children)

If you wait 10 minutes for a fare… give a 20-minute ride to some suburban house… and then drive 20 minutes back to the city…

your pay would be $10.83 (with this new deal).

…that’s very different from $32.50 per hour.

  • Does an airline baggage-handler only get paid for the “specific minutes” when he is lifting luggage?

  • Does a cashier only get paid for “specific minutes” when there are customers in her line?

The original goal of this lawsuit was to classify drivers as employees under state law…

And that goal was ignored completely.

[–] [email protected] 98 points 1 month ago (16 children)

It’s not as much as it seems…

The wage is only “for time spent traveling to pick up riders, and transporting them to their destination”.

  • No pay for driving back to the pickup area.

  • No pay for waiting when there are no fares.

It’s a per-minute wage, and only for certain minutes.

[–] [email protected] 7 points 2 months ago (1 children)

I love the joy you feel from the appearance of a monarch - knowing what that signifies.

And I love the way you study the overall water channel.

[–] [email protected] 1 points 3 months ago (2 children)

I think you have to select multiple languages in settings.

Select "Undetermined, English, and any others" (and then save).

(this language setting affects the web app, mobile app, and search results)

That might fix it buddy.

[–] [email protected] 0 points 1 year ago* (last edited 1 year ago) (1 children)

Yeah, I understand what you mean (after a year of exploring the Web Socket).

FYI - that lemmy auth value is pulled from a JWT cookie in the browser - which you can access in JS by document.cookie. It is required for any API calls which are user-specific (saved posts, subscribed communities, etc).

[–] [email protected] 4 points 1 year ago

Yes exactly - living on the edge!

One way to learn the new API is - explore the code of (similar) extensions and browser scripts, to see how they build and send their calls.

[–] [email protected] 3 points 1 year ago (3 children)

Is there a specific API call you'd like to make?

Maybe someone can reveal that method and endpoint.

[–] [email protected] 1 points 1 year ago* (last edited 1 year ago) (1 children)

This User Script called Fediverse Redirector auto-redirects all Community, Post, and User pages to your home instance. It works well.

  • Just click install on that page - it will be added to TamperMonkey (or similar).

  • Then click settings (under the script) and enter your home lemmy instance.

And to directly answer your question: the raw code is visible in that repo, so you could explore how the post redirect query was constructed.

[–] [email protected] 2 points 1 year ago* (last edited 1 year ago)

Yes, this issue has been fixed and merged into 18.1 (the next lemmy version).

And as a temporary fix (until 18.1 releases) - if you click the “create post” button, then click the "back" button, the subscribe button should magically appear.

1
submitted 2 years ago* (last edited 1 year ago) by [email protected] to c/[email protected]
 

UPDATE: HERE IS THE ANSWER

^^^^^^^


Hi,

Lemmy is awesome.

I’m having trouble launching my instance.

Here is a home page screenshot:

HERE'S THE FULL ERROR:

“Found. Redirecting to /404?err=FetchError: invalid json response body at http://lemmy:8536/api/v3/post/list?page=1&limit=20&sort=Active&type_=Local&saved_only=false 
reason: Unexpected token N in JSON at position 0”

IF YOU CLICK ‘SIGN UP’, CONSOLE SAYS:

client.js:formatted:60298 Uncaught TypeError: Cannot read properties of undefined (reading 'site')
    at n.get (client.js:formatted:60298)
    at n.get (client.js:formatted:60293)
    at n.a.render (client.js:formatted:59987)
    at Ae (client.js:formatted:7378)
    at Pe (client.js:formatted:7410)
    at client.js:formatted:7420
    at Ve (client.js:formatted:7423)
    at client.js:formatted:7495
    at Ue (client.js:formatted:7497)
    at qe (client.js:formatted:7819)

OFTEN REQUESTED LOGS / CONFIGS: (pastebin)

Docker logs (2 errors)

  • TL-DR (the 2 errors):
  • lemmy_server:::root_span_builder:NotFound
  • lemmy_server:::root_span_builder:captcha_incorrect

Lemmy config

Nginx config (/etc/nginx/sites-enabled/ggg.com.conf)


PORTS

I have the following ports open on the server (maybe too many):

  • 22, 80, 443, 8536, 5432, 1235

And the following rules in IPTABLES (maybe too many)

  • A INPUT -p tcp -m state --state NEW -m tcp --dport 22 -j ACCEPT
  • A INPUT -p tcp -m state --state NEW -m tcp --dport 80 -j ACCEPT
  • A INPUT -p tcp -m state --state NEW -m tcp --dport 443 -j ACCEPT
  • A INPUT -p tcp -m state --state NEW -m tcp --dport 8536 -j ACCEPT
  • A INPUT -p tcp -m state --state NEW -m tcp --dport 5432 -j ACCEPT
  • A INPUT -p tcp -m state --state NEW -m tcp --dport 1235 -j ACCEPT

I've failed at several 'fixes'.

If anyone knows what to do, I’d really appreciate the guidance.

If any more info is needed, I'll gladly provide.

Thank you

view more: next ›