- 0 Posts
- 8 Comments
squincybones@lemmy.mlto
Off My Chest@lemmy.world•Lemmy ain't the cure - humans suck everywhereEnglish
1·1 year agoIt may be more apt to share the recommendation that individuals should regulate their social media use to limit negative effects. The limits must be self-defined according to what each of us can tolerate. Bear in mind that it is often easier to define limits with the help of a mental health professional.
squincybones@lemmy.mlto
Not The Onion@lemmy.world•U.S. House Speaker calls Portland naked bike ride [protest] ‘most threatening thing I’ve seen yet’English
4·1 year agoThis reads to me like mockery. As in, “Naked bike riding is the most dangerous demonstration so far.” Not dangerous at all.
Recently in the US, a murder suspect’s father told a priest, who tipped off the FBI, leading to the arrest.
squincybones@lemmy.mlto
3DPrinting@lemmy.world•Does the filament path of ruby nozzles degrade + is DUROZZLE any good?English
3·1 year agoThe filament path does degrade. You want your filament to travel through your PTFE tube and nozzle with the smallest air gap possible (from extruder to nozzle- filament roll to extruder doesnt matter as much).
Due to wear over time, your PTFE tube and nozzle are both “wear items” like the brakes on your car.
Here’s a great article with photos of some new and used nozzles that have been cut in half to show the wear.
squincybones@lemmy.mlto
Android@lemdro.id•Let's talk security: Answering your top questions about Android developer verificationEnglish
5·1 year agoI understand where you’re coming from with this comment. I’m also generally frustrated when I see people commenting on sensationalized headlines without taking the time to learn more.
I, however, have read their published plans for developer ID’s.
Think back, and be objective about how Google has managed Android since AOSP launched. Time and time again, Google has borrowed and adapted code which was submitted to the project by talented, passionate developers who expected no compensation. At each milestone, Google has taken steps to apply additional restrictions on developers- Siding instead with hardware manufacturers to limit the public’s ability to use their purchased hardware as they see fit.
I am aware that there is a balance that must be struck to limit expense, exploitation, and to prevent widespread security incidents and piracy, but how many times in the past have end users and developers been in this precise situation over the years? How long until Google decides that they don’t need the AOSP project at all and fork the entire project? They’ve already taken large parts of the framework private.
Maybe I’m a little jaded, but I can’t see a benefit here for anyone but Google and hardware manufacturers. This is just another step towards locking us out.
squincybones@lemmy.mlto
Android@lemdro.id•Let's talk security: Answering your top questions about Android developer verificationEnglish
181·1 year agoWhat if they refuse to approve your developer identity application? Now you can’t sideload the app you developed for personal use.


Some others shared that this is likely a federated mastadon post and that the formatting doesn’t get translated well. To me, this looks like a couple of short comments with links to 3 communities, but no specific content related to the comments. Here’s a screenshot:
No offense intended.