I wonder if there are companies that are a good fit for people who are good at programming but bad at programming alone when it comes to the 95% of the workaday tasks that aren't naturally engaging in their own. So, lots of pair programming and close collaboration of 2+ developers on even fairly small projects. I also wonder if there are any shops that have perfected the art of doing this remotely.
I think the next release of #mastalab will offer the ability to follow instances.
Currently, I need to set by default cross-account actions but an important part already works.
tech 🌶️🌶️🌶️ w/caps & effbombs Show more
While I'm at it, it is truly amazing the number of Android apps which absolutely shit when your phone happens to switch networks when you hit a button. You'd think in the Year of Our Lord two thousand and eighteen that MAYBE some engineer involved at SOME level of the stack on these apps MIGHT have given a thought to that
look when i first heard "the sharing economy" i thought it meant "a cooperative end to scarcity" so i am extremely disappointed that it just means "worse jobs for worse pay"
mastodev, relays, hashtag search, small instances Show more
Hey, it'd be cool if relays also facilitated hashtag search, allowing small instances which don't want to have a huge database to at least query the hashtags of the everything the relay sees. I feel like the better search on them works, the more attractive hashtags become. Yay masto hashtags! 😀 @Gargron #mastodev
This company wants you to have a bachelors degree to make memes lmao
ActivityPub spec take Show more
i'm glad that ActivityPub reached Recommendation status before the Working Group charter expired but I think
1. It needs a 1.1 or 2.0 release to clarify a LOT of behaviors and clean up a lot of aspects of the spec
2. That 1.1/2.0 draft should basically be a rewrite informed by how it is (a) being used, and (b) planned to be used by implementors in the wild, with special attention paid to implementations with unconventional needs
I've got SSD taste, but 5200 RPM HD wealth
Problems we are having with #Signal:
* It is and will remain centralized (clear strategy of *not* federating servers)
* It requires strong identifiers/selectors (phone#) to use
* Author disallows distribution by anyone but Google, although free/libre
* It keeps pushing away verification of fingerprint in interface
* It relies on Google+Amazon infrastructure
* Its funding is shady (OTF = Radio Free Asia = USG)
= clearly unethical choices, unjustifiable by accessibility or technological reasons.
The Better options all require advanced skills to use. Non-technical users deserve privacy too.
* Non-federation means users not giving up at server selector dialog and no one-off hostile servers.
* Phone numbers are mediocre IDs but hard for users to screw up.
* Google prevents third parties (e.g. abusive ex, corrupt local sherrif) from tampering with the apk.
* Funding is funding; the USG funds lots of stuff, some of it good.
Signal is imperfect but the perfect is the enemy of the good.
I feel like instead of decrying all content recommendation systems as evil spyware, we should work on ethical alternatives.
There should be a global 'awareness' week for developers. For a week reduce your RAM to 2 GB, disable all cores except 2, downscale your resolution to 1366x768 and cap your internet at 1 Mbps (or less for mobile developers)...
Maybe, just maybe we will start to have less crappy, bloated software.