Notices by KemoNine (kemonine@social.holdmybeer.solutions)
-
KemoNine (kemonine@social.holdmybeer.solutions)'s status on Saturday, 22-Jun-2019 21:12:27 UTC 
KemoNine
@craigmaloney it's not as bad as you think 😉
it's still a common "thing" at times.
box may also be ano ther one to look into but i don't know if they have a proper linux client these days -
KemoNine (kemonine@social.holdmybeer.solutions)'s status on Saturday, 22-Jun-2019 21:11:19 UTC
KemoNine
@craigmaloney If it works with owncloud it should also "just work" with nextcloud.
It's likely using web dav or similar behind the scenes. -
KemoNine (kemonine@social.holdmybeer.solutions)'s status on Friday, 13-Jul-2018 18:45:00 UTC
KemoNine
Lollipop Cloud is now 100% independent and self-hosted and all the things.
No more shared anything (domain / dns included)
Check out the updated domain at https://lollipopcloud.solutions
ALL services have been migrated thanks to the core Lollipop Team doing a *ton* of work over the last week or so.
Please boost/toot/etc so people know where to find us again 😉
(image desc: lollipop cloud logo) -
KemoNine (kemonine@social.holdmybeer.solutions)'s status on Thursday, 28-Jun-2018 21:35:15 UTC
KemoNine
Who on the west coast near Seattle knows of open Python developer positions?
NEED HELP ASAP!!!!!!
Asking for a friend.
Signal boosts appreciated -
KemoNine (kemonine@social.holdmybeer.solutions)'s status on Monday, 04-Jun-2018 03:58:35 UTC
KemoNine
@alcinnz @cwebber mentioned ocap-ld to me earlier but it's not quite there yet.
Hopefully with the AP network growing and getting more software we'll see things like ocap-id progress quickly.
The more we can all work together on decentralization the better IMHO. The megacorps are due for some foundation shaking.
https://w3c-ccg.github.io/ocap-ld/ -
KemoNine (kemonine@social.holdmybeer.solutions)'s status on Wednesday, 23-May-2018 06:48:56 UTC
KemoNine
@kaniini @href I know this but I'm in a position of convincing others that this is the case.
The pleroma devs are about the code, quality of code and reasonable features and reasonable prioritization of development.
As a professional programmer I <3 this approach.
It can be a pain in the ass to put forth to non-devs though.
I deployed pleroma *because* you and other are decidedly non-assholes by default and focused on building good code and being reasonable about said code.
Aside from the code the pacmaning of gnusocial instances by pleroma puts the non-programmer ethos in a difficult position. I don't assume you are pro-jackass admin but at the same time your software is taking over those instances.
*That* is the hard problem to solve and one I've already argued in favor of pleroma
All Chirp! content and data are available under the