dsfgs@activism.openworlds.info asked:
> Would that fit with your vision?
Re: Jobseeker service? I wouldn't be against it but would there be demand for someone skilled in recruitment to be at the couple branches? And would there be the casual jobs available at council to have this sort of setup? How popular will the bank even be? If it were popular, maybe a noticeboard in the branch(s) advertising council jobs, and prompting visitors to council's jobs page (https://careers.unley.sa.gov.au/job-search/) if a skilled recruiter was not physically present.
It might be self-reinforcing, in that some may visit the branch for the job leads and others for the non-lending banking but after they have an interest in the other service too!
It could align with other strategies like water, land use and resilience. For example, in relation to a more ethical response to common plants ("weeding"), by not using "possibly carcinogenic" herbicides, its possible a FOS app can be developed that connects willing workers with council for a morning of "weed" removal, or urban farm work etc. I'm not totally comfortable with an app, even an ethical FOS app, until other issues are resolved surrounding tech. I'm going to say a lot is possible, if and only if council are honest and upfront about challenges and is able to communicate effectively, easily and without pomp.
dsfgs asked:
> (...)what country are you in?
Same as you... on the plains where 'Adele' laid. 😅
1.) If the public bank were to act as a recruitment service, it would only be able to recruit into public (aka government jobs). Otherwise we get into the same problems of government "speculating" on or choosing winners and losers and that is exactly a type of problem that got us into messes we are currently in.
Being governed by council, the scope would be further limited to local government jobs.
2.) Are you able to explain the second point about encryption keys in more detail. What is the use case? You want the bank to store your public keys. Will you pay them to do this? They may need to verify you, which will take some effort. Or do you want them to just store any keys with no guarantee of reliable service?
patching file display.css
Hunk #17 FAILED at 1224.
1 out of 17 hunks FAILED -- saving rejects to file display.css.rej
About the answer: I don't think Javascript is involved. If you hover the "in reply to" of your notice (the one starting with "BTW"), you'll see that it is, indeed, a reply to your previous notice (the one starting with "Np"). It would have notified me if it were an answer to one of my notices.
I tend to manually insert the handle of the account I'm writing to, as it would not produce notifications for mastodon (and maybe pleroma) otherwise.
That line is 100% correct. 😁 There is a (�) question mark in a diamond character that I removed from the file in the git repo. You'll see that I replace that line with the same line just with that diamond character removed.
> This is what I get when I run "patch display.css [lots of errors]
After you get the file the sha256 of it should conform to:
913a1e2bb5d44777643b91cbd16743d10e80deafd46c97950f61cd3d4c997de8
After above you should be able to run:
patch display.css out.patch
(I should have really named it 'input.patch')
Tell me how you go.
> This [post] didn't notify me, because you wrote it as an answer to yourself.
Ah! Ok, I was wondering about that! So when someone clicks the 'reply' button I'm going to assume that Javascript is used to add all the needed recipients? One day I will turn on the javascript to test it but I want to be able to learn the non-javascript method of using GNUSocial first.
@dcent This is what I get when I run "patch display.css <display_css_dcent":
patching file display.css
Hunk #2 FAILED at 4.
1 out of 2 hunks FAILED -- saving rejects to file display.css.rej
patching file display.css
Hunk #1 FAILED at 159.
Hunk #2 FAILED at 186.
Hunk #3 FAILED at 243.
Hunk #4 FAILED at 247.
Hunk #7 FAILED at 269.
Hunk #9 FAILED at 276.
6 out of 9 hunks FAILED -- saving rejects to file display.css.rej
patching file display.css
Hunk #4 FAILED at 980.
Hunk #5 FAILED at 984.
patch unexpectedly ends in middle of line
patch: **** unexpected end of file in patch at line 77
@forza4 [ESP] Te damos la bienvenida a gnusocial.net. Varias cosas:
- Es NECESARIO responder a este mensaje para levantar el aislamiento inicial de tu cuenta.
- Las cuentas que continúen aisladas al cabo de un mes serán borradas.
- Las cuentas antiguas sin actividad serán borradas al cabo de un año.
- Documentación: https://gnusocial.net/url/7821081
[ENG] Welcome to gnusocial.net. Several things:
- You MUST answer to this notice in order to get your account initial sandboxing uplifted.
- Sandboxed accounts will be deleted after one month.
- Old accounts without activity will be deleted after a year.
- Docs: https://gnusocial.net/url/7821081