What's new in modded minecraft today?

  • The FTB Forum is now read-only, and is here as an archive. To participate in our community discussions, please join our Discord! https://ftb.team/discord

Geometry

New Member
Jul 29, 2019
468
0
1
This is interesting. Apparently Redstone in Motion is now being maintained by a new Dev under a new name "Remain in motion".
There was apparently some "issues" between the original dev and the FTB team that prevented it from being included in any FTB pack.
I did ask and it seems that this dev doesn't seem to have the same "issues" but I don't really know what all those issues are so I can't be sure.

But I'm hoping that this mod under this new dev will be included in a FTB pack soon.

http://forums.technicpack.net/topic/59545-16x-remain-in-motion-continuation-of-redstone-in-motion/
Just so you know, this was already posted here a while ago. The author also made a thread about it here: http://forum.feed-the-beast.com/thr...in-motion-block-moving-mod.45350/#post-634842
 

Geometry

New Member
Jul 29, 2019
468
0
1
@TeamCoFH have updated Thermal Expansion 3 to 3.0.0.7

TeamCoFH said:
3.0.0.7

-Bugfix: Cryotheum should no longer solidify non-source Glowstone. -Bugfix: White wool in a Pulverizer no longer gives dye. -Bugfix: Fixes occasional crash caused loading a world with already stuffed ducts and 3.0.0.6.

-Tweak: Blizz will now spawn on stone, in cold biomes, when dark. -Tweak: Chance for dye in the Pulverizer reduced to 5% by default. :)

Farewell Glowstone Generators :(
 

AlCapella

New Member
Jul 29, 2019
709
0
0
This sounds problematic. Sending any sort of data to third party sores. And I don't see anything saying explicitly what the mod is for or even what sort of data is collected.
It sounds like it's for testing mods but this kind of data can be should be gathered by the mod devs during testing. And should never sent over the net.

The real hazard is that this mod might be currently benign in nature. If someone involved had malice in mind all they would have to do is wait a few versions until people stop checking the code and slip in the dangerous code.

Disagree somewhat.

If you used google/chrome for your daily activities, there is enough data being collected behind your back, and enough installs and updates being done behind you back, which is way more than what this mod is actually doing. And at some level you should be more worried about those things than this.

That aspect of counter scaremongering aside, can we please give more credit to the mod dev than that last paragraph above :( . Here is a sample of a recent twitter conversation b/w tema, mikemoo and another person:

@amadornes @Extra_Utilities I'd probably refuse the pull request :)

He knows what he is doing (and what he knows, he knows well). Look, use it, or don't use it, that's up to the player's choice right now. The mod itself is doing a excellent job in providing good, and relevant debugging information to the mod authors to fix their mods better. I suspect many if not all mod devs will get behind this idea very quickly and endorse this mod as it will facilitate their debugging by quite a bit.

In defence of the idea behind the mod, it is a clever idea whose time was overdue. Mod devs have enough on their plates than writing something like this as well into their main mod code (bloatware, anyone?). Rules of good software are, modularity, and "do the one thing you do, right" among others. Sending debug information is a straightforward and common activity, regardless of what mod does it. So, why not have a mod that does exactly this activity as its sole purpose of existence?

Lastly, let us accept that all human systems are vulnerable to some form of exploit from another perverted human being, at some point or another. Latest case in point? heartbleed exploit. And it won't likely be the last one either.[DOUBLEPOST=1399532439][/DOUBLEPOST]
IMHO opinion openeye should be open source code mod developers could put in their mod to act the same way as it does now, just exclusively to the mod and mod authors who want it. So just plug in the code give your mod id and a place to send crash reports, then done.

Did you click the links? From their website:
Our primary aim is to collect and share vital information to allow us to provide a set of tools to the community to make the experience easier, drama-free and more secure for both users and modders.

We want to make it clear from the very start that we do this in a completely transparent way - our data is open to anyone and our code is open source. We do not track users or keep any identifying information, and people are very welcome to confirm that for themselves by browsing the code or the regular data dumps that we will provide.
 
Last edited:
  • Like
Reactions: FrankieTheSnake

VikeStep

New Member
Jul 29, 2019
1,117
0
0
I was in an IRC Channel and KingLemming showed up and posted this:
8DPhD.png


If you can't see it, look at the window title
 

AlCapella

New Member
Jul 29, 2019
709
0
0
I was in an IRC Channel and KingLemming showed up and posted this:
8DPhD.png


If you can't see it, look at the window title

Won't lie! I said this aloud,


and in that exact voice :-( DIAF, all of you, for eliciting that response from me :p

Failed I have, into exile I must go :(
 

NJM1564

New Member
Jul 29, 2019
2,348
-1
0
Disagree somewhat.

If you used google/chrome for your daily activities, there is enough data being collected behind your back, and enough installs and updates being done behind you back, which is way more than what this mod is actually doing. And at some level you should be more worried about those things than this.

That aspect of counter scaremongering aside, can we please give more credit to the mod dev than that last paragraph above :( . Here is a sample of a recent twitter conversation b/w tema, mikemoo and another person:

He knows what he is doing (and what he knows, he knows well). Look, usse it, or don't use it, that's up to the player's choice right now. The mod itself is doing a excellent job in providing good, and relevant debugging information to the mod authors to fix their mods better. I suspect many if not all mod devs will endorse this mod as it will likely facilitate their debugging by quite a bit.

In defence of the idea behind the mod, it is a clever idea whose time was overdue. Mod devs have enough on their plates than writing something like this as well into their main mod code (bloatware, anyone?). Rules of good software are, modularity, and "do the one thing you do, right" among others. Sending debug information is a straightforward and common activity, regardless of what mod does it. So, why not have a mod that does exactly this activity as its sole purpose of existence?

Lastly, let us accept that all human systems are vulnerable to some form of exploit from another perverted human being, at some point or another. Latest case in point? heartbleed exploit. And it won't likely be the last one either.[DOUBLEPOST=1399532439][/DOUBLEPOST]

Did you click the links? From their website:

Comparing it with google is not exactly a good thing.
That's like saying this drink will poison you and this other drink will poison you a little less so you should take it.

That twitter conversation has nothing to do with any of this. Why did you post it?

As for information that helps mod devs the crash logs that players post are enough for any debugging purposes. No dev should need more. And by manually posting those logs we can see just what it is that we are posting.
There is a reason no legitimate dev has ever written code like this into there mod.

Human systems are vulnerable but that doesn't mean we should stop trying to be cautions.

Even if Mike's intentions are completely pure and hoist, and I'm sure they are, people will find a way to take advantage of this. Make a similar mod pass it around or modify his version and send it out in a mod pack.
 
  • Like
Reactions: Jadedcat

mikeemoo

New Member
Jul 29, 2019
117
0
0
"As for information that helps mod devs the crash logs that players post are enough for any debugging purposes. No dev should need more. "

Actually, the logs that users post normally have FAR FAR more potentially sensitive information than we collect. We collect as little as we can while trying to balance that against giving mod developers just enough information to be able to work out what could be going wrong - and even though we make sure we don't send any potentially personal fields of data, we even go so far as to make sure we sanitize things like the actual crash message on the off-chance that a mod developer has done something weird and put a username or similar in the actual exception message.

The response for this project has been overwhelmingly positive, from both modders and users - and even after it's first day of release it's been helping mod developers catch crashes early that would normally have taken longer to hunt down.

A project like this will always have that 1% of people who don't like the idea. That's fine - they are under absolutely no obligation to use it, and it's very easily disabled via snooper settings, config files, or un-installing (we make SURE they user is very aware of what the mod does when you first install it, with flashing icons and lots of help).
 

NJM1564

New Member
Jul 29, 2019
2,348
-1
0
and even though we make sure we don't send any potentially personal fields of data, we even go so far as to make sure we sanitize things like the actual crash message on the off-chance that a mod developer has done something weird and put a username or similar in the actual exception message..

This is the important part. You might want to place that information front and center. Along with mentioning that the mod is for collecting bug and crash related data.
Just saying it collects information is a little unspecific.

Cause this makes no since to a laymen.
"Our primary aim is to collect and share vital information to allow us to provide a set of tools to the community to make the experience easier, drama-free and more secure for both users and modders."

Infact it kind sounds like this.
"Our primary aim is to collect and share vital information [Like passwords and credit card information] to allow us to provide a set of tools to the community to make the experience [of stealing your stuff] easier, drama-free and more secure [for our experienced leet hackors] for both users and modders."

(The [] is what leaps to a persons mind as they are reading that.)

That screams run away in big flashing neon lights. And any assurances after that only makes it worse.

In addtion to modifying that phrasing and being more spesific as to what kind of data you will and will not collect I'd recommended getting a known third party to vet the program. That would make a lot of people feel more secure. Something like (picks a random moder name) "Mdyo tested and approved". Or "Proven Jadedcat resistant." Or Direwold says "He didn't derp it".
 

mikeemoo

New Member
Jul 29, 2019
117
0
0
This is the important part. You might want to place that information front and center. Along with mentioning that the mod is for collecting bug and crash related data.
Just saying it collects information is a little unspecific.

Cause this makes no since to a laymen.
"Our primary aim is to collect and share vital information to allow us to provide a set of tools to the community to make the experience easier, drama-free and more secure for both users and modders."

Infact it kind sounds like this.
"Our primary aim is to collect and share vital information [Like passwords and credit card information] to allow us to provide a set of tools to the community to make the experience [of stealing your stuff] easier, drama-free and more secure [for our experienced leet hackors] for both users and modders."

(The [] is what leaps to a persons mind as they are reading that.)

That screams run away in big flashing neon lights. And any assurances after that only makes it worse.

Tried my best to make it as clear as possible, but it seems I'm not too great at English :) thanks for the feedback.
 

AlCapella

New Member
Jul 29, 2019
709
0
0
Glad that @mikeemoo chimed in. However there are a few things that I want to clarify here about your reply to my post. I gave it a few hours to think if I wanted to write this. Yep, definitely wanted to post this one reply at least.

Comparing it with google is not exactly a good thing.
That's like saying this drink will poison you and this other drink will poison you a little less so you should take it.
Wrong. I am saying, "you are are ignoring the elephant in the room and tackling a helpful irc error logger instead" :rolleyes:

That twitter conversation has nothing to do with any of this. Why did you post it?
^^ I will admit it. This is what got my goat the most! I was seriously offended that you even had the gall to make this remark. Let me attach what you wrote:
The real hazard is that this mod might be currently benign in nature. If someone involved had malice in mind all they would have to do is wait a few versions until people stop checking the code and slip in the dangerous code.
So, from that paragraph:
  1. Who is the "someone involved had malice in mind"? Is it the mod dev? Is it the contributor? Anonymous pull request maker? Who?
  2. Who is going to "stop checking the code"? Again, mod dev? general public? pull request maker? Who?
  3. Who is going to " slip in the dangerous code"? Once again, is it the mod dev? Is it the contributor? Anonymous pull request maker? Who?
That tweet was to say you are wrong in that blanket whitewashing statement that you just made. Spell it for you: The mod dev is clued up on what he does, is clued up on what he wants to include or not, and extrapolating this further, if you want to persist with this "slip in malicious code" angle, you might as well revert to vanilla MC. cuz you know, no mod is safe :eek:

As for information that helps mod devs the crash logs that players post are enough for any debugging purposes. No dev should need more. And by manually posting those logs we can see just what it is that we are posting.
There is a reason no legitimate dev has ever written code like this into there mod.
o_O I definitely think @mikeemoo was very kind in his reply to your post. Please read this para again. Really? Dat last line tho o_O :rolleyes:
Although ironically, your remarks reminded me of these historically (in)famous replies similarly made with regards to computers.
  1. 640K ought to be enough for anybody - Bill Gates
  2. I think there is a world market for maybe five computers - Thomas Watson.
So glad people did listen to ^^ those visionaries, eh? And definitely glad mikeemoo didn't think so about the "universal sufficiency" of pasting voluminous error logs into pastebin either (as his mod evidenced). Nothing better to do than scroll through pages of error logs to debug *each and every* time, eh? I give up. But honestly, dat last line tho o_O :rolleyes:

Human systems are vulnerable but that doesn't mean we should stop trying to be cautions.
Even if Mike's intentions are completely pure and hoist, and I'm sure they are, people will find a way to take advantage of this. Make a similar mod pass it around or modify his version and send it out in a mod pack.

I. just. don't. even. know. where. to. start.... if. to. start....

And after all this stance in your reply to my post, you dropped this clanger in your reply to @mikeemoo

I'd recommended getting a known third party to vet the program. That would make a lot of people feel more secure. Something like (picks a random moder name) "Mdyo tested and approved". Or "Proven Jadedcat resistant." Or Direwold says "He didn't derp it".
What an about turn! So now that last para of "yada yada yada all they would have to do is wait a few versions until people stop checking the code and slip in the dangerous code" is not valid anymore? Because "x said so"? For every release?
Thanks very much for reminding me the names of quite a few cognitive biases. /sarcasm

[Stands up and leaves. Closes door softly behind him]
 

midi_sec

New Member
Jul 29, 2019
1,053
0
0
This is the important part. You might want to place that information front and center. Along with mentioning that the mod is for collecting bug and crash related data.
Just saying it collects information is a little unspecific.

Cause this makes no since to a laymen.
"Our primary aim is to collect and share vital information to allow us to provide a set of tools to the community to make the experience easier, drama-free and more secure for both users and modders."

Infact it kind sounds like this.
"Our primary aim is to collect and share vital information [Like passwords and credit card information] to allow us to provide a set of tools to the community to make the experience [of stealing your stuff] easier, drama-free and more secure [for our experienced leet hackors] for both users and modders."

(The [] is what leaps to a persons mind as they are reading that.)

That screams run away in big flashing neon lights. And any assurances after that only makes it worse.


In addtion to modifying that phrasing and being more spesific as to what kind of data you will and will not collect I'd recommended getting a known third party to vet the program. That would make a lot of people feel more secure. Something like (picks a random moder name) "Mdyo tested and approved". Or "Proven Jadedcat resistant." Or Direwold says "He didn't derp it".

My friend, FAQ.

here it spells out what the mod does in the detail that you're requesting. @mikeemoo your english is fine. :)